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] [day] [month] [year] [list]
Date:	Tue, 15 Oct 2013 17:20:51 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [GIT PULL] device tree reverts and fix against v3.12-rc5

On Tue, Oct 15, 2013 at 2:43 PM, Grant Likely <grant.likely@...retlab.ca> wrote:
>
> *unless you find the signed tag questionable. You'll notice that I
> have a shiny-new gpg key which is currently only signed by my old key.
> Yes. Bad. I left it very late to create a new key, the old key is now
> expired, and I haven't gotten anyone else to sign the new one yet. It
> will be properly signed real-soon-now and I can resend the pull
> request when that happens if you don't like this one.

Hmm. Why did you do a 2048-bit key? Your old one was 4k..

Since you haven't gotten anybody to sign the new key yet, may I
suggest throwing this one away and doing a new 4096-bit key?

Yeah, yeah, I know, my *own* key is just 2048 bits, because back when
I created it we were discussing using various hardware tokens, and
some of them (at the time) didn't do more than 2k. So I shouldn't
really complain when somebody else does a 2k key. But that was a few
years ago, and I claim stupidity (I never did use a hardware token).

Anyway, pulled, since it was all signed by your previous key, and I
guess 2k is still supposed to be "good enough".

                Linus
--
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