linux-kernel - Re: 463 kernel developers missing!

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <489061E0.5000501@keyaccess.nl>
Date:	Wed, 30 Jul 2008 14:43:12 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Adrian Bunk <bunk@...nel.org>
CC:	Jon Smirl <jonsmirl@...il.com>, Paul Mundt <lethal@...ux-sh.org>,
	James Morris <jmorris@...ei.org>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	Dave Jones <davej@...hat.com>, Theodore Tso <tytso@....edu>,
	Simon Arlott <simon@...e.lp0.eu>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 463 kernel developers missing!

On 30-07-08 09:24, Adrian Bunk wrote:

> Whether Jon's patch is a good idea one might discuss

<discussion>it is not</discussion>

> but as soon as someone puts an email address into a kernel commit
> Google will anyway find it:

It will and note this is not a privacy issue "as such" at least for me 
(for rmk rewriting addresses is a privacy issue, directly or via law, 
and whether or not needed in this specific example or not)

Google find lots of things, most of which do not end up at the top of 
the search results. This address I'm now posting with is definitely 
public (or I wouldn't be posting with it) but given that it shouldn't 
even exist at the moment I have been careful for some time to put a 
relay address into anything which I intend to be long lived.

Since outside its non-existence it's the best address I have available I 
do still use it though. This is not a problem, since all mailing list 
archives go to great trouble to obscure addresses anyway and my gmail 
address will feature as the "most public" from it being in _content_. 
Sometimes others use this address in content as well but given that they 
can't be expected to know about any of my peculiar mail fetishes I'm not 
going to whine about it and it's not a practical problem anyway.

Then Jon comes along, puts _all_ addresses in content inside a hugely 
publicized, widely web-indexed tree and fucks it up.

Anyways... yesterday I had to turn the fan on my monitor to keep it from 
damage in this bloody furnace while today it's some 5 degrees cooler and 
the fan's aimed at me again so I'll stop cursing and shouting now. But 
still a damn bad idea.

Rene.
--
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/