freebsd security - Sep 2020 - 12.2R Sigs

On Thu, Sep 17, 2020 at 03:41:22PM -0400, grarpamp
wrote:
>
https://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/htdocs/releases/12.2R/signatures.xml
> 
> Is it plan that 12.x 13.x etc continue with
> provision of sig files for BETA and RC?
> If so, process can be added to releng todo docs,
> and the sig asc files pushed out to website,
> and to download areas (https, ftp, rsync, torrent, etc)
> alongside with the image datasets themselves.
> If not, the docs can make note of the labels
> to which sigs apply.
> 
They will be added with the first RC build, after the doc tree is tagged
for the final release.  Since moving the release notes and other related
documentation from base to doc, this introduced a bug in the order of
operations I have not yet figured out how to solve the right way.  In
other words, adding the signed BETA* checksums to the doc tree for the
12.1-BETA* builds, turned out to be an error.

(Also note, the signed checksums were not available for previous release
BETA builds.  And there is the PGP-signed email to stable@ that contains
them.)

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL:
<http://lists.freebsd.org/pipermail/freebsd-security/attachments/20200917/deeb3908/attachment.sig>

> They will be added with the first RC build
Yes RC* seems the latest point in timeline
to begin excercise them.
> a bug in the order of operations
> And there is the PGP-signed email to stable@ that contains
> them.
Future noting that lists do not support foreknown path schemes
for that data. Whereas repo, website and dataset locations are more
predictable and programmatic... allowing fetching, validation, etc.

There could be a commit subsequent to tags, to hold all
relavant collected metadata results, created sigs, etc of
those tagged builds.