From: Jim McNamara <roboloki@yahoo.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: weird error gpg
Date: Fri, 24 Jun 2022 15:55:13 +0000 (UTC) [thread overview]
Message-ID: <201387757.8392172.1656086113460@mail.yahoo.com> (raw)
In-Reply-To: <201387757.8392172.1656086113460.ref@mail.yahoo.com>
Hi guys-
$ cd /cygdrive/c/Users/DeathDealer/Downloads
$ 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?
thanks,
jim
next parent reply other threads:[~2022-06-24 15:55 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 [this message]
2022-06-24 16:21 ` René Berber
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=201387757.8392172.1656086113460@mail.yahoo.com \
--to=roboloki@yahoo.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).