[19561] in Kerberos_V5_Development
Fixes for some issues found using Coverity
daemon@ATHENA.MIT.EDU (Kittel, Martin)
Mon Mar 20 13:06:26 2017
From: "Kittel, Martin" <martin.kittel@sap.com>
To: "krbdev@mit.edu" <krbdev@mit.edu>
Date: Mon, 20 Mar 2017 17:03:42 +0000
Message-ID: <23f1e43d7f284d7bb2278be66dfa9e51@sap.com>
Content-Language: en-US
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Hi,
we ship krb5 as part of some of our products and as part of our QA we run Coverity scans on all components, including krb5.
As part of these scans a number of issues were found that we think need or might need fixing. I am wondering now how to best feed back those fixes into the mainline
I have prepared a first bunch of git commits against the current HEAD from https://github.com/krb5/krb5 and tried to group them according to the Coverity findings. However I don't know whether I can feed these into krb5-bugs directly. What is the preferred way to post such patches?
Thanks and best wishes,
Martin.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
