openssh unix dev - Mar 2017 - FreeBSD Coverity scan issues in OpenSSH -> how to contribute back patches?

Hi,
	FreeBSD runs a Coverity static analysis scan on a weekly basis to determine
whether or not there are issues within the software that we ship with FreeBSD.
After the latest upgrade (to 7.4p1) I noticed that there are some new issues in
SSH.
	We (FreeBSD) have some local modifications to OpenSSH that are maintained for
features or behavior (I believe), so I?ll need to go through our patchset and
determine whether or not the issues are in our modifications or in the upstream
code.
	That being said, I was wondering how you prefer for patches to be submitted
back upstream, in particular, is there a process that I should follow for
signing off on patches, contributing, etc?
Thank you for your time,
-Ngie

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20170308/6ae94ac2/attachment.bin>

On Thu, Mar 9, 2017 at 8:28 AM, Ngie Cooper (yaneurabeya)
<yaneurabeya at gmail.com> wrote:
> That being said, I was wondering how you prefer for patches to be submitted
back
> upstream, in particular, is there a process that I should follow for
signing off on patches, contributing, etc?
Trivial patches can be sent to this list (be aware that non-text
attachments will be dropped), for non trivial patches
https://bugzilla.mindrot.org/ is preferred.

Thanks.

-- 
Darren Tucker (dtucker at zip.com.au)
GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860  37F4 9357 ECEF 11EA A6FA (new)
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

> On Mar 8, 2017, at 15:23, Darren Tucker <dtucker at zip.com.au>
wrote:
> 
> On Thu, Mar 9, 2017 at 8:28 AM, Ngie Cooper (yaneurabeya)
> <yaneurabeya at gmail.com> wrote:
>> That being said, I was wondering how you prefer for patches to be
submitted back
>> upstream, in particular, is there a process that I should follow for
signing off on patches, contributing, etc?
> 
> Trivial patches can be sent to this list (be aware that non-text
> attachments will be dropped), for non trivial patches
> https://bugzilla.mindrot.org/ is preferred.
Hi Darren,
	Perfect! Thanks so for the info :).
All the best,
-Ngie
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20170308/9ae8d905/attachment.bin>