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: <201110022129.11820.rjw@sisk.pl>
Date:	Sun, 2 Oct 2011 21:29:11 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Willy Tarreau <w@....eu>,
	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 11:39 AM, Willy Tarreau wrote:
> > 
> > I'm not opposed to generate a second key, but I don't really understand
> > how it solves the isolation issue. I'm not used to key signing parties
> > and am presently in the situation where I don't know whom to ping to
> > sign my key. The only thing I could do was to sign it with my old key
> > as you suggested in the initial mail on the subject :-/
> > 
> > So if at least generating a second key can save that hassle for next
> > time, I'm all in favor of making it, it just takes a few seconds.
> > 
> 
> The idea is that you have a key that you keep *extremely* secure.  When
> you go to key signing parties you only bring the public key (for
> verifying the fingerprint) but you don't sign keys until you're at your
> secure host, for example.
>
> That is the key you will use to establish yourself in the web of trust.
>  The key you will actually *use* is a child key signed with that key,
> and perhaps a handful of others.

OK, call the "extremely secure" key pair a "master".  So, in practice I'll only
take the master and child public keys (the child key signed with the master)
with me to the KS.  At the KS I'll collect the IDs and fingerprints of
people's keys to sign and I'll sign them, with the master key, when I'm back
at my secure host.  I also give my public keys (both master and child) to
people for signing.

Is this what you mean?

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