From: Henrik.Carlqvist@deadspam.com   
      
   On Sun, 15 May 2022 16:52:59 +0000, Rich wrote:   
   > Also, verify you got the data without something glitching by checking   
   > the files using the CHECKSUMS.md5 file before you try moving to a stick   
   > or booting what you download.  If the checksums match, you can be   
   > reasonably sure you have the same bytes as the original file, so any   
   > failure to boot is something that is occurring on your end after the   
   > download.   
      
   If you want to be really sure that the files are OK you could also check   
   the gnupg signature of the file CHECKSUMS.md5 by running:   
      
   gpg --verify CHECKSUMS.md5.asc   
      
   That should give you an output looking something like:   
      
   gpg: assuming signed data in `CHECKSUMS.md5'   
   gpg: Signature made Sun May 15 22:23:44 2022 CEST using DSA key ID   
   40102233   
   gpg: checking the trustdb   
   gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model   
   gpg: depth: 0  valid:   1  signed:   1  trust: 0-, 0q, 0n, 0m, 0f, 1u   
   gpg: depth: 1  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 1f, 0u   
   gpg: next trustdb check due at 2038-01-19   
   gpg: Good signature from "Slackware Linux Project   
   "   
      
      
   However, before running gpg like that you will need to import the   
   Slackware public key to your keyring. First, you should get the public   
   key from a trustworthy source, best would be if you could get it from an   
   old purchased original Slackware media.   
      
   The file GPG-KEY from the media is imported by:   
      
   gpg --import GPG-KEY   
      
   If you are sure that the GPG-KEY has not been tampered with you should   
   also sign it:   
      
   gpg --edit-key security@slackware.com   
   gpg (GnuPG) 1.4.23; Copyright (C) 2015 Free Software Foundation, Inc.   
   This is free software: you are free to change and redistribute it.   
   There is NO WARRANTY, to the extent permitted by law.   
      
      
   pub  1024D/40102233  created: 2003-02-26  expires: 2038-01-19  usage: SCA   
                        trust: full          validity: unknown   
   sub  1024g/4E523569  created: 2003-02-26  expires: 2038-01-19  usage: E   
   [ unknown] (1). Slackware Linux Project    
      
   gpg> sign   
   Your current signature on "Slackware Linux Project   
   "   
   has expired.   
   Do you want to issue a new signature to replace the expired one? (y/N) y   
      
   pub  1024D/40102233  created: 2003-02-26  expires: 2038-01-19  usage: SCA   
                        trust: full          validity: unknown   
    Primary key fingerprint: EC56 49DA 401E 22AB FA67  36EF 6A44 63C0 4010   
   2233   
      
        Slackware Linux Project    
      
   This key is due to expire on 2038-01-19.   
   Are you sure that you want to sign this key with your   
   key "Henrik Carlqvist " (94066DCB)   
      
   Really sign? (y/N) y   
      
   gpg> quit   
   Save changes? (y/N) y   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)