[Tickets #10956] Re: Common Name is 0 while using S/MIME certificates with non-ASCII characters

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10956
------------------------------------------------------------------------------
  Ticket             | 10956
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Common Name is 0 while using S/MIME certificates with
                     | non-ASCII characters
  Queue              | Horde Groupware Webmail Edition
  Version            | 4.0.6
  Type               | Bug
-State              | Unconfirmed
+State              | Feedback
-Priority           | 2. Medium
+Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2012-02-02 15:08) wrote:

I noticed this a few weeks back.  The ASN.1 parsing algorithm hasn't  
been touched in probably 10 years.  And most of the work it is doing  
is to grab completely esoteric information that we don't need (the  
modulus for the public key?  do I care?).  The important info is  
probably validity dates and personal information (name, email), so  
that's all we should really care about.

So switch you using openssl_x509_parse() to parse the certs.  I  
realize it says the API may change, but it has been this way for 10  
years so at some point we should use it.

So try this and see if it fixes things.