https://bugzilla.novell.com/show_bug.cgi?id=393186
User meissner@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393186#c20
--- Comment #20 from Marcus Meissner
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.
Not that I know of. I just imagined somewhere could have a policy like "all keys must have X bits" or ".. X or larger" X being a non-default size. So even if the database would be customized to have the extra keys, auto-upgrading it (which would be desirable) could be a problem. Not a big deal to me, personally. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.