Jim Starkey wrote: ..........
As for the library search, there are a surprising number of crypto libraries out there. Some were ruled by license, since I need a library embeddable in a commercial product. Others were rules out by language (C or C++ is a requirements; Delphi need not apply). The libraries I looked at in depth were:
* Crypto++ (actually started here). Upside: it works. Downside: gigantic footprint, code is inscrutable, and documentation non-existent. * SSLeay. Very low level API. Written in "historical" C, so conversion to C++ would be a major problem as would taming it dynamic memory allocation for embedded use. It also requires attribution in product documentation. This isn't a disqualifier, but is a nuisance. * Netscape Security Services (NSS). The download has 3,133 files. I opened the box, looked in, closed the box, and ran. * LibTomCrypt. Written in C with C++ conditionals. Extremely modular. Controlled by an explicit customization header and designed for embedding. A couple of trivial problems converting to C++ porting to AMD64. Superb documentation *and* internal comments. And no templates.
For the time being, I've settled LibTomCrypt. Performance isn't an issue for my usage, so I haven't compared performance. His license is "The library is free for all purposes without any express guarantee it works.",Tom St Denis, [EMAIL PROTECTED], http://libtomcrypt.org.
Hi,
What do you think cryptlib written in C? I found it is more stable than Crypto++ libraries.
With regarding to LibTomCrypt, does it have API support SSH protocol directly?
Sam.
