❌ Software Replacement | Replacing pfsense with opnsense and adding ipfire as additional suggestion #2254
Labels
No Label
🔍🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
No Milestone
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#2254
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
After the previous 2 issues (add opn as suggestion) seemed to have lost traction i thought its time to create a suggestion to not just add opnsense as recommendation but replace pfsense entirely with it.
Why I am making the suggestion
In light of recent news of pfsense plus netgate states the following:
https://www.netgate.com/blog/announcing-pfsense-plus.html
So in short: dropping non-paying customers like hot potatoes and putting future support in the hands of the community while moving new security features and improvements to the paid-only version.
Together with apparently never actually being open source in the first place ( https://github.com/rapi3/pfsense-is-closed-source ) this should make them an absolute non-recommendation on something as delicate as privacy tools you have to rely on. (Even when using the paid version).
In stark contrast opnsense, a fork of pfsense which has massively picked up development pace and ships far newer software versions and (imho) nicer plugins, is committed to the community ( https://opnsense.org/about/about-opnsense/ ). Linux-based ipfire is also going out of their way to maintain support for the community they built their success on, even going as far as to state https://blog.ipfire.org/post/ipfire-is-open-source-software-and-it-going-to-be-open-source-for-forever . As perfectly put by ipfire:
And for a good reason, as with this recent blunder coming from netgate: https://arstechnica.com/gadgets/2021/03/buffer-overruns-license-violations-and-bad-code-freebsd-13s-close-call/ and the ensuing "professional" behaviour ( See the Defense Mail Jason, creator of Wireguard, hat to send out to defend from the outrageous allegations by netgate ) not shining a good light on future unreviewable closed source code in pfsense and their handling of community and external auditor review and contributions.
So for something as essential to security and as central to a network as a firewall users should not have to rely on closed source editions to keep them secure with code they cant review from a company with unprofessional behaviour towards maintainers that plans to focus on updating the closed source, unreviewable and paid edition first - whereas 2 competitors, fully open source, absolutely outdo them with community support and open source at heart. Especially with opnsense being a direct upgrade path.
Previous Issues:
https://github.com/privacytools/privacytools.io/issues/506
https://github.com/privacytools/privacytools.io/issues/497
My connection with the software
Neither author, nor competitor - just a user of opnsense and ipfire after switching from pfsense after learning of their general behaviour. Switched and never looked back.
I have 1 or 2 issues reported against opnsense and plugins whenever i found bugs which have been quickly resolved.