Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #222397
| From | Victor Sudakov <vas@sibptus.ru> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: debsecan does not report a vulnerability? |
| Date | 2020-05-12 06:00 +0200 |
| Message-ID | <A5ufg-45B-1@gated-at.bofh.it> (permalink) |
| References | <A3L0R-4o1-1@gated-at.bofh.it> <A4ZuN-2dT-1@gated-at.bofh.it> <A5aTf-OQ-3@gated-at.bofh.it> <A5tjb-3xg-1@gated-at.bofh.it> <A5tCx-3SX-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
David Wright wrote: > > On Monday, 11 May 2020 00:14:02 PDT Victor Sudakov wrote: > > > > > > What do you use to track vulnerabilites in your Debian hosts? What's the > > > general approach? Do we just rely upon unattended-upgrade to fetch and > > > install patched packages for us? > > > > Running unattended upgrades is generally a recommended way to keep the system > > up-to-date. It minimizes the time from update being published to installed. > > > > I got interested and installed debsecan on my laptop. Here is what man says: > > > > Much like the official Debian security advisories, debsecan's > > vulnerability tracking is mostly based on source packages. > > > > So it seems that it only knows about issues that were reported to source > > packages. The next logical step would be to grep bugtracker to see if this CVE > > was even reported to that package. > > Or you could check /usr/share/doc/openssl/changelog.Debian.gz > though it only shows up in version 1.1.1d-0+deb10u3 of course. > > $ zcat /usr/share/doc/openssl/changelog.Debian.gz | head I'm looking for a more generic tool to audit all installed packages and report vulnerable ones. > $ > > (I'm not sure why the OP is still running the previous version.) I downgraded it on purpose, to find a tool which would detect and report this package as vulnerable. The "debsecan" turned out to be the wrong tool. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49@fidonet http://vas.tomsk.ru/
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-05-07 11:30 +0200
Re: debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-05-10 17:20 +0200
Re: debsecan does not report a vulnerability? Ihor Antonov <ngor@antonovs.family> - 2020-05-10 21:10 +0200
Re: debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-05-11 09:20 +0200
Re: debsecan does not report a vulnerability? Ihor Antonov <ihor@antonovs.family> - 2020-05-12 05:00 +0200
Re: debsecan does not report a vulnerability? David Wright <deblis@lionunicorn.co.uk> - 2020-05-12 05:20 +0200
Re: debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-05-12 06:00 +0200
Re: debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-05-12 05:50 +0200
motivation for switching to Debian? (was: Re: debsecan does not report a vulnerability?) Victor Sudakov <vas@sibptus.ru> - 2020-05-12 05:50 +0200
Re: debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-07-07 09:30 +0200
Re: debsecan does not report a vulnerability? l0f4r0@tuta.io - 2020-07-07 23:30 +0200
Re: debsecan does not report a vulnerability? Victor Sudakov <vas@sibptus.ru> - 2020-07-08 04:20 +0200
csiph-web