[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Sun, 30 Dec 2012 17:12:02 -0700
From: Kurt Seifried <kseifried@...hat.com>
To: oss-security@...ts.openwall.com
CC: Henri Salo <henri@...v.fi>
Subject: Re: Isearch insecure temporary files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/30/2012 09:16 AM, Henri Salo wrote:
> On Sat, Dec 29, 2012 at 08:53:42PM -0700, Kurt Seifried wrote:
>> One random thought, might it be worth adding structured data to
>> CVE that basically says when the issue was made public/reported
>> to the upstream and when upstream 1) acknowledged it (if ever)
>> and then they patched it (if ever) and when they shipped a fixed
>> version (if ever). Obviously then you could simply parse for the
>> time between date reported and date acknowledged/patched/fixed
>> and see how healthy/responsive the upstream is.
>
> Yes, that would be really useful data with CVEs. OSVDB is
> collecting that already. That is not easy task btw.
>
> - Henri Salo
Maybe iDefense or iSIGHT would be willing to share (I know the data
exists, I helped collect it for 9.5 years =). One thing I'm really
noticing as a good rule of thumb:
1) if a project has security@ or similar email and responds timely,
this is good.
2) if a project has security@ or similar email and never responds then
they tend to fix things but not overly quickly/consistently
3) if a project has no security@ or similar email chances are they
don't handle security issues very gracefully (big surprise hey).
Basically if the first result in Google for "report security issue to
X" isn't useful chances are it's not going to end well. The best part
is not all vendors provide a secure means to submit vulnerabilities
(e.g. please provide a PGP encryption key for email, and if you use a
web form please use HTTPS!).
- --
Kurt Seifried Red Hat Security Response Team (SRT)
PGP: 0x5E267993 A90B F995 7350 148F 66BF 7554 160D 4553 5E26 7993
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQ4NhSAAoJEBYNRVNeJnmTJ0AQALDRGqpIgLWLyYvc44pBHf5Z
QkgqUPtXFG/okXm7MwffXZz9y7B9h/Fotgvi8dr4X4CuVVeJ3Wiz/8+P2E/qc2TJ
HXNlVMxSvzqvLMNT/XmKnNVHfQAWdQD3a5y6oRZSPA07ZUSXfoWwbQbHCq8LR8ba
XjyMDkjN1ial0ICFJ5bQseKWHliwGSGk9eCxGR0u3Ok2Bp8lzPuCCSXEwnW2XI2c
8bIdbI73NAnfccDJp5701871VPuj+Z81LhN2SDpysZ+I6E/2dIIv1hhaM9y1ivwG
ZjsSVpHeO1wukr5CLH5e7NjiNlaoiqL92yQxI67Pv9RRVk5ib+D8nDVK1aKMrlYi
jwBFgBz13WPB8bZzfoSStACnxGTSVVVfHxixQmnxOrFopY40jGhAp1J98udRz9xq
dlo4w6j8H0FO810ZSAmITv3zie4rJ/jtQULus78FOsRjpJurPFldze7KQjNY4oNZ
Rjww62SWCho4pZVBEznU0YiwxvF0NICCtlAt4JzyFtEVFXK87isnattXAr36jLIQ
FA7pgUBDt2oREzojOaNuepNz3htTaIGnYlQbBRSBByZsTl3QlKJ6cFPK1mfuXMVL
qZXhCmAguF/zPFdUK4hFsrMVHyK6yCAI9c5+TAoLM6H70Qs2+fHUuCU3YS9n20kr
lUkiKelZDWZYCFb7ESF/
=6Z7z
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
