* Cyril Bouthors:
On 27 Mar 2006, Cyril Bouthors wrote:
Which debsecan options do I have to use?
3 weeks have passed. Do you have any news?
I tried to explain that I have trouble understanding your
expectations: You tell debsecan to create reports against the sarge
suite, but at the same
On 27 Mar 2006, Cyril Bouthors wrote:
Which debsecan options do I have to use?
3 weeks have passed. Do you have any news?
--
Cyril Bouthors
pgpJNdvF0qBOc.pgp
Description: PGP signature
To sum this up:
1) I'm running sarge
2) I have installed few sid packages where I need recent features
thanks to /etc/apt/preferences (mainly php5 and it's deps)
3) both sarge and sid packages are the latests packages of the
official distributions
4) I need to run debsecan every
Package: debsecan
Version: 0.4.1
Severity: normal
libcurl3/unstable is reported as insecure but it's not:
web1:~# debsecan --suite sarge --only-fixed
CVE-2006-1061 libcurl3 (fixed)
web1:~# dpkg -l libcurl3 debsecan
Desired=Unknown/Install/Remove/Purge/Hold
|
* Cyril Bouthors:
web1:~# debsecan --suite sarge --only-fixed
CVE-2006-1061 libcurl3 (fixed)
There is an upgrade for sarge (actually a downgrade), but not one
for sid. I don't think debsecan's output is incorrect in this case.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
On 20 Mar 2006, Florian Weimer wrote:
There is an upgrade for sarge (actually a downgrade), but not one
for sid. I don't think debsecan's output is incorrect in this case.
Debsecan should only report insecure and fixed packages with invoked
with --only-fixed.
Since libcurl 7.15.2-3 has no
* Cyril Bouthors:
On 20 Mar 2006, Florian Weimer wrote:
There is an upgrade for sarge (actually a downgrade), but not one
for sid. I don't think debsecan's output is incorrect in this case.
Debsecan should only report insecure and fixed packages with invoked
with --only-fixed.
It does.
7 matches
Mail list logo
