Scott, I just checked the CVE ID's on mitre, and as of now ( 11:18 AM PST 1/26/17 ) they are all listed as 'reserved' and don't have any information about the issue. NVD shows the same information. In either case, it seems like an extra hoop to jump through to have to go to a third party site to find a commit #, when the third party chooses to release the information.
On Thu, Jan 26, 2017 at 10:53 AM, Scott Neugroschl <scot...@xypro.com> wrote: > The CVE itself contains the commit info. Find it at cve.mitre.org > > > > *From:* openssl-users [mailto:openssl-users-boun...@openssl.org] *On > Behalf Of *Ethan Rahn > *Sent:* Thursday, January 26, 2017 10:40 AM > *To:* openssl-users@openssl.org > *Subject:* [openssl-users] Should openssl publish the commit #'s that > fixed each CVE? > > > > Hello, > > > > When looking a the latest security announcement, something that I notice > is that it's hard to find the actual commits that fixed an issue. If you > search git.openssl.org you can find some of them if they are mentioned in > the change message, but it still requires some active effort. > > > > Would it be a good idea for openssl to publish the commit(s) that fixed > each CVE? It would make it easier to see what changed, which is great for > > a.) backporting. > > b.) satisfying curiosity of armchair cryptographers. > > c.) better assessing an issue. > > > > Cheers, > > > > Ethan > > -- > openssl-users mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users > >
-- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
