[erlang-questions] Update to public_key in anticipation of CRL support

[Ingela Andin]

Hi!

Sigh, why can they not just follow the PKCS standard. It is of course possible
to let public_key recognise the other oids. We will look into this.
CRL support in public_key is included in R16 although we have not had time
to integrate the support in SSL yet.

Regards Ingela Erlang/OTP team - Ericsson AB

2013/2/17, Drew Varner <drew.varner@REDACTED>:
> It looks like CRL support will enter Erlang in the future [1]. CRLs
> sometimes use the signature algorithm ID 1.3.14.3.2.29 for SHA instead of
> 1.2.840.113549.1.1.5 [2][3]. Can we update pubkey_cert.erl to understand
> this OID [4], even though CRL functionality isn't in place yet? It might be
> useful in other situations also.
>
> Thanks,
> Drew
>
> [1] http://erlang.org/pipermail/erlang-questions/2011-August/060639.html
> [2]
> http://javadoc.iaik.tugraz.at/iaik_jce/current/iaik/asn1/structures/AlgorithmID.html
> [3] https://bugzilla.mozilla.org/show_bug.cgi?id=405966
> [4]
> https://github.com/erlang/otp/blob/maint/lib/public_key/src/pubkey_cert.erl#L377
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>