> [src's] included on the
> installation medium for reproducibility
Wherever the src.tgz, they should not be considered to be
unbreakable reproducible bitwise duplicate authentic or
traceable back to any repo since there is no provable cryptographic
chain back to same, only assertions over the bre
On Thu, Sep 17, 2020 at 09:09:26PM -0400, grarpamp wrote:
> >> > 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 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.
>
> And for R
On Thu, Sep 17, 2020 at 08:03:54PM -0400, grarpamp wrote:
> > 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.
>
> 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.
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 th
