(picrin tls)

[omasanori]

For better or worse, we use TLS for daily communications nowadays, so will we. (I will tackle this after launching Unicode support, but of course you can do it if you can't wait until I finally start to do. :smile:) Here are some references:

• OpenSSL docs
• OpenSSL wiki
• libtls man page
  • The APIs from OpenBSD folks are dramatically simplified from powerful-but-complicated OpenSSL's. We should learn from this.
• s2n usage guide
  • This new SSL/TLS library from AWS Labs is also well worth learning.
• SSL libraries comparison table in the cURL site
• Gauche's TLS library
• The Guile binding for GnuTLS
• openssl egg for Chicken Scheme

[KeenS]

I'd like to have simpler one. I don't think picrin should be able to generate certificates.

[omasanori]

@KeenS I'm on your side. Kitchen-sink approaches should be avoided, IMHO, especially on security.

Also, I think general cryptography-related things should be provided by, say (picrin crypto), (picrin rsa) or so on, if we want them. Proposal: the role of (picrin tls) is providing network connection on TLS (and/or DTLS.)