On Sonntag, 20. Februar 2022 22:16:31 CET Ralph Seichter via Gnupg-users
wrote:
> > Has the tarball been signed with two keys?
>
> According to the output you posted there are two signatures from two
> separate keys, made on two different days.
Looking at
https://gnupg.org/download/integrity_che
Not gpg specific, but I would capture that output in a file, and then
use other tools to figure out what that text is. On linux, I would
start with some variant of "od -c" or perhaps open it in a text editor
or word processor.
On 2/18/22 06:34, Gao Xiaohui via Gnupg-users wrote:
Hi developer
* mailinglisten:
> Has the tarball been signed with two keys?
According to the output you posted there are two signatures from two
separate keys, made on two different days.
-Ralph
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
https://lists.gnupg
Hi there,
when trying this:
gpg --verify gnupg-2.3.4.tar.bz2.sig gnupg-2.3.4.tar.bz2
I get that:
gpg: Signature made Mo 20 Dez 2021 22:52:45 CET
gpg:using EDDSA key 6DAA6E64A76D2840571B4902528897B826403ADA
gpg: Good signature from "Werner Koch (dist signing 2020)" [unknown]
gpg:
On Sonntag, 20. Februar 2022 17:37:51 CET Alireza Sadeghpour wrote:
> On Sun, 20 Feb 2022, 7:37 PM Ingo Klöcker, wrote:
> > On Sonntag, 20. Februar 2022 16:25:31 CET Alireza Sadeghpour wrote:
> > > I am trying to encrypt and sign a file with gpg and loopback pinentry
> > > option, with the below c
Thanks for your response,
Actually i need to use two keys, one for aes encryption and another one is
used for rsa signing, which both of them are protected with a passphrase.
I tried to indicate rsa key passphrase with --passphrase option and aes key
with --passphrase-file option.
If that is wr
On Sonntag, 20. Februar 2022 16:25:31 CET Alireza Sadeghpour via Gnupg-users
wrote:
> I am trying to encrypt and sign a file with gpg and loopback pinentry
> option, with the below command:
>
> gpg --pinentry-mode=loopback --passphrase ="mypws" \
> --ignore-time-conflict --ignore-valid-from \
> -
I am trying to encrypt and sign a file with gpg and loopback pinentry
option, with the below command:
gpg --pinentry-mode=loopback --passphrase ="mypws" \
--ignore-time-conflict --ignore-valid-from \
--cipher-algo AES256 --symmetric --ignore-time-conflict \
--passphrase-file ~/.gnupg/PG/p-enckey -
Whoever told you SHA-1 is broken was gravely in error. There are certain areas of the cryptographic space where it is no longer recommended. There are others where it's strong as a rock.As part of an iterated key derivation function, SHA-1 is still believed safe. There's no reason to shy away from
> Has it really been that long? ... No, it has not been: a free-start
collision was
> found on the SHA-1 compression function in 2015, less than
> 7 years ago.
>
> As far as I know, a single collision pair ("SHAttered") has been produced,
> using about 9 months on a very large cluster, against the
10 matches
Mail list logo