Conversation

Notices

1. Embed this notice
   feld (feld@friedcheese.us)'s status on Sunday, 01-Sep-2024 02:21:37 JST feld
   What's the deal with all the #FreeBSD infighting happening over the FreeBSD-SA-24:05.pf patch? (it broke things, a new patch is coming)
   
   Like, why? Who gives a shit. Nobody actually cares about the old bad blood between Netgate/pfSense and Decisio/Opnsense. So the maintainer that broke shit (and did the modern pf port from OpenBSD) works for Netgate and then ignores bug reports from Opnsense blaming Opnsense's kernel
   
   > “Getting stuff upstreamed in other operating systems usually is a lot more difficult, and often you run into a roadblock” “While after a short amount of time, it’s integrated into part of FreeBSD”
   
   https://freebsdfoundation.org/blog/freebsd-as-a-platform-for-your-future-technology/
   
   okay but Allan you're a src committer so of course you can upstream it.
   
   Why do we even have to do this stupid bickering. SHUT UP AND CODE. And also let the Linux folks fighting over their Rust bullshit have the drama. We don't need this.
   • Embed this notice
     Tim W (admin (and human)) (tim@union.place)'s status on Sunday, 01-Sep-2024 02:27:04 JST Tim W (admin (and human))

     in reply to

     @feld To be fair Linux probably doesn't **need** the drama either. But I'd definitely give it to them over FreeBSD. <3 FreeBSD.

     feld likes this.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Sunday, 01-Sep-2024 02:41:05 JST feld

     in reply to

     • Tim W (admin (and human))
     @tim it's their social currency
   • Embed this notice
     Tim W (admin (and human)) (tim@union.place)'s status on Sunday, 01-Sep-2024 02:41:06 JST Tim W (admin (and human))

     in reply to

     @feld though I guess maybe Linux does in fact live on the drama...

   • Embed this notice
     Miscbrains:beastie::segasaturn: (miscbrains@misc.brainsoap.net)'s status on Sunday, 01-Sep-2024 07:12:22 JST Miscbrains:beastie::segasaturn:

     in reply to

     @feld@friedcheese.us fallout from the drama with the wireguard import drama?

   • Embed this notice
     John-Mark Gurney (encthenet@flyovercountry.social)'s status on Tuesday, 03-Sep-2024 03:03:10 JST John-Mark Gurney

     in reply to

     @feld

     Actually, why is that an SA and not an EN?

     I don't see any particular security issue other than an echo reply can be triggered from a local broadcast domain machine. Yes it is a firewall bypass but nothing malicious can be done with it.

     If this is an SA, then there are definitely ENs that should have been an SA.

     #FreeBSD

     feld likes this.
   • Embed this notice
     feld (feld@friedcheese.us)'s status on Tuesday, 03-Sep-2024 05:42:41 JST feld

     in reply to

     • John-Mark Gurney
     @encthenet I'll support you on this if you want them to rescind the SA. I think labeling it as an SA caused the remediation to be rushed. And every time I think about it, it's like "okay so they gotta be on the same broadcast domain to send you an ND packet, and then ping following to hopefully get a response confirming it exists? But this would never work to scan the entire IPv6 address space and the threat is already on your network you control or is your ISP's modem/router?"
   • Embed this notice
     John-Mark Gurney (encthenet@flyovercountry.social)'s status on Tuesday, 03-Sep-2024 11:11:22 JST John-Mark Gurney

     in reply to

     @feld
     I mean, there are public wi-fi and guest networks that are potentially malicious, but still nothing like the recent windows ipv6 vuln.

     feld likes this.