|
|
|
|
|
|
by fkooman
3576 days ago
|
|
|
It seems to make more sense to just have ONE that can accommodate all those scenarios in a secure way. One doesn't solve bloat by introducing more bloat. I'd say more can be won by removing e.g. ASN.1 and X.509 for certificate handling and encoding that are a very difficult (impossible?) to get right and switch to something simple that solves the 99% use case of current TLS. |
|
|
Those two are part of my plaintext-offenders list, like SMTP. They make life equally painful for both man and machine.