7 Aug
2014
7 Aug
'14
6:35 a.m.
Debian's lynx(1) supports SSL out of the box:
How fortunate, then, that I am not using Debian. (Though I have many
other reasons.)
Someday I may
try to find enough documentation to build my own
implementation which doesn't depend on crap like that, but so far
every time I've looked I've rapidly ended up at pay-to-play
"standards", which I of course consider completely unacceptable -
indeed, I think the IETF should never have let HTTPS in the door
until that was fixed.)
If you're looking to implement the actual crypto,
you're doing it
wrong. It's a fairly major endeavour and very easy to make critical
mistakes that ruin the crypto. Anyway, AFAICS, all of the sailient details are right
there in the
RFCs or other public domain sources
Most RFCs are not public domain.
for anybody who still wants to go ahead and write
their own
implementation.
I'll have to have another look sometime, then. Fuzzy memory says it
depended on X.something or some such from the ISO.
[TLS] protects against passive network sniffing, which
is the most
common threat, especially now Wifi is so heavily-used.
I don't care about passive network sniffing. Once packets leave my
border I consider them exposed to the world anyway.
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B