@rey @phessler @kellerfuchs As a counterpoint, #OpenBSD fixes stuff like this constantly. Also, @stsp has been doing massive amounts of work in the 802.11 stack for some time now. When that errata came out, I just assumed someone looked over his work and found a bug.

@kurtm @kellerfuchs and to be perfectly clear: we coordinated with the original author on our commit in August.

That the author regrets that choice is 1) not our problem, and 2) not our responsibility.

it is completely inappropriate that he singled out #OpenBSD, when e.g. Mikrotik also stealth published before hands.

*whew* just finished migrating my server to new hardware. did a big #openbsd upgrade, and switched some of the daemons I used for teh lulz.

postfix -> smtpd
apache1.3 -> openbsd httpd

So #OpenBSD is getting flak for #KRACK early patch, yet a silent patch a week before release from Mikrotik is OK?

funny how the only vendor taking flak over #KRAK is #OpenBSD, for patching it. Not the vendors who left everyone vulnerable while they delayed and stalled for half a year.

looks like #OpenBSD fixed the #KRACK #WPA2 attack in 6.1 Errata 027. This is also fixed in 6.2-release.

As #OpenBSD's de-facto wifi maintainer, I first learned about this WPA problem in June. A simple patch was provided which I could commit with slight modifications.

The original embargo was already 2 months long, and then extended again for 2 months.

The generall public (you) were left in the dark about this for at least 4 months.

This is a very sad state of affairs. It takes the industry much too long to apply a simple patch.

"Je rappelle à tous ceux qui s'inquiètent du #wifi que vous pouvez construire votre propre #routeur avec #OpenBSD, #Opnsense, #PfSense ou acheter un Turris."

Ôtez moi d'un doute : c'est moi qui suit con, ou ça n'a absolument rien à voir ?

Je rappelle à tous ceux qui s'inquiètent du #wifi que vous pouvez construire votre propre #routeur avec #OpenBSD, #Opnsense, #PfSense ou acheter un Turris.

Don't worry about today's WPA2 vuln if you're running #OpenBSD - both 6.1-stable and 6.2 release are already patched.

Via Noah Axon on Google+ (yes that still exists...): a nice #OpenBSD tutorial

So yesterday I mildly grumped at our sysadmin for being rather critical of a user who was having computer trouble. There's much nicer ways he could have said "you're doing it wrong".

He took it gracefully and nodded and agreed that, he was not in a great mood and he should not talk down to (l)users.

Then he thought for a moment, and said, (you must imagine a thick slavic accent) "Now I know why you are #debian user, you have soft heart. I am #openbsd user, so I am very cruel."


it.....looks like it "won't" be possible to move mailman to live within the chroot. this is pretty much bullshit.

what email list software do people like now nowadays?

or, do people have a clever way to solve The #Mailman On #OpenBSD problem?

It seems we're doing #introduction #introductions again.. 😀

I'm a pizza 🍕 obsessed Canadian 🇨🇦 who also occasionally does #OpenBSD 🐡 , and all without pants. I also enjoy watching TV and pondering whether my cat loves or me.. 😺

Premier patch de sécurité pour 6.2 à lancer. Faîtes péter .
Un reboot est nécessaire :