Hacker News new | past | comments | ask | show | jobs | submit login

It does a lot of things it really shouldn't be doing. I recommend you watch Bob Beck's talk about LibreSSL[1] (Ted's there too).

[1]: https://www.youtube.com/watch?v=GnBbhXBDmwU




The discussion of Big Endian amd64 support at 38:50 in that video is hilarious and scary.


That whole discussion on the slide from 38:50 is hilarious and scary.

"You can't turn off the debugging malloc but you can turn off sockets"

"If the size of socklen_t changes while your program is running, OpenSSL will cope"


Big Endian AMD64? Cisco support? iOS compiled big endian to little endian? WTF!? Lmao crazy on so many levels...

EDIT to add:

Epic observation: "The good news is: if the size of socklen_t changes while your program is running, then... (other guy) OpenSSL will cope." Lol.


If I remembered correctly Cisco was using PowerPC and it was big endian. I do believe that might be a factor in the madness.


Probably thought it would be easier to write a converter than figure out how to change their code without breaking it. That's my guess. Wouldn't have even been a problem if Intel/AMD had chosen the best endianness. ;)


I love how OpenBSD is consistent about using Comic Sans in their material.

They clearly haven't lost their sense of humour despite working with this terrible material. Lesser men would turn cynical over half the things they have to endure :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: