FS#71879 - [tcsh] use signed release, https, sha256
Attached to Project:
Community Packages
Opened by T.J. Townsend (blakkheim) - Friday, 20 August 2021, 19:09 GMT
Last edited by Brett Cornwall (ainola) - Sunday, 14 August 2022, 18:04 GMT
Opened by T.J. Townsend (blakkheim) - Friday, 20 August 2021, 19:09 GMT
Last edited by Brett Cornwall (ainola) - Sunday, 14 August 2022, 18:04 GMT
|
Details
Description:
Attached diff switches the tcsh package to use a PGP-signed release downloaded over HTTPS. It also switches from MD5 to SHA256. |
This task depends upon
Closed by Brett Cornwall (ainola)
Sunday, 14 August 2022, 18:04 GMT
Reason for closing: Fixed
Additional comments about closing: tcsh-6.24.01-2 has this patch. Thanks for your work, and, more importantly, your persistence!
Sunday, 14 August 2022, 18:04 GMT
Reason for closing: Fixed
Additional comments about closing: tcsh-6.24.01-2 has this patch. Thanks for your work, and, more importantly, your persistence!
Comment by
T.J. Townsend (blakkheim) -
Wednesday, 15 September 2021, 21:28 GMT
Comment by
T.J. Townsend (blakkheim) -
Wednesday, 09 March 2022, 17:10 GMT
Comment by
George Rawlinson (rawlinsong) -
Monday, 14 March 2022, 01:00 GMT
Comment by
George Rawlinson (rawlinsong) -
Wednesday, 23 March 2022, 00:51 GMT
Comment by
T.J. Townsend (blakkheim) -
Saturday, 13 August 2022, 22:05 GMT
Comment by
T.J. Townsend (blakkheim) -
Saturday, 13 August 2022, 22:06 GMT
Ping?
Ping
I’ve just picked up maintenance of this package, I’ll have a look
when I can.
Due to the GPG keyservers being completely inaccessible, I don't
think there's any point in using the signed release. The author
hasn't replied to my queries regarding where to find the public
key either.
Public key now available on keyserver and I have an updated diff.
...And here it is.