We’re excited to announce the third Radiant Award recipient, Claudio Jeker.
When we at ISRG think about the greatest threats to Web security today, the lack of Border Gateway Protocol (BGP) security might top our list. Claudio's passion for networking, his focus on security, and his talent as a software developer are enabling him to make great contributions to fixing this and other Web security problems. In particular, he is making great contributions to OpenBSD and OpenBGPD.
commit from today  makes IP stack more paranoid. Up to now OpenBSD
implemented so called 'weak host model' . The today's commit alters
that for hosts, which don't forward packets (don't act as routers).
Your laptops, desktops and servers now check packet destination address
with IP address bound to interface, where such packet is received on.
If there will be mismatch the packet will be discarded and 'wrongif'
counter will be bumped. You can use 'netstat -s|grep wrongif' to
display the counter value.
It is understood the behavior, which has been settled in IP stack since 80's,
got changed. firstname.lastname@example.org (or email@example.com) wants to hear back from you,
if this change breaks your existing set up. There is a common believe this
change won't hurt majority (> 97%) users, though there is some non-zero risk,
hence this announcement is being sent.
from the hard-as-nails-(in-the-coffin-of-exploit-techniques) dept.
Theo de Raadt (deraadt@) has
code for a new exploit-prevention mechanism:
Repurpose the "syscalls must be on a writeable page" mechanism to
enforce a new policy: system calls must be in pre-registered regions.
We have discussed more strict checks than this, but none satisfy the
cost/benefit based upon our understanding of attack methods, anyways
let's see what the next iteration looks like.
This is intended to harden (translation: attackers must put extra
effort into attacking) against a mixture of W^X failures and JIT bugs
which allow syscall misinterpretation, especially in environments with
polymorphic-instruction/variable-sized instructions. It fits in a bit
with libc/libcrypto/ld.so random relink on boot and no-restart-at-crash
behaviour, particularily for remote problems. Less effective once on-host
since someone the libraries can be read.
from the ecstatic-nostrils dept.
Florian Obser (florian@) has
code to give
a flexible approach to resolving strategies:
sbin/unwind : resolver.c resolver.h
Instead of only considering if a resolving strategy is dead, works or
validates, measure how well it is doing.
Next up in our hackathon series from p2k19 is one from Stefan Sperling (stsp@),
My main goal for the p2k19 hackathon was 9260 device support in iwm(4).
Firmware updates for previous device generation were an important
prerequisite step. One day before p2k19, the oldest generation of hardware
supported by the iwm(4) driver was switched to latest available firmware images.