Previously Jean-Marc Boursot wrote:
> Like the last postfix DoS? Am I wrong or there wasn't any bugtraq
> report for that?
There was, Wietse announced it to bugtraq.
Wichert.
--
_
/[EMAIL PROTECTED] This space intention
Previously Jean-Marc Boursot wrote:
> Like the last postfix DoS? Am I wrong or there wasn't any bugtraq
> report for that?
There was, Wietse announced it to bugtraq.
Wichert.
--
_
[EMAIL PROTECTED] This space intention
Previously Jean-Marc Boursot wrote:
> Like the last postfix DoS? Am I wrong or there wasn't any bugtraq
> report for that?
There was.
Wichert.
--
_
/[EMAIL PROTECTED] This space intentionally left occupied \
| [EMAIL PR
On Thursday 13 December 2001 20:41, Wichert Akkerman wrote:
> Previously Javier Fern?ndez-Sanguino Pe?a wrote:
> > I guess a public database could be useful both for
>
> We have a private database (well, a status-file in which we keep
> track of things). A public database can't be used since we
Previously Jean-Marc Boursot wrote:
> Like the last postfix DoS? Am I wrong or there wasn't any bugtraq
> report for that?
There was.
Wichert.
--
_
[EMAIL PROTECTED] This space intentionally left occupied \
| [EMAIL PR
On Thursday 13 December 2001 20:41, Wichert Akkerman wrote:
> Previously Javier Fern?ndez-Sanguino Pe?a wrote:
> > I guess a public database could be useful both for
>
> We have a private database (well, a status-file in which we keep
> track of things). A public database can't be used since w
On Thu, Dec 13, 2001 at 08:41:38PM +0100, Wichert Akkerman wrote:
> Previously Javier Fern?ndez-Sanguino Pe?a wrote:
> > I guess a public database could be useful both for
>
> We have a private database (well, a status-file in which we keep track
> of things). A public database can't be used s
Previously Javier Fern?ndez-Sanguino Pe?a wrote:
> I guess a public database could be useful both for
We have a private database (well, a status-file in which we keep track
of things). A public database can't be used since we frequently get
private info we can't share.
Wichert.
--
_
On Thu, Dec 13, 2001 at 08:41:38PM +0100, Wichert Akkerman wrote:
> Previously Javier Fern?ndez-Sanguino Pe?a wrote:
> > I guess a public database could be useful both for
>
> We have a private database (well, a status-file in which we keep track
> of things). A public database can't be used
How do the Debian Security team currently follow the vulnerabilities
posted
upstream? I guess that's easy when the upstream maintainer (or the one that
found the
bug) tells Debian's team before posting. But what if somebody posts in bugtraq a
security issue around a software available at
Previously Javier Fern?ndez-Sanguino Pe?a wrote:
> I guess a public database could be useful both for
We have a private database (well, a status-file in which we keep track
of things). A public database can't be used since we frequently get
private info we can't share.
Wichert.
--
How do the Debian Security team currently follow the vulnerabilities posted
upstream? I guess that's easy when the upstream maintainer (or the one that found the
bug) tells Debian's team before posting. But what if somebody posts in bugtraq a
security issue around a software available at
12 matches
Mail list logo
