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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 2 Oct 2011 20:14:27 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>
Subject: Re: kernel.org status: establishing a PGP web of trust

On Sunday, October 02, 2011, H. Peter Anvin wrote:
> On 10/02/2011 04:54 AM, Rafael J. Wysocki wrote:
> > On Sunday, October 02, 2011, H. Peter Anvin wrote:
> > 
> > Hmm.  That doesn't seem very practical if someone doesn't live close
> > to any other core kernel developers.
> > 
> 
> You probably know enough people (including myself) that would be willing
> to sign your key over the phone.  That's part of giving yourself
> sufficient time.

Well, then I propose that people create two new key pairs instead of
just one and take both of them to the KS for signing.  Afterwards, one
of them will be used for development and the other one's private key
will be kept in a safe place (without any online access), so it can be
used readily if the first pair is lost or compromised somehow.

Perhaps the second pair should have a longer life time.

> > What number of signatures on the key will be regarded as sufficient?
> > 
> >> We can work out specific details at KS.
> > 
> > Well, the KS is going to be busy time this year I suppose. :-)
> > What about people who haven't been invited to the KS?
> 
> Well, KS is still a place where we can discuss these kinds of policies;
> we can't be a perfect democracy and in fact have never even attempted to.

That doesn't seem to address my question directly.  Never mind. :-)

FYI, I am going to keep my current tree at github up to date even after
kernel.org has become operational again.  If every tree Linus pulls from
is hosted in two different locations, so that they can be used for double
checking the tree's integrity, that will improve the security of data
we want to protect much more than making access to kernel.org alone so
much more difficult.

Thanks,
Rafael
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ