nginx2root

I'm sure if there was a cheap, easy & quick way of addressing the issue it would have been done.

The only workaround seems to be to build your own packages from ports, but that's not necessarily fun.
Do we want to lay back and accept that situation, or do we want to change that in a good way?
AI driven attacks are pushing the timeline even more.
It is not always possible for everybody to have your own ports compiled due to various reasons.
This is the reason why we have the pkgs in first place.

Are we now accepting that using pkgs are insecure by default?
Then we might have a problem in general since the pkg base it pointing to that direction even more in the future.
 
I am using ports, no worries. I am not looking for a fight, I am pointing to a current structural problem.
Following your path: We should then abandon the pkg use on servers. Thats a very good sign for all the pkgs users and self hosting dudes out there.
 
Well, all the sites my web dev company built were on http3 by the time we closed down. We were always bleeding edge but that's why they loved us.
Any http2/3 server will happily chug along with http1 requests. @everyone, do any servers allow turning off http1 at all? I don't think that's even possible because 2 and 3 are built on top of 1.
 
With a little help from Gemini, should work on FreeBSD too.
nginx -T 2>/dev/null | grep -E '^\s*(http2\s+on\b|listen\b[^#]*\b(http2|quic)\b|resolver\b|mail\s*\{)'

If you get no output none of the vulnerable modules are loaded or active. Then you can breathe again, sit back and wait for the update, you're not going to be hacked in the meantime. Not through any of this at least.
 
Well, then you'd be blocking older browsers and other things from accessing your site if they can't do http2.
any browser THAT old also very likely isn't capable of TLS 1.2+ and can't connect anyways. (you DO have TLS 1.0/1.1 disabled, do you? It's been deprecated over 4.5 years ago...)
 
online ordering system
where up to date security and encryption is mandatory as you are processing personal data and possibly even payment details. Seriously - ancient, known broken encryption has absolutely no place here - you can't put all users at risk just for those 4 idiots that still want to use their Windows XP doorstop to browse the web...
 
🤔

Just as a thought experiment: how much faster would packages be built if anything rust and rust dependend would be excluded out of the ports tree ?
Hey sacrifices have to be made in the name of security , 🤪
 
🤔

Just as a thought experiment: how much faster would packages be built if anything rust and rust dependend would be excluded out of the ports tree ?
Hey sacrifices have to be made in the name of security , 🤪
we'll be like
Yo, AI Agent my d0g, binary patch my vulnerable shit.....
 
🤔

Just as a thought experiment: how much faster would packages be built if anything rust and rust dependend would be excluded out of the ports tree ?
Hey sacrifices have to be made in the name of security , 🤪

The Debian project seems to have no problems building specific, single packages fast even though their tree has the same pigs as ours.
 
where up to date security and encryption is mandatory as you are processing personal data and possibly even payment details. Seriously - ancient, known broken encryption has absolutely no place here - you can't put all users at risk just for those 4 idiots that still want to use their Windows XP doorstop to browse the web...
Are you talking to me? Have no clue why you would be. Our systems were so bleeding edge some people were afraid of us. You couldn't punch holes in our stuff.
 
Back
Top