-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEQY2JmAMM0Uo2gGJ8smIYX2HgPJ4FAlz1pAsACgkQsmIYX2Hg
PJ5DEA/+MjOg7QBn+XZ+vTJUP+RfyF8KFgcAcJ45J2l6qVx/ySM7KXPVamC9QD/r
myHXDhM9MXCJork580GcE1Lb/7dzwdC3SvBCl/XjDJbrzKPPq6yuRZuNTxLJL2Bt
r9/FNq0h40pBMnzupj/a9S4s96OgueXUFrf/uLhT2v0f4/GhQ9HDvRGC5i4cQx1/
gsnBOIGaGtDSD/LAx6jE4DLVn4pgxcultzNae1vj4FVVcDT5o1bVZjlL/7p5/xUq
xWIicOG9ADZr9zhKVr2dvxHpnHFWIylkkPVBLKmA40aTyggBaUNWT6meohf7NEld
4fb9/UxjKuRNqVv/9Xu0kK2/P4OzDLSbEKTX9T+bh2uCgqY33RATk7yUfs86gRpd
cPe5CndPl5fStrvvAAXV2cEWa9gkRpeR8Qr/XjJQT1mW1VCtRMVVyJBhLlccwGVT
1I3MYDw2FV4jZVGmLxHjO9ILmdlTLgFmsoHERUM+/MoF1D54MskknbTK+Yqpk3Td
0Xj8gkP/juKc/5Sjhf2J1ZnJbC75osN1yeDHZ9ediuRW6Kfmf+alQ2fYcX0bOosv
p1TGIBPRctM2eqk34OjHltEY7Q2pj0sUkF2Bb3xlE/55QRs6Ur8mbJQoJT1fU8Yy
LzMArE2ktd7vMZjmZl04oXRqIqg5hC5lRQdQPGaCy3AziOMlNKs=
=idZN
-----END PGP SIGNATURE-----
> 4. jun. 2019 kl. 00:32 skrev Josef Pospisil <j_pospisil@outlook.com>:
>
> Can someone be that kind and explain to me if the whole code of OpenBSD
> was checked at least once since the openBSD was founded? That there are
> no backholes like i was describing?
Code auditing (aka 'reading the code like the devil reads the Bible') is very much part of the project lifestyle. A good place to start for taking in how the project works is the project website itself, start at the top with the project goals page http://www.openbsd.org/goals.html and work your way through at your own pace.
There are of course other, less official propaganda presentations like my own «OpenBSD and you» (https://home.nuug.no/~peter/openbsd_and_you/) that will if nothing else show you highlights I thought important while composing a user group presentation (and some minor brushups since then), with links to further info.
- Peter
—
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
No comments:
Post a Comment