On Wed, Oct 26, 2005 at 08:18:57PM +0200, Florian Weimer wrote:
On Tue, Oct 25, 2005 at 05:35:19PM +0200, Florian Weimer wrote:
Is the issue described below already on your radar screen? I couldn't
find it in the relevant files. AFAICT, no CVE name has been assigned.
Its the first I've
On Tue, Oct 25, 2005 at 05:35:19PM +0200, Florian Weimer wrote:
Is the issue described below already on your radar screen? I couldn't
find it in the relevant files. AFAICT, no CVE name has been assigned.
Its the first I've seen of it, but that doesn't mean much.
Which GIT tree is the commit
On Tue, Oct 25, 2005 at 05:35:19PM +0200, Florian Weimer wrote:
Is the issue described below already on your radar screen? I couldn't
find it in the relevant files. AFAICT, no CVE name has been assigned.
Its the first I've seen of it, but that doesn't mean much.
Which GIT tree is the
Is the issue described below already on your radar screen? I couldn't
find it in the relevant files. AFAICT, no CVE name has been assigned.
commit 4717ecd49ce5c556d38e8c7b6fdc9fac5d35c00e
Author: Patrick McHardy [EMAIL PROTECTED]
Date: Mon Jul 18 06:52:50 2005 +0200
[PATCH] Fix
4 matches
Mail list logo