openssh unix dev - Jan 2011 - Contributing Code to OpenSSH

Hello everyone,

I have found a bug (memory leak) in the OpenSSH code for which I would like to
submit a patch; how do contributors go about the submission process?  The
website does not appear to afford such an opportunity to give back.

Thank you,
David

Hi David,

David and Jamie Gosselin wrote:
> I have found a bug (memory leak) in the OpenSSH code for which I
> would like to submit a patch; how do contributors go about the
> submission process?
I suggest to use CVS or mercurial to check out the current source
code, fix the bug, then use either cvs diff or hg commit + hg export
to generate a patch file. Send that patch file to this mailing list
for review and inclusion in the codebase.

Another approach is to file a bug in the web based bugzilla bug
tracker for the project.


//Peter

On 01/23/2011 12:45 PM, David and Jamie Gosselin wrote:
> Hello everyone,
>
> I have found a bug (memory leak) in the OpenSSH code for which I
> would like to submit a patch; how do contributors go about the
> submission process?  The website does not appear to afford such an
> opportunity to give back.
You can either mail the patch to this list (note that it must be sent as 
either a mime type of text or inline otherwise it will be stripped by 
the list server) or via http://bugzilla.mindrot.org (both of these are 
covered at http://www.openssh.com/report.html, along with a couple of 
other things).

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
     Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.