From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: smime-cert-by-ldap-1 problem
Date: Thu, 16 Jun 2005 14:40:15 +0200 [thread overview]
Message-ID: <ilu3bricw5s.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87zmtqoenw.fsf@seamus.arnested.dk> (Arne =?iso-8859-1?Q?J=F8?= =?iso-8859-1?Q?rgensen's?= message of "Thu, 16 Jun 2005 11:05:07 +0200")
Arne Jørgensen <arne@arnested.dk> writes:
> Another solution is to look for a magic string ("MII") at the
> beginning of the certificate. I have not been able to find any
> authoritative documentation stating that a certificate must begin with
> "MII" (in base64 encoding), but googling for "x509 certificate MII" is
> not against it.
I suspect only degenerative x.509 certs don't start in this way...
I applied your second patch. Was that you think is best?
next prev parent reply other threads:[~2005-06-16 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 18:26 David S. Goldberg
2005-06-14 20:46 ` Arne Jørgensen
2005-06-16 9:05 ` Arne Jørgensen
2005-06-16 12:40 ` Simon Josefsson [this message]
2005-06-16 12:51 ` Arne Jørgensen
2005-06-16 13:52 ` David S. Goldberg
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=ilu3bricw5s.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).