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 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
Hi!
and thanks the report.
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 didn't checked the mailing list though
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 Werner!
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
Thanks for finding that out.
Is that triggered by the csr
Hi!
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
Salam-Shalom,
Werner
--
The pioneers of a warless world are the youth that
refuse military service. - A. Eins
Am Donnerstag 20 Juni 2024 11:20:14 schrieb Marco Moock:
> My cert itself creates the problem, the separate CA intermediate
> cert can be imported properly.
I've figured and included the lines for additional context only. :)
--
https://intevation.de/~bernhard +49 541 33 508 3-3
Intevation GmbH
Hello!
Am 20.06.2024 um 11:07:00 Uhr schrieb Bernhard Reiter via Gnupg-users:
> gpgsm --debug-all --import zert.crt
>
> gpgsm: can't get authorityInfoAccess: No value
> gpgsm: issuer certificate (#/CN=Sectigo RSA Client Authentication and
> Secure Email CA,O=Sectigo Limited,L=Salford,ST=Greater
Hi Marco, hi Werner,
Am Dienstag 18 Juni 2024 08:44:00 schrieb Bernhard Reiter via Gnupg-users:
> > I can send you mine if you would like to test.
>
> At least I can try to import it and see what my version says.
did a test with Gpg4win, which print a different error message:
gpg (GnuPG) 2.4.5
l
Hi
> 4 - 2024-06-18 16:08:56 gpgsm[39608]: ksba_cms_parse failed:
> Ungültiges CMS Objekt
Please send me such a non-parseable message/data by private mail. No
HTML parts or ZIP files, just gzip the message.
Which version of GnuPG are you using:
gpgsm --version
also shows the libksba version
Am 12.06.24 um 21:37 schrieb Marco Moock:
I tried to import it, but it doesn't work.
I've now managed to import it in Thunderbird and can send emails, but
Claws Mail (using gpg as backend) can't check the cert.
[2024-06-18T16:08:52] Protokollierung begonnen
[client at fd 4 connected (local)
Am Montag 17 Juni 2024 19:27:35 schrieb Marco Moock:
> Am 17.06.2024 um 17:14:07 Uhr schrieb Bernhard Reiter via Gnupg-users:
> > does Sectigo offer a public certificate somewhere which could
> > possibly be imported for a test?
> I can send you mine if you would like to test.
At least I can try
Am 17.06.2024 um 15:40:00 Uhr schrieb Werner Koch:
> gpgconf -V
>
> gives a verbatim description of the version and the used libraries.
>
> gpgconf -X
>
> lists all configuration files along wity some other info. Take care
> to redact lines which you consider sensitive.
Is included in the a
Am 17.06.2024 um 17:14:07 Uhr schrieb Bernhard Reiter via Gnupg-users:
> Am Mittwoch 12 Juni 2024 21:37:11 schrieb Marco Moock:
> > I got an S/MIME certificate from Sectigo, which I would like to use
> > with gpgsm/Kleopatra.
>
> does Sectigo offer a public certificate somewhere which could
> p
Hello,
Am Mittwoch 12 Juni 2024 21:37:11 schrieb Marco Moock:
> I got an S/MIME certificate from Sectigo, which I would like to use
> with gpgsm/Kleopatra.
does Sectigo offer a public certificate somewhere which could possibly be
imported for a test?
The message
gpgsm: unknown digest algorith
Hi!
If you send bug reports or asking for support please always tell us the
version of GnuPG you are using as well as the operating system and its
version. The latter part is needed because Linux distributions often
apply a lot of custom changes to software which are not reflected by the
version
Am 14.06.2024 um 11:51:07 Uhr schrieb Ingo Klöcker:
> Start by adding "--verbose" to the command line of gpgsm. You can add
> "--verbose" multiple times to increase the verbosity.
I did that and it shows me some stuff.
The question is how can I find out why the digest algorithm isn't
recognized?
On Freitag, 14. Juni 2024 11:30:06 CEST Marco Moock wrote:
> Am 13.06.2024 um 18:19:53 Uhr schrieb Eason Lu via Gnupg-users:
> > If you have access to the Kleopatra gui, you can just open the .cert
> > with Kleopatra. And than it will ask you for the password with the
> > cert and let you set a new
Am 13.06.2024 um 18:19:53 Uhr schrieb Eason Lu via Gnupg-users:
> If you have access to the Kleopatra gui, you can just open the .cert
> with Kleopatra. And than it will ask you for the password with the
> cert and let you set a new one. Once Kleopatra accepted the cert, gpg
> will sync it.
Kleo
Hi
If you have access to the Kleopatra gui, you can just open the .cert
with Kleopatra. And than it will ask you for the password with the cert
and let you set a new one. Once Kleopatra accepted the cert, gpg will
sync it.
Eason
___
Gnupg-us
Hello!
I got an S/MIME certificate from Sectigo, which I would like to use
with gpgsm/Kleopatra.
I got a .crt (PEM according to the file command) from them and I used
openssl to create a pfx (also tried p12) together with my private key.
openssl pkcs12 -export -out zertifikat-smime/zert-alles.pf
21 matches
Mail list logo