From: ludo@gnu.org (Ludovic Courtès)
To: Martin Castillo <castilma@uni-bremen.de>
Cc: 31444@debbugs.gnu.org
Subject: [bug#31444] 'guix health': a tool to report vulnerable packages
Date: Mon, 14 May 2018 11:07:10 +0200 [thread overview]
Message-ID: <87r2mea9mp.fsf@gnu.org> (raw)
In-Reply-To: <f7776a30-f164-3b78-5164-3df5d7d84718@uni-bremen.de> (Martin Castillo's message of "Mon, 14 May 2018 10:06:46 +0200")
Hello,
Martin Castillo <castilma@uni-bremen.de> skribis:
> On 14.05.2018 00:15, Ludovic Courtès wrote:
>> [...] shadow@4.6 is available and fixes CVE-2018-7169, consider ugprading
> ^typo
>
>> Should we satisfy ourselves with the current approach in the meantime?
>
> Release early and often would say yes. But I'm not an experienced developer.
OK.
> I have the feeling that guix lint does not cache the CVEs it fetches. I
> think it should.
It does: it caches them in ~/.cache/guix/http and then uses
‘If-Modified-Since’ to avoid re-fetching the database if the cached copy
is up-to-date.
Now the 2018 database obviously keeps changing, so caching helps when
you’re running ‘guix lint’ several times in a row (say while reviewing
packages), but it doesn’t help much if you run it once a day or less.
Also, it fetches the whole database for a year. I think they publish
diffs as well, but using them seems tricky.
Ludo’.
next prev parent reply other threads:[~2018-05-14 9:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-13 22:15 [bug#31444] 'guix health': a tool to report vulnerable packages Ludovic Courtès
2018-05-14 8:06 ` Martin Castillo
2018-05-14 9:07 ` Ludovic Courtès [this message]
2018-05-14 16:49 ` Nils Gillmann
2018-05-15 7:24 ` Ludovic Courtès
2020-09-18 22:43 ` zimoun
2020-09-25 16:34 ` Ludovic Courtès
2023-07-21 16:44 ` Maxim Cournoyer
2023-09-08 16:25 ` Ludovic Courtès
2023-09-09 22:14 ` Maxim Cournoyer
2023-09-13 19:58 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2mea9mp.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=31444@debbugs.gnu.org \
--cc=castilma@uni-bremen.de \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).