deraadt@ modified libexec/getty/main.c: unveil(2) in getty. This has been in snaps for more than 2 months, since I worry that a mistake in here will cause significant grief.
Before I was born, IT was struggling with physical limitations.
Now it's only struggling with its own complexity and its own past mistakes.
"Why I’m done with Chrome” https://blog.cryptographyengineering.com/2018/09/23/why-im-leaving-chrome/ #privacy
Starting with Chrome 69, logging into a Google Site is tied to logging into Chrome.
(I created a blog for occasions where 500 characters just aren't enough)
Slides for mortimer@'s talk are up:
Holy crap" ― Bob Beck, 2018.
Syspatch : correctif LDTR - CPU AMD - pour OpenBSD https://www.journalduhacker.net/s/qp8ny7/syspatch_correctif_ldtr_cpu_amd_pour https://obsd4a.net/blog/index.php?article53/syspatch-correctif-ldtr-cpu-amd-pour-openbsd #systèmed'exploitation #sécurité #openbsd
• Marc Espie, Advances in OpenBSD packages: https is a lie
• Kristaps Džonsons, OpenBSD and Diving
• Ingo Schwarze, Better documentation - on the web and for LibreSSL
• Bob Beck, Pledge and Unveil in OpenBSD
• Todd Mortimer, Removing ROP Gadgets from OpenBSD
• Bob Beck, LibTLS Tutorial for TLS beginners
• Peter Hessler, Introduction to BGP for developers and sysadmins
Intel NUC firmware contains a nasty bug with CVSS score of 8.2(!) because it allows arbitrary code execution:
“Improper input validation in firmware for Intel NUC Kits may allow a privileged user to potentially execute arbitrary code resulting in information disclosure, escalation of privilege and/or denial of service via local access.”