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
| ||
|
Date: Tue, 10 Jul 2007 08:15:14 +0200 From: Oliver Neukum <oliver@...kum.org> To: "Satyam Sharma" <satyam.sharma@...il.com> Cc: "Kunai, Takashi" <kunai@...ux-foundation.jp>, holzheu@...ux.vnet.ibm.com, "Rob Landley" <rob@...dley.net>, "Andrew Morton" <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, lf_kernel_messages@...ux-foundation.org, mtk-manpages@....net, jack@...e.cz, randy.dunlap@...cle.com, gregkh@...e.de, pavel@....cz, tim.bird@...sony.com, gh@...ibm.com, arjan@...radead.org, sam@...nborg.org, jengelh@...putergmbh.de, hpa@...or.com, joe@...ches.com, auke-jan.h.kok@...el.com, hansendc@...ibm.com, davem@...emloft.net, Valdis.Kletnieks@...edu, kenistoj@...ibm.com, schwidefsky@...ibm.com, heiko.carstens@...ibm.com Subject: Re: Documentation of kernel messages (Summary) Am Dienstag, 10. Juli 2007 schrieb Satyam Sharma: > But, I'm not sure they'd be operating against a known target -- I don't > really know what exactly would be hashed, but if it's kernel printk() > messages (the format string, obviously), then please remember that > new messages would get added all the time, and unless we're also > willing to change the hash function every time a printk() gets added > to the kernel (whew!) it's going to be a problem -- especially because > we don't really want to generate new hash functions for every kernel > version / or for every kernel build, because we'd obviously like the > same error message to hash to the same value across versions. I suggest exactly that you build a new hash function for every build. Nothing but your translating demon need ever see it. We build a new System.map every time and it doesn't hurt. Regards Oliver - 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/
Powered by blists - more mailing lists