* Helmut Toplitzer:
Hi!
Just a few remarks:
Same here.
Use unstable or testing, and apply security fixes yourself. Over
To my opinion this is a bad suggestion.
It's the only approach that will result in timely fixes of the bugs
that are important to *you*. Any vendor team will work
Hi!
Thanks Florian for your input.
It's nice to hear opinions of people inside debian, but
my remaining question is (and has already been picked up by
the release team in the release meeting minutes),
how and where the we are not able to support you state
of the security team should
Greetings,
Am Samstag, 18. Juni 2005 09:04 schrieb Helmut Toplitzer:
Hi!
Just a few remarks:
Use unstable or testing, and apply security fixes yourself. Over
To my opinion this is a bad suggestion. Maybe my last mail was a bit
unclear about this. As security is a process rather than a
Hi!
Just a few remarks:
Use unstable or testing, and apply security fixes yourself. Over
To my opinion this is a bad suggestion. Maybe my last mail was a bit
unclear about this. As security is a process rather than a state,
your systems will hardly ever have all the available
* Helmut Toplizer:
I'm also interested in other opinions as I can't suggest an already
established best-practice.
Use unstable or testing, and apply security fixes yourself. Over
time, stable (with its historic software version) will drift
considerably from upstream, which will make security
Greetings,
Am Freitag, 17. Juni 2005 10:58 schrieb Florian Weimer:
Rumors suggest that the technical foundations of security support for
sarge and woody are working again.
Nice to hear - however, a SpamAssassin-patch has to be ported to sarge.[1]
Let's see... the Sec-Announce was posted ~2
Hi!
Today I noticed a message on http://www.infodrom.org/~joey/log/?200506142140
that security-support was down during the last days.
Because this is not an official
channel I tried to verify this by the lists and s.d.o without success.
A lot of people (to my opinion) trust the way of the
7 matches
Mail list logo
