Sara Golemon <[EMAIL PROTECTED]> writes: >>> At this point, I think it would be useful for others to review the code and >>> comment on it. I'm sure there are mistakes, but I'm to deep into the code >>> to see them now. >> >> Nice work Simon! >> > Agreed! Excellent work! This doubles the options and opens the door for > inclusion in distributions which have issues with OpenSSL's licensing > scheme. This also paves the way for laying in a mini-crypto version for > use in embedded applications. > > In other news, I got the word today that I should be able to start > making commits to libssh2 once again very soon (lawyers were involved, > don't ask)...
Great! > Unless people have other things in mind, I'd like to look at rolling a > new release shortly after Daniel's completed his network blocking fixes > and feels confident about them. Hopefully by then I'll have had the > opportunity to toss in the patches I've been sitting on. The only remaining issue for me is to fix RSA libgcrypt signing, and some stress-testing and code review. Since RSA signing with libgcrypt didn't exist in earlier versions, that isn't a regression. RSA signing with OpenSSL works fine, of course, and curl appear to prefer DSA authentication anyway. As far as I'm concerned, I consider my part ready for release now. /Simon ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ libssh2-devel mailing list libssh2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libssh2-devel
