Hali
Ugy erted: haltot nyomtatok rajta?!
T.
> -Original Message-
> From: Moritz Muehlenhoff [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 29, 2006 9:29 PM
> To: debian-security-announce@lists.debian.org
> Subject: [SECURITY] [DSA 1082-1] New Linux kernel 2.4.17 packages fix
> several vuln
Florian Weimer wrote:
> * Martin Schulze:
>
> > Disabled again. The problem lies somewhere "between" saens and you.
> > It's fine on saens locally.
>
> While the bogus A record should be gone now that saens is down, you
> should still remove saens from the list of authoritative name servers
> fo
* Martin Schulze:
> Disabled again. The problem lies somewhere "between" saens and you.
> It's fine on saens locally.
While the bogus A record should be gone now that saens is down, you
should still remove saens from the list of authoritative name servers
for debian.{org,com,net} and ipv6.debian
severity 340008 grave
thanks
I have increased the severity of this bug as overwriting the SSL key is
data loss. This affects the recent security upgrade in sarge which makes
it especially visible. It is perhaps worth reissuing this erratum having
fixed this problem. If there is interest in this I
Neil McGovern wrote:
> I'm forwarding this over to debian-admin, as they're the people who can
> fix this :)
I had already answered Bjoern:
Ah yes, the named on saens went alive again. That was not planned.
Disabled again. The problem lies somewhere "between" saens and you.
It's fine on saens
I'm forwarding this over to debian-admin, as they're the people who can
fix this :)
Neil
On Mon, May 29, 2006 at 10:57:06AM +0200, Bjørn Mork wrote:
> First, not so serious, but still an error: All debian.org servers have
> a mismatch between the delegation and the served data, adding
> samosa.de
Jan Luehr wrote:
> Is fix for 005 and 006 on its way?
The fixes you're talking about [1] don't seem complex at first sight,
as the patches for Drupal 4.6.6 [2,3] are pretty simple. So, I guess
the security team will be able to handle this without problems :)
If you can't wait, just try to apply t
First, not so serious, but still an error: All debian.org servers have
a mismatch between the delegation and the served data, adding
samosa.debian.org as autoritative (I know samosa is listed as primary
in the SOA record, but it need not, and should not, be listed as
autoritative as long as it's no
8 matches
Mail list logo
