ohai.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A cozy, fast and secure Mastodon server where everyone is welcome. Run by the folks at ohai.is.

Administered by:

Server stats:

1.8K
active users

#IPFire

2 posts2 participants0 posts today

🧱 IPFire Linux Firewall Gets Post-Quantum Cryptography Support for IPsec Tunnels
@9to5linux

“This choice will ensure that modern cryptography is being used when available, but IPFire will remain compatible with older solutions from other vendors. Of course, you may enable this for existing tunnels on the advanced settings page of the tunnel”

9to5linux.com/ipfire-linux-fir

Replied in thread

@adam_wysokinski
@QubesOS (Poland)
@tails (Ireland)
#ParrotOS (Italy)
#IPFire (Germany)
#AlpineLinux (Norway)

This is great because now (F)OSS and non-American solutions are being brought to the table and it shows how much Europe has. And these alternatives or those of us who have been using it for years are the norm and Big Tech is the alternatives 😁 but the developers are getting noticed and that's great. That's also one of the good things about this situation

IPFire is a Linux distribution developed for use as a firewall.

Post-quantum cryptography has been implemented.
Source: ipfire.org/blog/ipfire-2-29-co

Supports running a Tor client.
Supports running a Tor relay.
Source: ipfire.org/docs/addons/tor

Post-quantum cryptography: wikipedia.org/wiki/Post-quantu
Tor: wikipedia.org/wiki/Tor_(networ

Website: ipfire.org
Mastodon: @news

Replied in thread

@lanefu @pearl I mean, I'd rather try to use #ipFire but sadly I've yet to see some #Linux-based #Networking distro / setup that comes close to #pfSense / #OPNsense...

  • It's just that once you used #pfSync / #CARP & had cheap hot-standby hardware redundancy you don't want to go back!

But that's me being "too lazy" to do #iptables...

infosec.space/@kkarhan/1137134

Infosec.SpaceKevin Karhan :verified: (@kkarhan@infosec.space)@ClickyMcTicker@hachyderm.io @pearl@rrr.sh @geerlingguy@mastodon.social *From scratch* should (and would) be possible if said #configuration isn't just proprietary bs but actually following a documented syntax akin to any proper #configuration. - I assume this is *NOT* the case cuz otherwise you'd not offer said job. Not to mention #vendors prefer #siloing amd #Enshittifying products, so having #InterchangeableFormats goes against their primary #commercial interests. - We can see this peak with #Cisco & #Microsoft pushing both proprietary #SingleVendor & #SingleProvider standards, #patenting the implementation (i.e. #VRRP) and sueing everyone who wants to implement them (i.e. #CARP had to do a shitton of redundant work!) whilst also refusing to follow #Standards (i.e. #Posix [new line](https://en.m.wikipedia.org/wiki/Newline) ) & #Conventions (I've seen literal CISCO <=> #IETF dictionaries!)... Sadly it's more #unrealistic to see such standardization to happen than #YAML being replaced [by](https://github.com/greyhat-academy/YADL) #YADL...