linux-kernel - Re: OT: linux-kernel list and greylisting

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1160301643.5522.1.camel@shinybook.infradead.org>
Date:	Sun, 08 Oct 2006 11:00:43 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Gerhard Mack <gmack@...erfire.net>
Cc:	Mariusz Kozlowski <m.kozlowski@...land.pl>,
	Michael Obster <lkm@...ter.org>, linux-kernel@...r.kernel.org
Subject: Re: OT: linux-kernel list and greylisting

On Mon, 2006-10-02 at 09:41 -0400, Gerhard Mack wrote:
> If you absolutely need to graylist (I have my doubts about it's 
> effectiveness) then whitelist vger.kernel.org. 

Any half-sensible greylisting implementation would be exempting
vger.kernel.org as soon as it's observed to retry its _first_ mail,
anyway.

Greylisting done _stupidly_, where it keeps delaying mail from a given
host even after it's known to queue and retry, would be a problem. But
done sensibly it's fine.

-- 
dwmw2

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/