3 ms·
The History of a Security Hole
- raresp 8y agoForbidden You don't have permission to access /wp/the-history-of-a-security-hole/ on this server.
- Kovah 8y agohttps://web.archive.org/web/20180903022426/http://www.os2museum.com/wp/the-history-of-a-security-hole/ https://web.archive.org/web/20180903022426/http://www.os2mus...
- cperciva 8y agoWorth mentioning: FreeBSD had an equivalent bug on amd64, because the I/O permissions array got confused with a pointer to said array. This was fixed in April 2005 -- and was discovered by someone saying "that's weird, I can startx as a regular user even though the X server binary isn't setuid...".
- ezoe 8y agoSeriously? OpenBSD developers didn't consider the C compiler adds padding to the structure?
- tedunangst 8y agoNo, we've never heard about this padding of which you speak.
- anyfoo 8y agoRead the article. It goes into detail on what possibly went wrong and how multiple issues likely accumulated.
- userbinator 8y agoHow this works in emulators/VMs is also of interest --- because it could be another way in which code running on real hardware differs from that in VM, and can be used to distinguish.