TLS is quite a complex protocol. Crypto itself is a small part of it. OpenSSL does a good job encapsulating it. Trying to do a comparable job would be tough, and - from my point of view - pointless.
On the other hand - don't take my word: you've got a computer - get the TLS RFC from www.IETF.org and prove me wrong by adding TLS to Crypto++. Sent from my iPod On Jan 21, 2011, at 15:39, smu johnson <[email protected]> wrote: > Source code for all the ciphers for Crypto++ exist elsewhere too, so by that > reasoning, what would be the point of implementing Crypto++ at all? > > Since all the sym and asym ciphers are present in Crypto++, to me it doesn't > seem like a huge ordeal, other than adhering to a few RFCs... I'm not too > sure how much would be involved. Maybe it's a lot more work than I thought. > > On Thu, Jan 20, 2011 at 7:55 AM, Mouse <[email protected]> wrote: > Given that OpenSSL exists - what would be the point [of implementing > something as complex as TLS in Crypto++]? > > -- > You received this message because you are subscribed to the "Crypto++ Users" > Google Group. > To unsubscribe, send an email to [email protected]. > More information about Crypto++ and this group is available at > http://www.cryptopp.com. -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com.
