linux-kernel - Re: Announcement: Plans for v2.6.34-longterm

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]

Date:	Thu, 10 Nov 2011 11:54:11 -0800
From:	Greg KH <greg@...ah.com>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	"George G. Davis" <gdavis@...sta.com>,
	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	torvalds@...ux-foundation.org, stable@...nel.org,
	jason.wessel@...driver.com, Andi Kleen <andi@...stfloor.org>,
	lwn@....net
Subject: Re: Announcement: Plans for v2.6.34-longterm

On Tue, Nov 08, 2011 at 10:20:37PM -0500, Paul Gortmaker wrote:
> [Re: Announcement: Plans for v2.6.34-longterm] On 08/11/2011 (Tue 15:52) Greg KH wrote:
> 
> [...]
> 
> > Also, I would like to populate the linux-stable.git tree with the
> > missing .34-longterm releases that you have already done, care to
> > provide a git tree that I can pull from for those now?
> 
> Hi Greg,
> 
> The below pull rq should get your repo caught up on the .34
> content for my tags 8 --> 10.  You should be able to use the
> "git verify-tag v2.6.34.10" on this older content without issue
> as a double check on things.

$ git verify-tag v2.6.34.10
gpg: Signature made Sun 26 Jun 2011 09:47:42 AM PDT using DSA key ID 0D0A18AD
gpg: Good signature from "Paul Gortmaker (work) <paul.gortmaker@...driver.com>"
gpg: Note: This key has expired!
Primary key fingerprint: 2A15 067C 2C4D F8FD A89E  1882 DBE2 2294 0D0A 18AD

So I know that this was signed with an exprired key that is only
self-signed, hm, looks like that matches up with the previous releases
form you :)

thanks, now pushed out.

Hopefully you have a new key, that is in the kernel.org ring of trust,
that you will be using to sign your new releases?

thanks,

greg k-h
--
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/