brynet

30 ms·

301.
by brynet 8y ago
A somewhat related talk from BSDCan was Florian Obser's slaacd(8) - "A privilege separated and sandboxed IPv6 Stateless Address AutoConfiguration Daemon" https://www.openbsd.org/papers/florian_slaacd_bsdc
302.
by brynet 8y ago
These are the slides from Bob Beck (beck@'s) talk at BSDCan 2018 (Jun 8-9th), apparently missing its first page.. [0] http://www.bsdcan.org/2018/schedule/events/968.en.html Video should eventually show u
303.
by brynet 8y ago
That is the previous design which changed significantly from what's been committed today (see other comments). Github mirror, for easier review: https://github.com/openbsd/src/commit/e688c2b0648a80551cf73
304.
by brynet 8y ago
You must be jealous that we're self-hosted. ;-)
305.
by brynet 8y ago
This is not a dupe! That is a previous incarnation of RETGUARD that wasn't committed. The implementations are very different, please undo.
306.
by brynet 8y ago
OpenBSD's is per shared library, i.e: libc has a different stack cookie than your application and/or other libraries. RETGUARD however, is per function.
307.
by brynet 8y ago
It's also worth mentioning there's previous work to reduce the amount of polymorphic gadgets in the instruction stream, including a new framework for clang: https://marc.info/?l=openbsd-cvs&m=151123332419798&am
308.
by brynet 8y ago
This uses OpenBSD's random-data memory [0][1] feature, which was used by the stack protector to provide per shared object cookies. RETGUARD is more than just an improved stack protector, as explained in the commit message it protects f
309.
Retguard: An improved stack protector for OpenBSD(marc.info)
187 points by brynet 8y ago|69 comments
310.
by brynet 8y ago
Of course. If you promise "exec", then you're allowed exec. This allows pledge to be in software that otherwise would be impossible, for example text editors, and other shells. It still reduces attack surface, as the shell it
311.
by brynet 8y ago
> seccomp-bpf doesn't let you follow pointers, so you can't even implement most pledge() restrictions in it. That's not even the least of it, it's impossible to implement the ratcheting down semantics of pledge() usin
312.
by brynet 9y ago
Text editors are shells, remember that if your program executes a text editor.
313.
by brynet 9y ago
It was probably for testing, but that platform supports partitioning up the hardware through LDOMs, which OpenBSD supports as both a host and guest. https://www.tedunangst.com/flak/post/OpenBSD-on-a-Sun-T5120 (Not
314.
by brynet 9y ago
OpenBSD's also had arm64 support since 6.1, with 6.3 coming out early this month introducing SMP support. https://www.openbsd.org/arm64.html https://www.openbsd.org/61.html https://www.openb
315.
by brynet 9y ago
C++ support is pretty good with base Clang 5, OpenBSD is using the libc++ standard library and libc++abi (FreeBSD uses PathScale's libcxxrt). The situation with debuggers is another story, the base version of gdb is outdated (GPLv2 ver
316.
by brynet 9y ago
For the sake of easier application software, yes. sndio is the higher level of abstraction. There is a lower level API, audio/mixer/midi(4), but they exist as only ioctl(2) calls.
317.
by brynet 9y ago
On Linux, this is implemented on top of ALSA, which is the native Linux kernel sound API.
318.
by brynet 9y ago
This is the native audio subsystem used by OpenBSD, it includes a library (libsndio) and a privsep server (sndiod). There was a massive successful undertaking to write backends for most 3rd party audio software in the ports tree, things lik
319.
by brynet 9y ago
I probably wouldn't trust implementing important network speaking services as a shell script, potentially running as root. OpenBSD's acme-client [0] is a fork of Kristaps Dzonsons' project (formerly letskencrypt), it's a
320.
by brynet 9y ago
OpenBSD had no idea who the other insiders were, only that it received a patch from the researcher, and the go-ahead to fix an important security problem. Suggesting that the correct response was to sit on the patch for months leaving users
321.
by brynet 9y ago
That's not how it happened, that's the narrative you're spinning, certainly. https://twitter.com/vanhoefm/status/921425715903463425
322.
by brynet 9y ago
You know, it's really tiring that people keep up with the same old shtick every time the topic of embargoes and OpenBSD come up. OpenBSD followed [0] the original embargo from the KRACK researcher, he gave OpenBSD the go-ahead to commi
323.
by brynet 9y ago
The implementation is of course different, but the workaround is the same, separating the user/kernel pages tables. One key difference is that OpenBSD doesn't have to deal with 32-bit binary compatibility [0] and such, and also ha
324.
by brynet 9y ago
Yes. I use OpenBSD on both my desktop and laptop daily, I also use it for my home firewall and personal server. Full disclosure: OpenBSD developer.
325.
by brynet 9y ago
More OpenBSD slides/papers and the full video from the event are online: https://www.openbsd.org/events.html GConfs channel: https://www.youtube.com/user/GConfs/videos EuroBSDcon: https:&#x2
326.
by brynet 9y ago
This is from an excellent talk Stefan Sperling (stsp@) gave at EuroBSDcon this week! Livestream segment: https://youtu.be/8wuW8lfsVGc?t=21489
327.
by brynet 9y ago
OpenBSD has been expanding the fork+exec model throughout its source tree, since the OpenSSH preauth work done by Damien Miller, many more followed. The list includes bgpd/ldpd/eigrpd/smtpd/relayd/ntpd/httpd&#x
328.
by brynet 9y ago
"ROP attack methods are impacted because existing gadgets are transformed to consist of '<gadget artifacts> <mangle ret address> RET'. That pivots the return sequence off the ROP chain in a highly unpredictable an
329.
by brynet 9y ago
Here's a better mail archive link: https://marc.info/?l=openbsd-tech&m=150317547021396&w=2 EDIT: Thanks mods? :-)
330.
Retguard: OpenBSD/Clang(marc.info)
139 points by brynet 9y ago|33 comments

More ›