Re: smime-cert-by-ldap-1 problem

["Arne Jørgensen" <arne@arnested.dk>]

david.goldberg6@verizon.net (David S. Goldberg) writes:

> According to this bit from smime.el:
>
> 	  ;; Certificates on LDAP servers _should_ be in DER format,
> 	  ;; but there are some servers out there that distributes the
> 	  ;; certificates in PEM format (with or without
> 	  ;; header/footer) so we try to handle them anyway.
> 	  (if (or (string= (substring (cadaar ldapresult) 0 27)
> 			   "-----BEGIN CERTIFICATE-----")
> 		  (condition-case nil
> 		      (base64-decode-string (cadaar ldapresult))
> 		    (error nil)))
> 	      (setq cert
> 		    (smime-replace-in-string
> 		     (cadaar ldapresult)
> 		     (concat "\\(\n\\|\r\\|-----BEGIN CERTIFICATE-----\\|"
> 			     "-----END CERTIFICATE-----\\)")
> 		     "" t))
> 	    (setq cert (base64-encode-string (cadaar ldapresult) t)))
>
> then the result of smime-cert-by-ldap should be a base64 encoded block
> surrounded by the BEGIN and END CERTIFICATE lines. 

Correct.

> Instead, I get the DER with extra CRs inserted every 64 bytes,
> surrounded by the BEGIN and END lines. The problem is that
> base64-decode-string does not throw an error, and from what I can
> see in base64.el, it's not designed to.

Is base64-decode-string on XEmacs different from the one in Emacs?

As I remember base64-decode-string does throw an error on Emacs. I
will look deeper in to this tomorrow or the day after.

> Interesting enough, the DER with the extra CRs seems to work OK though

That's weird I think.

> I have to wonder if it's related to the CRs that in the magic number
> issue I wrote about earlier.

I don't think so.

Kind regards,
-- 
Arne Jørgensen <http://arnested.dk/>