Hi Piraveena, I tried a few X509 parsers online[1] with ---- (4 hyphens) in the delimiter. They seem to work fine. However, in [2] the cert fingerprint calculation fails if we have 4 hyphens and works fine with 5 hyphens.
I couldn't find any reference strictly stating the requirement on the number of dashes in the delimiter. However, in most examples online, I saw 5 hyphens used. So let's use ----- (5 hyphens) as the delimiter. [1] http://phpseclib.sourceforge.net/x509/decoder.php [2] https://www.samltool.com/fingerprint.php Thanks, Farasath On Fri, Feb 1, 2019 at 9:40 AM Piraveena Paralogarajah <[email protected]> wrote: > Hi, > > I'm working with X509 Authentication and now I need to decode the PEM > format of X509 Certificate. > > I want to know whether the number of dashes in Begin of Certificate/ End > of Certificate is defined or it depends on the implementation. > > -----BEGIN CERTIFICATE----- > > -----END CERTIFICATE----- > > Mostly I have seen 5 dashes, but in some places I have different number of > dashes. For an example, In this Git issue [1], there are 4 dashes. I have > referred the spec The Internet IP Security PKI Profile of IKEv1/ISAKMP, > IKEv2, and PKIX [2] also. Can you please tell whether it is mandatory to > have 5 dashes in the format? > > Any help on this would be appreciated. > > [1] https://github.com/wso2/product-is/issues/4352 > [2] https://tools.ietf.org/html/rfc4945#section-6.1 > > Thanks, > Piraveena > *Piraveena Paralogarajah* > Software Engineer | WSO2 Inc. > *(m)* +94776099594 | *(e)* [email protected] > > -- Farasath Ahamed Senior Software Engineer, WSO2 Inc.; http://wso2.com Mobile: +94777603866 Blog: blog.farazath.com Twitter: @farazath619 <https://twitter.com/farazath619> <http://wso2.com/signature>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
