Am Wed, 22 Jan 2025 11:32:00 +0100
schrieb Matthias Apitz :
> I asked an Insurance Company in its web pages for contacting me
> and got the two attachments without any further text in the body of
> the mail. What can or should I do to read the encrypted text?
Do you have GPG set up and a keypair?
Am 05.11.2024 um 21:58:28 Uhr schrieb Werner Koch:
> Thanks for the certificate; that is really helful. Please give me a
> few days to check it. The good thing is that the parser works:
>
> $ ~/b/libksba/tests/cert-basic x.cer
> Certificate in `x.cer':
> serial: (#00CDB882CF52A4258A4CB6FA
Am 17.11.2024 um 09:14:47 Uhr schrieb Andrew Gallagher:
> A question to both Robert and Marco:
> Where did you get your gnupg(s) from?
Debian repo, currently experimental.
> In the above transcript it looks like it is querying
> keys.openpgp.org, which sometimes distributes keys without userids.
Am 16.11.2024 um 17:34:31 Uhr schrieb Robert J. Hansen via Gnupg-users:
> > It won't be listed by --list-keys and doesn't give an error
> > message.
>
> It does, in fact.
It doesn't, on my machine, which I want to investigate further.
> rjh@sarah ~ % gpg --recv-keys
> 0x020898F03962F8B76B42D9
Hello!
I tried to import a GPG key.
gpg --recv-keys 0x020898F03962F8B76B42D9F1E805C860F0E3CCB5 --verbose
It won't be listed by --list-keys and doesn't give an error message.
Do I use it wrong, is the key faulty or is it a problem on my system?
m@ryz:~$ gpg --version
gpg (GnuPG) 2.4.6
libgcrypt
Am 05.11.2024 um 13:51:12 Uhr schrieb Werner Koch:
> On Tue, 5 Nov 2024 13:12, Marco Moock said:
>
> > As the release notes say it is fixed in 2.4.6, I tried it today, but
> > doesn't work yet.
>
> Unfortunately the tracker has no information on a sample certificate
> useful for debugging. I
Am 20.06.2024 um 15:15:38 Uhr schrieb Werner Koch:
> your certificate is the first I have seen with empty Subject but a an
> altSubjectName. This is valid but not yet supported.
>
> Tracked at https://dev.gnupg.org/T7171
As the release notes say it is fixed in 2.4.6, I tried it today, but
doesn
Hello!
https://gnupg.org/gph/de/manual/f20.html#AEN33
doesn't seem to have any charset encoding information.
If the charset in the browser isn't set to "western", it won't display
many special characters like "Ä" properly.
In the HTTP inspector I also can't find any encoding info.
Content-Type:"
Am Sat, 31 Aug 2024 18:29:17 +0200
schrieb "T. S." :
> If someone could provide me with information, if such header
> implementations are already somewhere discussed, I would be glad.
I've now seen an implementation for signing control messages for Usenet:
ftp://ftp.isc.org/usenet/control/hispag
Am 01.09.2024 um 15:51:57 Uhr schrieb Stuart Longland:
> Given the public key is published in DNS records, could you imagine
> the hot mess that'd create for domains with lots of users? Either
> lots of DNS records, or lots of users sharing the same private key.
Is there a limit for DNS records?
Am 01.09.2024 um 14:46:58 Uhr schrieb Stuart Longland via Gnupg-users:
> 1. end-to-end digitally sign the email, the email is not signed until
> it is transmitted by your mail server, malicious code (or users) on
> the server can still manipulate it before sending.
It would be possible to sign DK
Am Sat, 31 Aug 2024 18:29:17 +0200
schrieb "T. S." :
> Is somethings similar available for GPG/PGP?
I don't know about such an implementation, but if you want to create
one, everybody can publish RFCs at IETF, so feel free to create such a
technology.
If you want something unofficial, use the X-
12 matches
Mail list logo
