NetBSD Problem Report #10272
Received: (qmail 19182 invoked from network); 3 Jun 2000 10:19:36 -0000
Message-Id: <200006031019.DAA11402@digital.clock.org>
Date: Sat, 3 Jun 2000 03:19:23 -0700 (PDT)
From: "Erik E. Fair" <fair@digital.clock.org>
Reply-To: fair@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: NetBSD software releases should be PGP signed
X-Send-Pr-Version: 3.95
>Number: 10272
>Category: security
>Synopsis: NetBSD software releases should be PGP signed
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: security-officer
>State: closed
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sat Jun 03 10:20:01 +0000 2000
>Closed-Date: Sat Sep 23 23:10:41 +0000 2006
>Last-Modified: Sat Sep 23 23:10:41 +0000 2006
>Originator: Erik E. Fair
>Release: 1.4.2
>Organization:
International Organization of Internet Clock Watchers
>Environment:
System: NetBSD digital.clock.org 1.4.2A NetBSD 1.4.2A (DIGITAL) #2: Tue May 23 17:26:00 PDT 2000 root@digital.clock.org:/usr/obj/sys/arch/alpha/compile/DIGITAL alpha
>Description:
The NetBSD Project should arrange for its software to be PGP signed
to verify the integrity of any software bundle downloaded from an
arbitrary source.
The port-specific binary distributions should be signed by
the Portmaster for the port.
The source distribution should be signed by Release Engineering.
This issue is really a joint problem to be solved by the Security
Officer, the Release Engineering Team, and Core.
>How-To-Repeat:
>Fix:
1. cause PGP keys to be generated by all roles which require
the ability to sign stuff.
2. cross verify the roles by the security-officer.
3. change procedures to require signatures before release is
considered complete.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: security-officer->elad
Responsible-Changed-By: elad@netbsd.org
Responsible-Changed-When: Tue, 17 Jan 2006 16:57:05 +0000
Responsible-Changed-Why:
i'll handle it.
State-Changed-From-To: open->closed
State-Changed-By: elad@netbsd.org
State-Changed-When: Fri, 20 Jan 2006 00:05:37 +0000
State-Changed-Why:
this is being done.
From: "Erik E. Fair" <fair@netbsd.org>
To: gnats-bugs@netbsd.org
Cc: elad@netbsd.org, security-alert@netbsd.org
Subject: Re: security/10272 (NetBSD software releases should be PGP signed)
Date: Thu, 19 Jan 2006 18:33:25 -0800
This problem report should not be closed until a PGP signed release
has been put forth, and mechanisms put in place to make sure that
all subsequent releases are also signed.
Erik <fair@netbsd.org>
From: Elad Efrat <elad@NetBSD.org>
To: "Erik E. Fair" <fair@netbsd.org>
Cc: gnats-bugs@netbsd.org, security-alert@netbsd.org
Subject: Re: security/10272 (NetBSD software releases should be PGP signed)
Date: Fri, 20 Jan 2006 12:22:12 +0200
Erik E. Fair wrote:
> This problem report should not be closed until a PGP signed release
> has been put forth, and mechanisms put in place to make sure that
> all subsequent releases are also signed.
Sorry - I sent mail to releng@ etc. and got the impression it can be
closed.
I'll re-open.
-e.
--
Elad Efrat
State-Changed-From-To: closed->open
State-Changed-By: elad@netbsd.org
State-Changed-When: Fri, 20 Jan 2006 10:48:57 +0000
State-Changed-Why:
re-open as requested by eric e. fair.
From: David Maxwell <david@crlf.net>
To: gnats-bugs@netbsd.org
Cc: elad@netbsd.org, gnats-admin@netbsd.org,
security-alert@netbsd.org, fair@netbsd.org
Subject: Re: security/10272 (NetBSD software releases should be PGP signed)
Date: Fri, 20 Jan 2006 11:33:08 -0500
On Fri, 20 Jan 2006, Erik E. Fair wrote:
> This problem report should not be closed until a PGP signed release
> has been put forth, and mechanisms put in place to make sure that
> all subsequent releases are also signed.
Three releases have been signed, to date. The mechanism is in place, so
far as it is part of the releng process during release to let S-O know
when the release is ready, and request the signature.
It's probably not the 'best' system that could exist, but I think it's
sufficient.
--
David Maxwell, david@vex.net|david@maxwell.net --> Mastery of UNIX, like
mastery of language, offers real freedom. The price of freedom is always dear,
but there's no substitute. Personally, I'd rather pay for my freedom than live
in a bitmapped, pop-up-happy dungeon like NT. - Thomas Scoville
From: Daniel Carosone <dan@geek.com.au>
To: gnats-bugs@netbsd.org
Cc: elad@netbsd.org, gnats-admin@netbsd.org,
security-alert@netbsd.org, fair@netbsd.org
Subject: Re: security/10272 (NetBSD software releases should be PGP signed)
Date: Sat, 21 Jan 2006 10:32:28 +1100
--UlVJffcvxoiEqYs2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Fri, Jan 20, 2006 at 04:35:03PM +0000, David Maxwell wrote:
> Three releases have been signed, to date. The mechanism is in place, so
> far as it is part of the releng process during release to let S-O know
> when the release is ready, and request the signature.
I would like a (brief) document describing the process to be followed.
We had to reinvent it on the spot for the last release.
For example:
- does SO generate the hashes (if so from which sets of binaries via
what trust path)?
- does SO re-sign a list of hashes provided by a releng developer,
perhaps direct off the autobuild system? (this was what I did).
- what are the specific commands used to generate (and thus to
compare) hashes, so as to maintain sort stability etc.
- where are they uploaded to? (I had to find(1) them on the ftp server).
Not hard things, I just couldn't find a simple cheat-sheet document so
I'd have confidence I was doing the same thing as the last time, and
that the next person would do the same thing next time. With that,
it'd be fine to close the PR.
--
Dan.
--UlVJffcvxoiEqYs2
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
iD8DBQFD0XMMEAVxvV4N66cRAsrdAKC/ZROFS1xjwdZguTIPkEGMZFp+mwCfaoRa
sqQ/Ms3b6eOJRD2OET6kOV4=
=Pmex
-----END PGP SIGNATURE-----
--UlVJffcvxoiEqYs2--
From: Elad Efrat <elad@NetBSD.org>
To: gnats-bugs@netbsd.org, elad@netbsd.org, gnats-admin@netbsd.org,
security-alert@netbsd.org, fair@netbsd.org
Cc:
Subject: Re: security/10272 (NetBSD software releases should be PGP signed)
Date: Sat, 21 Jan 2006 01:35:15 +0200
Daniel Carosone wrote:
> I would like a (brief) document describing the process to be followed.
> We had to reinvent it on the spot for the last release.
if this had to be reinvented on the spot for the last release, *and*
it had been done for more than one release, *and* there's an open PR
for it, why this didn't come up in any of the lists? :/
-e.
--
Elad Efrat
Responsible-Changed-From-To: elad->security-officer
Responsible-Changed-By: elad@netbsd.org
Responsible-Changed-When: Thu, 02 Feb 2006 20:01:54 +0000
Responsible-Changed-Why:
security-officer should handle it
State-Changed-From-To: open->closed
State-Changed-By: elad@netbsd.org
State-Changed-When: Sat, 23 Sep 2006 19:02:12 +0000
State-Changed-Why:
i'm sorry, but i find what we do now sufficient given the tools we can use in the distribution. if you want to write a policy, write it; keeping a PR open won't make it write itself.
State-Changed-From-To: closed->open
State-Changed-By: david@netbsd.org
State-Changed-When: Sat, 23 Sep 2006 23:02:03 +0000
State-Changed-Why:
Closure was unjustified.
State-Changed-From-To: open->closed
State-Changed-By: elad@netbsd.org
State-Changed-When: Sat, 23 Sep 2006 23:10:41 +0000
State-Changed-Why:
david says its okay to close it
>Unformatted:
And closing a PR to 'clean up the database' is simply wrong.
Either the document is needed, and the PR is needed, or *something has
changed*, and
the document is no longer needed.
To me, closing a PR because it hasn't been closed yet is non-sensible. The
purpose of a PR database is to track outstanding issues. Seems to me that
this issue is still outstanding.
(Contact us)
$NetBSD: query-full-pr,v 1.51 2026/08/10 02:28:17 riastradh Exp $
$NetBSD: gnats_config.sh,v 1.10 2026/05/13 22:00:09 riastradh Exp $
Copyright © 1994-2026
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.