Bryan Screel 🕷💀 is a user on mastodon.social. You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

Bryan Screel 🕷💀 @canadianbryan@mastodon.social

Pinned toot

It seems we're doing again.. 😀

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

Pinned toot

You too can earn the illustrious top spot on the pizza wall of fame! 🍕brynet.biz.tm/wallofpizza.html

Pinned toot

If you donate to me please know some of that is going towards a bit of hacking OR a lot of pizza.. thx.

paypal.me/brynet
amazon.ca/gp/registry/wishlist

🇨🇦🍕

I'm excited when my cat does new interesting things like a parent is when it's their child.. 😺

Interesting technique by Todd Mortimer to reduce the number of gadgets on x86 even further: marc.info/?l=openbsd-tech&m=15

I finally just realized you can "Pin" new columns on Mastodon, keeping searches open like Tweetdeck. It's still not great though..

@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 , when e.g. Mikrotik also stealth published before hands.

Bugs show up everywhere:

marc.info/?l=openbsd-ports&m=1

This is a full disclosure of a 4 byte stack overwrite in GNU ghostscript 9.07.

Though perhaps I should have sat on it for 4 months, and registered a domain first? How does ghostsmash.com sound?

Astonishing how anyone could think this is anything BUT toxic..

"Mailed you a diff, please sit on it for 3 or 4 months while I pass it around to various government and private institutions."

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.

and regarding the embargo:

Tedu on HN: “A bunch of dudes on a linux mailing list lack the authority to prevent OpenBSD from fixing things.”

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

As '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.

I emoji'd the hell out of that, you're welcome.

It seems we're doing again.. 😀

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

Would appreciate someone sharing my previous post on Twitter, thanks!

patrick@ has committed an initial version of bwfm(4) to , a wireless driver for Broadcom FullMAC devices.

marc.info/?l=openbsd-cvs&m=150

Still lots do to...