| 1 |
I just use this one liner: |
| 2 |
|
| 3 |
glsa-check --list 2> /dev/null | grep '\[N\]' |
| 4 |
|
| 5 |
and manually merge the packages listed each morning when I get to |
| 6 |
work. Takes no time at all. |
| 7 |
|
| 8 |
On 9/20/05, W.Kenworthy <billk@×××××××××.au> wrote: |
| 9 |
> Not strictly correct - "glsa-check --list" does tell you if the system |
| 10 |
> is vulnerable: it highlights the entry in red, and sets [N] for the |
| 11 |
> entry. --test is just a shortcut that allows individual tests, or with |
| 12 |
> "all" lists only those that fail the test. --list|grep "\[N" is |
| 13 |
> actually better as it includes the description as well. |
| 14 |
> |
| 15 |
> BillK |
| 16 |
> |
| 17 |
> |
| 18 |
> On Tue, 2005-09-20 at 08:53 -0500, Brian G. Peterson wrote: |
| 19 |
> > On Tuesday 20 September 2005 07:44 am, Marius Mauch wrote: |
| 20 |
> > > > Brian Peterson wrote: |
| 21 |
> > > > The glsa-check tool is basically useless |
| 22 |
> > > > (as of gentoolkit-0.2.1_pre7), as it shows all GLSAs rather than just |
| 23 |
> |
| 24 |
> ... |
| 25 |
> |
| 26 |
> > > a long time. Also make sure you don't confuse the --list option with |
| 27 |
> > > the --test option. |
| 28 |
> > |
| 29 |
> > Sure. |
| 30 |
> > |
| 31 |
> > glsa-check --test |
| 32 |
> > |
| 33 |
> > run by itself, does nothing except give a command summary. |
| 34 |
> > |
| 35 |
> > glsa-check --list |
| 36 |
> > |
| 37 |
> > lists *all* unapplied GLSAs, regardless of whether the package is installed on |
| 38 |
> > the running system. |
| 39 |
> > |
| 40 |
> > So, you need to --test each and every GLSA to see if it applies to your |
| 41 |
> > system. |
| 42 |
> > |
| 43 |
> > glsa-test --test all |
| 44 |
> > |
| 45 |
> > gives a list of GLSAs that apply to a running system, but then provides no |
| 46 |
> > details about these GLSAs in the list. |
| 47 |
> > |
| 48 |
> |
| 49 |
> -- |
| 50 |
> gentoo-security@g.o mailing list |
| 51 |
> |
| 52 |
> |
| 53 |
|
| 54 |
-- |
| 55 |
gentoo-security@g.o mailing list |
Archives