Re: signing release files

2014-06-17 Thread Kenneth Westerback
On 17 June 2014 07:37, Nick Holland wrote: > On 06/17/14 02:40, Jiri B wrote: >> On Mon, Jun 16, 2014 at 05:47:03PM -0400, Nick Holland wrote: >>> [diff to easily allow different keys] >>> >>> I think focus has been lost. >>> >>> What's the point of signing releases? To say "This came from the >>

Re: signing release files

2014-06-17 Thread Nick Holland
On 06/17/14 02:40, Jiri B wrote: > On Mon, Jun 16, 2014 at 05:47:03PM -0400, Nick Holland wrote: >> [diff to easily allow different keys] >> >> I think focus has been lost. >> >> What's the point of signing releases? To say "This came from the >> OpenBSD project". >> >> Why? To make sure your

Re: signing release files

2014-06-16 Thread Jiri B
On Mon, Jun 16, 2014 at 05:47:03PM -0400, Nick Holland wrote: > [diff to easily allow different keys] > > I think focus has been lost. > > What's the point of signing releases? To say "This came from the > OpenBSD project". > > Why? To make sure your release is a pure, untampered with version.

Re: signing release files

2014-06-16 Thread Nick Holland
On 06/16/14 15:56, Jiri B wrote: On Sun, Jun 15, 2014 at 05:09:20PM -0400, Ted Unangst wrote: On Sun, Jun 15, 2014 at 14:12, Aaron Gomez wrote: I looked at the signify command but I can't figure out how to check all the files and then create the SHA256.sig. I tried "signify -S -s myprivatekey.

Re: signing release files

2014-06-16 Thread Jiri B
On Sun, Jun 15, 2014 at 05:09:20PM -0400, Ted Unangst wrote: > On Sun, Jun 15, 2014 at 14:12, Aaron Gomez wrote: > > I looked at the signify command but I can't figure out how to check all > > the files and then create the SHA256.sig. > > > > I tried "signify -S -s myprivatekey.sec -m SHA256 -x SH

Re: signing release files

2014-06-15 Thread Kevin Chadwick
previously on this list Aaron Gomez contributed: > What do I need to do to make it so the installer can verify my newly > created release files? You can check the iso and type no or simply copy the SHA256.sig from the mirror into the same folder as the sets. If you choose http method it will wor

Re: signing release files

2014-06-15 Thread Ted Unangst
On Sun, Jun 15, 2014 at 14:12, Aaron Gomez wrote: > I looked at the signify command but I can't figure out how to check all > the files and then create the SHA256.sig. > > I tried "signify -S -s myprivatekey.sec -m SHA256 -x SHA256.sig" but > that just created a file SHA256.sig with the following

signing release files

2014-06-15 Thread Aaron Gomez
Hi All, I follow stable and yesterday I updated my system and then built a release for the base system and xenocara. I then created an install CD but when I went to upgrade another system using the CD, as it's about to install the sets I get the following message: "Directory does not contain SHA2