tis 2021-08-03 klockan 16:51 -0700 skrev Jim Meyering:
> On Tue, Aug 3, 2021 at 12:25 PM Paul Eggert
> wrote:
> > On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list
> > wrote:
> > > + print "\nThe SHA256 checksum is base64 encoded and not
> > > hexadecimal,\n";
> > > + print "which
On Tue, Aug 3, 2021 at 12:25 PM Paul Eggert wrote:
> On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list wrote:
> > + print "\nThe SHA256 checksum is base64 encoded and not hexadecimal,\n";
> > + print "which is the default for most checksum tools.\n\n";
>
> Perhaps this?
>
>
On 8/3/21 12:20 PM, Simon Josefsson via Gnulib discussion list wrote:
+ print "\nThe SHA256 checksum is base64 encoded and not hexadecimal,\n";
+ print "which is the default for most checksum tools.\n\n";
Perhaps this?
print "\nThe SHA256 checksum is base64 encoded, instead of the\n";
Jim Meyering writes:
> Thanks, Simon! I too am all for B64-formatted checksums.
Good, it is a trade-off between output readability and code complexity.
Aligning 'sha*sum' with OpenBSD's 'sha*' tools would be nice, and base64
support is one missing piece.
> You may want to coordinate with
On Tue, Aug 3, 2021 at 8:40 AM Simon Josefsson wrote:
> Jim Meyering writes:
>
> > Feel free to make the script generate a full fingerprint and even
> > (though it feels a little like giving up) add a checksum or two.
>
> I think checksums still serve a purpose.
>
> Many announcement e-mails are
Jim Meyering writes:
> Feel free to make the script generate a full fingerprint and even
> (though it feels a little like giving up) add a checksum or two.
I think checksums still serve a purpose.
Many announcement e-mails are OpenPGP signed (and sometimes with a
different key than the release
sön 2021-08-01 klockan 17:47 +0200 skrev Bernhard Voelker:
> On 7/27/21 11:38 AM, Simon Josefsson via Gnulib discussion list
> wrote:
> > Let's discuss and see what we can do.
> Isn't this what the "release GPG keys" on Savannah are for?
>
> Each project maintainer can set them up correctly under
On 7/27/21 11:38 AM, Simon Josefsson via Gnulib discussion list wrote:
> Let's discuss and see what we can do.
Isn't this what the "release GPG keys" on Savannah are for?
Each project maintainer can set them up correctly under "Edit public info":
On Tue, Jul 27, 2021 at 2:38 AM Simon Josefsson via Gnulib discussion
list wrote:
> Hi. Our announce-gen contains:
>
> If that command fails because you don't have the required public key,
> then run this command to import it:
> gpg --keyserver keys.gnupg.net --recv-keys $gpg_key_id
>
>
I agree that the current situation is bad and that your suggestions
would be improvement.
Particularly the part about involving the ftp-upload people. My
impression is that they're quite conservative about changing things (and
rightly so) but we really need a more-reliable distribution
Hi. Our announce-gen contains:
If that command fails because you don't have the required public key,
then run this command to import it:
gpg --keyserver keys.gnupg.net --recv-keys $gpg_key_id
Given recent OpenPGP key server issues, that doesn't work reliably any
more, and behave different
11 matches
Mail list logo
