OpenBSD security features: Difference between revisions

Revision as of 12:08, 17 May 2018

Revision as of 20:38, 19 May 2018

Line 44:

OpenBSD has a history of providing its users with [[Full disclosure (computer security)|full disclosure]] in relation to various bugs and security breaches detected by the OpenBSD team.<ref>{{cite web |url=http://bsd.slashdot.org/story/00/12/11/1455210/theo-de-raadt-responds |title=Theo de Raadt Responds |last=Miller |first=Robin |publisher=[[Slashdot]] |date=December 11, 2000 |deadurl=no |archiveurl=https://web.archive.org/web/20110728031830/http://bsd.slashdot.org/story/00/12/11/1455210/Theo-de-Raadt-Responds |archivedate=July 28, 2011 |accessdate=May 16, 2014 }}</ref> This is exemplified by [[OpenBSD#Slogan|the project's slogan]]: "Only two remote holes in the default install, in a heck of a long time!"

In OpenBSD 5.3, support for [[full disk encryption]] was introduced.<ref>{{cite web|title=OpenBSD 5.3|url=http://www.openbsd.org/53.html|website=OpenBSD|accessdate=May 26, 2016}}</ref>

OpenBSD 5.8 introduced the first work on a new process-containment facility, originally named tame, later renamed to pledge.<ref>{{cite web|title=pledge() - a new mitigation mechanism|url=https://www.openbsd.org/papers/hackfest2015-pledge|website=OpenBSD|accessdate=May 19, 2018}}</ref> Since the original introduction, applications and ports have been changed to support this new technique.

<!-- This needs more. -->