public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "René Berber" <rene.berber@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: weird error gpg
Date: Fri, 24 Jun 2022 11:21:00 -0500	[thread overview]
Message-ID: <c94b40df-6460-12dc-3f1b-f287cda15430@gmail.com> (raw)
In-Reply-To: <201387757.8392172.1656086113460@mail.yahoo.com>

On 6/24/2022 10:55 AM, Jim McNamara via Cygwin wrote:

> $ gpg --verify fedora.asc Fedora-KDE-Live-x86_64-36-1.5.iso
> gpg: can't handle text lines longer than 19995 characters
> gpg: Signature made Fri May  6 10:21:35 2022 EDT using RSA key ID 38AB71F4
> gpg: BAD signature from "Fedora (36) <fedora-36-primary@fedoraproject.org>"
> 
> I am having a difficult time. I think they are breaking into my computer.
> They made it so I can't verify files.
> 
> Is there any way I can fix it so that this error goes away?

Start by checking gpg itself.


$ which gpg
/usr/bin/gpg

$ gpg --version
gpg (GnuPG) 1.4.23
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
         CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

$ sha256sum /usr/bin/gpg
a72cb1fd7a1dcf94c7c8de2a2e749bce22f16af59c2b2157b01f73518e0bece7 
*/usr/bin/gpg


Or...

$ which gpg2
/usr/bin/gpg2

$ gpg2 --version
gpg: WARNING: unsafe permissions on homedir '/home/reneb/.gnupg'
gpg (GnuPG) 2.2.35-unknown
libgcrypt 1.10.1-unknown
Copyright (C) 2022 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/reneb/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
         CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

$ sha256sum /usr/bin/gpg2
87f54df3c700c2bae6211cdb71540b8cc26b43bed60c8b2821e156e070c625f9 
*/usr/bin/gpg2

-- 
R.Berber

WARNING: multiple messages have this Message-ID
From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: weird error gpg
Date: Fri, 24 Jun 2022 11:21:00 -0500	[thread overview]
Message-ID: <c94b40df-6460-12dc-3f1b-f287cda15430@gmail.com> (raw)
Message-ID: <20220624162100.lIMGXLdTmpGgCe_WBZZKK60-U_NPNKeEx45-OfRcbZo@z> (raw)
In-Reply-To: <201387757.8392172.1656086113460@mail.yahoo.com>

On 6/24/2022 10:55 AM, Jim McNamara via Cygwin wrote:

> $ gpg --verify fedora.asc Fedora-KDE-Live-x86_64-36-1.5.iso
> gpg: can't handle text lines longer than 19995 characters
> gpg: Signature made Fri May  6 10:21:35 2022 EDT using RSA key ID 38AB71F4
> gpg: BAD signature from "Fedora (36) <fedora-36-primary@fedoraproject.org>"
> 
> I am having a difficult time. I think they are breaking into my computer.
> They made it so I can't verify files.
> 
> Is there any way I can fix it so that this error goes away?

Start by checking gpg itself.


$ which gpg
/usr/bin/gpg

$ gpg --version
gpg (GnuPG) 1.4.23
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, RSA-E, RSA-S, ELG-E, DSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
         CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

$ sha256sum /usr/bin/gpg
a72cb1fd7a1dcf94c7c8de2a2e749bce22f16af59c2b2157b01f73518e0bece7 
*/usr/bin/gpg


Or...

$ which gpg2
/usr/bin/gpg2

$ gpg2 --version
gpg: WARNING: unsafe permissions on homedir '/home/reneb/.gnupg'
gpg (GnuPG) 2.2.35-unknown
libgcrypt 1.10.1-unknown
Copyright (C) 2022 g10 Code GmbH
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: /home/reneb/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
         CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

$ sha256sum /usr/bin/gpg2
87f54df3c700c2bae6211cdb71540b8cc26b43bed60c8b2821e156e070c625f9 
*/usr/bin/gpg2

-- 
R.Berber


  reply	other threads:[~2022-06-24 16:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201387757.8392172.1656086113460.ref@mail.yahoo.com>
2022-06-24 15:55 ` Jim McNamara
2022-06-24 16:21   ` René Berber [this message]
2022-06-24 16:21     ` René Berber
2022-06-24 16:41     ` Jim McNamara
2022-06-24 16:54       ` René Berber
2022-06-24 16:54         ` René Berber
2022-06-24 19:27       ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c94b40df-6460-12dc-3f1b-f287cda15430@gmail.com \
    --to=rene.berber@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).