Netgate: Difference between revisions
correct two inaccurate usurped url-status values to dead Tag: Reverted |
restore the previous version Tag: Manual revert |
||
| Line 20: | Line 20: | ||
===Targeting other projects=== | ===Targeting other projects=== | ||
Netgate's co-founder, Jamie Thompson, has publicly criticized competing projects including OPNsense, a fork of pfSense.{{Citation needed|date=March 2026}} OPNsense, which is endorsed by the developers of m0n0wall (the project from which pfSense originated), was also the target of a parody website<ref>{{Cite web |author= |title=OPNSense |url=https://www.opnsense.com/ |website=OPNsense.com |date= | Netgate's co-founder, Jamie Thompson, has publicly criticized competing projects including OPNsense, a fork of pfSense.{{Citation needed|date=March 2026}} OPNsense, which is endorsed by the developers of m0n0wall (the project from which pfSense originated), was also the target of a parody website<ref>{{Cite web |author= |title=OPNSense |url=https://www.opnsense.com/ |website=OPNsense.com |date= | ||
|access-date=22 Mar 2025 |url-status= | |access-date=22 Mar 2025 |url-status=usurped |archive-url=https://web.archive.org/web/20160314132836/https://www.opnsense.com/ |archive-date=14 Mar 2016}}</ref> created by Netgate. OPNsense had to file a complaint with the World Intellectual Property Organization (WIPO) to gain control of the disputed domain.<ref>{{Cite web |author= |title=Netgate / pfSense acts in bad faith |url=https://opnsense.org/opnsense-com/ |website=OPNSense.org |date=24 Nov 2017 |access-date=22 Mar 2025 |url-status=usurped |archive-url=https://web.archive.org/web/20250321054706/https://opnsense.org/opnsense-com/ |archive-date=21 Mar 2025}}</ref><ref>{{Cite web |last=Barbero |first=Luca |title=WIPO Domain Name Decision: D2017-1828 |url=https://www.wipo.int/amc/en/domains/decisions/text/2017/d2017-1828.html |website=WIPO |date=12 Nov 2017 |access-date=1 Mar 2026 |url-status=live |archive-url=https://web.archive.org/web/20180207122545/https://www.wipo.int/amc/en/domains/decisions/text/2017/d2017-1828.html |archive-date=7 Feb 2018}}</ref> | ||
===Security concerns with WireGuard implementation (''2021'')=== | ===Security concerns with WireGuard implementation (''2021'')=== | ||