Hi Simon: Does Werner Koch have a website where one can find libgcrpyt ? The following are the versions of the TLS related libraries I currently used and the versions you recommended.
Library Current Recommended ------- -------- --------------- gsasl 0.2.20 1.4.4 gnutls 1.6.3 2.8.6 libgcrypt 1.2.4 1.4.5 libgpg-error 1.5 1.8 libtasn1 0.3.10 ? First, do any of the recommended versions have external interfaces changes ? Second, is there any reason to upgrade libtasn1, and if so, what version do you recommend ? Best Regards, Paul R. Simon Josefsson wrote: > Paul Romero <[email protected]> writes: > > > Hi Simon: > > > > Thank you for answering my questions so thoroughly, and I complement > > you on the clarity of the UC Linux porting menus on your website. > > What versions of libgcrypt and the the standard GSASL libraries > > do you consider most stable ? I am particularly curious about > > libgnutls and those parts related to TLS. > > The safest bet (both for libssh2 and generally) is to use libgpg-error > 1.8 (you may need to provide --enable-static since they disabled it by > default) and libgcrypt 1.4.5. GnuTLS 2.8.6 is stable, as is GNU SASL > 1.4.4. If you need recent TLS renego stuff, you may want to try just > released GnuTLS 2.10.0 but I wouldn't label it stable at this point. > > /Simon > > > Best Regards, > > > > Paul R. > > > > > > Simon Josefsson wrote: > > > >> Paul, what Peter and Daniel has said so far should have answered all > >> your questions, but let me add some more things for clarity. > >> > >> Libssh2 has not been ported to uClinux in the sense that libssh2 > >> provides the integration glue to make it part of a normal uClinux build > >> environment (i.e., make menuconfig + dep + all). Doing so should be > >> relatively easy, and as you know I have posted recipes on this available > >> from http://josefsson.org/uclinux/ for a bunch of projects already, and > >> it should be very easy to adapt for example the gnutls or gsasl recipes > >> (which depends on libgpg-error + libgcrypt, like libssh2 does) for > >> libssh2 as well. > >> > >> Fortunately, libssh2 does not require anything more than what GNU SASL > >> or GnuTLS requires from Libgcrypt: SSH2 uses standard crypto algorithms > >> like MD5, SHA1, HMAC, AES, RSA and DSA. > >> > >> /Simon > >> _______________________________________________ > >> libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel > > > > -- > > Paul Romero > > > > RCOM Communications Software > > > > Phone/Fax: (510)339-2628 > > E-Mail: [email protected] > > > > > > _______________________________________________ > > libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel > _______________________________________________ > libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel -- Paul Romero RCOM Communications Software Phone/Fax: (510)339-2628 E-Mail: [email protected] _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
