OpenBSD Journal

Call for testing: pledge(2) in -current

Contributed by pitrh on from the pledged to unbreak dept.

As noted in a previous story, the new pledge(2) privilege restriction syscall (formerly known as tame(2)) has been inserted into large swathes of the base system. Theo de Raadt (deraadt@) asked tech readers to look closely for any failures:

Many will have observed that pledge(2) usage is being pushed into the source tree at a very rapid pace.

I'd like if everyone looks in their dmesg logs for pledge errors. But please don't immediately mail a report! Instead, look for if someone else reports an error in the same command. If noone else does within 24 hours, then please inform tech@, or myself and semarie@

We're doing the best we can to test every usage case of the programs we modify, but there are going to be some glitches, hopefully all found & fixed quickly.


Oh and what has pledge become? A very simple annotation system call a program can do, to tell the kernel what it will do henceforth. If it breaks the rules, it gets killed (and you see those pledge messages). It's a new kind of security system, just wait and see... :)

You heard the man: If you're already running snapshots or intending to start doing so, your reports will be much appreciated.

(Comments are closed)


Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]