[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: libssh code contributions


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.



Mark Riordan
Sr Software Developer
T. 608.824.3632 | mriordan@xxxxxxxxxxxx

-----Original Message-----
From: Gearoid Murphy [mailto:gearoid.murphy@xxxxxx] 
Sent: Friday, March 09, 2012 10:29 AM
To: libssh@xxxxxxxxxx
Subject: libssh code contributions


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.

  - Gearoid

libssh code contributionsGearoid Murphy <gearoid.murphy@xxxxxx>
Archive administrator: postmaster@lists.cynapses.org