Even in open source, responsible disclosure is generally possible.
See, e.g. Spectre/Meltdown, where they worked privately with high level Linux Kernel developers for months to have patches ready on all supported branches before they made the vulnerability public
Yeah, my calico is super careful to never extend her claws when playing with me, but she will get her claws in her toys and just look at me or flail wildly until it flys away, even with her nails trimmed 😂
Seems like a continuation of the sad state of affairs for ARM chips. Most of the allowed chips are ARM based, and most companies making ARM chips never update their kernels
At a high level, microkernels push as much as possible into userspace, and monolithic kernels keep drivers in kernel space
There are arguments for each e.g. a buggy driver can’t write into the memory space of another driver as easily in a micro kernel, however it’s running in the same security level as userspace code. People will make arguments for both sides of which is more secure
Monolithic kernels also tended to be more performant at the time, as you didn’t have to context switch between ring 0 and ring 1 in the CPU to perform driver calls - we also regularly share memory directly between drivers
These days pretty much all kernels have moved to a hybrid kernel, as neither a truly monolithic kernel nor a truly micro kernel works outside of theoretical debates
That was my assumption, but the way it was stated, I wanted to clarify there wasn’t something special about WireGuard in the way people tend to mean peer to peer
Yeah, it’s much less convenient. I prefer TOTP, but I will pick HOTP over Cisco Duo’s proprietary implementation that I can’t use without their specific app if those are my only options
And they’re allowed to start doing it again in 5 years