[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080516215854.GB3801@openwall.com>
Date: Sat, 17 May 2008 01:58:54 +0400
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: OpenSSH key blacklisting
On Fri, May 16, 2008 at 05:10:43PM -0300, Gustavo De Nardin (spuk) wrote:
> If this is going to be accepted as a more general solution, it'd be good to
> allow also for local, admin-maintened, blacklists, not just upstream
> maintened (and automatically updated).
I agree that this might be desirable functionality, but unfortunately it
has a price - we'd have to maintain two file parsers and lookup
algorithms (perhaps binary and indexed, and text and sequential) or an
additional program to update the binary file. (If we only create the
binary file ourselves, then that program can be a quick hack - maybe
even a Perl script.)
Has there been any demand for such blacklists, prior to the Debian issue
coming up? If not, then this additional feature is probably not worth
implementing right away.
Alexander
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
