[EMAIL PROTECTED](Stephen Gran) 19.09.05 08:58
>This one time, at band camp, Rainer Zocholl said: >> Hello >> >> it happend that i can't update clamav on a box. >> >> That was caused by the line >> >> # cat apt.conf >> Apt::Default-Release "stable"; >> >> >> >> aptitude remove clamav clamv-base ...., >> aptitude clean >> aptitude install >> >> shows: >> >> Get:1 http://security.debian.org stable/updates/main libclamav1 >> 0.84-2.sarge.2 [252kB] >> Get:2 http://security.debian.org stable/updates/main clamav-base >> 0.84-2.sarge.2 [154kB] >> Get:3 http://security.debian.org stable/updates/main >> clamav-freshclam 0.84-2.sarge.2 [2171kB] >> >> Why is such an old and broken version still on *security* ? >> >> Current version is 0.87(!) and all version below 0.86 are remote >> exploidable. >Debian backports security fixes, rather than upgrading to new versions >with new bugs. Jepp. >All of the remote bugs have been fixed >in 0.84-2sarge.2. How can i "check"/validate that debians security 0.84 is as secure as "volatile" 0.86/0.87? >(except a few that are only just fixed in 0.87) Em,.. jepp. >If you want to >use a newer version of the software, please have a look at >http://volatile.debian.net I know that. Thanks. But a way to determine what "flaws" are fixed would be nice. Rainer---<=====> Vertraulich // // <=====>--------------ocholl, Kiel, Germany ------------ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
