Gearoid, As I recall, the preferred way is to log a feature request at https://red.libssh.org/ and then attach a unified diff source code path file to the request.
Regards, Mark ------------------------------ Mark Riordan Sr Software Developer T. 608.824.3632 | [email protected] www.IpswitchFT.com -----Original Message----- From: Gearoid Murphy [mailto:[email protected]] Sent: Friday, March 09, 2012 10:29 AM To: [email protected] Subject: libssh code contributions Hi, We've updated our local build of libssh with some simple additions for exposing client public key functions. This allows developers to implement arbitrary types of public key authentication without having to go into the guts of the (elegantly written) libssh code. We've also extended the examples with an x509 public authentication demo using OpenSSL x509 functions on Linux and WinCrypt certificate functions on Windows. How do we go about pushing this code back into the mainline?, I vaguely recall some references to a certification process that's required before making commits. Thanks - Gearoid
