public inbox for gentoo-security@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kevin Bryan <bryank@cs.uri.edu>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] No GLSA since January?!?
Date: Fri, 26 Aug 2011 14:08:38 -0400	[thread overview]
Message-ID: <20110826180838.GA21426@zen.cs.uri.edu> (raw)
In-Reply-To: <4E57D29B.5070603@gocept.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Although I like having the summary information about what the
vulnerability is, if I'm only reading them for packages I have
installed, then a reference of some kind would suffice.

I'd be fine even if it was just a new variable in the .ebuild file that
somehow indicated which versions it was a fix for, reusing the syntax
for dependency checking.  A reference to the CVE or gentoo bug reference
would be good, too:

SECURITY_FIXES="<www-plugins/adobe-flash-10.1.102.64"
SECURITY_REF="CVE:2010-2169 http://..."
SECURITY_BUG="343089"
SECURITY_IMPACT="remote"

Then would be most of the work the committer needs to do is right there
in a file they are modifying anyway.

The portage @security set could also look for and evaluate these tags,
instead of parsing the GLSA's.

Note on the impact variable: make a few easy to understand tags:
local
remote
remote-user-assist
denial-of-service
...

- --Kevin


On Fri, Aug 26, 2011 at 07:06:35PM +0200, Christian Kauhaus wrote:

> Am 26.08.2011 18:55, schrieb Alex Legler:
> > Compared to other distributions, our advisories have been rather detailed with
> > lots of manually researched information. I'm not sure if we can keep up this
> > very high standard with the limited manpower, but we'll try our best.
> 
> I see the point. I think it would be an achievement over the current situation 
> (which is: no current GLSAs at all) to send out less detailed GLSAs. Even 
> something short as: "$PACKAGE has vulnerabilities, they are fixed in $VERSION, 
> for details see $CVE" would be immensely helpful.
> 
> Is the any viable way to get it at least to this point? Probably the largest 
> part of such a task could be automated. This would lift the burden from the 
> security maintainers.
> 
> Regards
> 
> Christian
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iEYEARECAAYFAk5X4SYACgkQ6ENyPMTUmzpTLwCeIrikkC82ZC/YMALUD3AUOG71
GQ0An02FoagrOJSU4kFQ8RUP+q/1+zQn
=/kf5
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2011-08-26 18:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 16:12 [gentoo-security] No GLSA since January?!? Christian Kauhaus
2011-08-26 16:43 ` Christoph Jasinski
2011-08-26 16:57   ` JD Horelick
2011-08-26 17:18     ` Daniel A. Avelino
2011-08-26 17:57       ` Alex Legler
2011-08-26 18:22         ` Daniel A. Avelino
2011-08-26 18:44           ` Alex Legler
2011-08-26 19:27             ` Daniel A. Avelino
2011-08-26 16:55 ` Alex Legler
2011-08-26 17:06   ` Christian Kauhaus
2011-08-26 18:00     ` Joost Roeleveld
2011-08-26 18:07       ` Alex Legler
2011-08-26 19:30         ` Joost Roeleveld
2011-08-26 18:08     ` Kevin Bryan [this message]
2011-08-26 18:40       ` Alex Legler
2011-08-26 20:02         ` Kevin Bryan
2011-08-26 20:40           ` Daniel A. Avelino
2011-08-26 22:27           ` Alex Legler
2011-08-26 23:38             ` Daniel A. Avelino
2011-08-26 18:41       ` Daniel A. Avelino
2011-08-27  8:49       ` Christian Kauhaus
2011-08-27 12:13         ` Rich Freeman
2011-08-27 12:34           ` Tobias Heinlein
2011-08-27 13:06             ` Rich Freeman
2011-08-27 13:34               ` Tobias Heinlein

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110826180838.GA21426@zen.cs.uri.edu \
    --to=bryank@cs.uri.edu \
    --cc=gentoo-security@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox