Re: Known vulnerabilities left open in Debian?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings,
Am Montag, 22. März 2004 21:20 schrieb Nathan Eric Norman:
> On Mon, Mar 22, 2004 at 10:01:14PM +0100, Jan Lühr wrote:
> > Greetings,
> >
> > Am Montag, 22. März 2004 21:16 schrieb Bryan Allen:
> > > On Mar 22, 2004, at 2:57 PM, Jan Lühr wrote:
> > > > Cron is another example - the be honest, the debian security team
> > > > seems to be
> > > > crippled by the debian release policy.
> > > > Because of this policy debian stable is insecure by definition.
> > >
> > > http://security.debian.org/
> > >
> > > You are asked on install if you would like to use it. The default is
> > > "yes".
> >
> > <irony>
> > I did so, but I didn't get all necessary patches - did I do something
> > wrong? </irony>
>
> You opened a bug on cron and supplied links to the patches you're
> talking about, right? For some reason I don't see any open bugs on
> cron with your name on them.
Sorry, there was a misunderstanding between Florian and me (in a previous
e-mail correspondence). I'd like to cancel my statements about cron - my
apologies.
Keep smiling
yanoszu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iQIVAwUBQF9eqtAHMQ8GQaYRAQLh6hAAnDcBcOT/bn31OTvtgzibj26bOQgP22Q5
j93+L0+odxV1FKjLFiE3vsAAaBzut8Px5/9r84yHUNm/LfPhPJWlASrtsXbG9S9Z
4FO8FkQWR6/lj1ejpqRK7aGUAEsb7jwDzJbcXKwzNrtK56BekSxClRatXc8B6nL9
x3MDvrV0coYDXTF7zTezAP4xaWbuzcBwdUOQu41HsxvYRbUy1jNeO9lCeNXQWn2M
tjTlKibzRHNQJd6Cao/JWhN4ZObdYFW1GqJCNl3ZnmN0PZptr0TlCABlstDH9Z3s
16vWs+lk0nyctM0yyYtkSiKaw8XMMkiZAgixkvP0s9MEUsEKz9fXM+cW9juv38Pf
1mRDLeQwF+KCDeF2cBzT5Q24YRypzLbEoqoZBMFhY0HnDdi1V7/B1vm3tprchz+Q
eWcKdlJ8uM1LPMNDMOlM5W1tyI34ZAnVuo9etgOeUCFgSFa6I25Cj+ZiY0m5kyER
6mIELZixHzQHv33QC4e3zGU5vJPjNAwMic6wSB/aThy1hUxAQHp1Mu2qeBokigZN
jC5xvwohEb0kLkK/izfvUz6mMH3kkSVjU4dbHP4Eni4OjAH23UnVVnqafQnpz3ni
4fJTfGNWPPQeAtVaov2Jg/ashwO0OeEh83kFmWoxedgLVOFkRRGcTiRHdfhFwzMh
7yivSHXY+G8=
=v8DJ
-----END PGP SIGNATURE-----
Reply to: