<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Nov 17, 2014 at 10:51 PM, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 11/18/14, 3:35 AM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br>
<br>
<br>
><br>
>From my tracing, it's throwing the exception in Bouncy Castle's code that<br>
>cryptacular is calling, rather than cryptacular itself.<br>
<br>
</span>Correction, it's in cryptacular.<br>
<br>
AttributeType.class:<br>
<br>
public static AttributeType fromOid(final String oid)<br>
{<br>
for (AttributeType t : AttributeType.values()) {<br>
if (t.getOid().equals(oid)) {<br>
return t;<br>
}<br>
}<br>
throw new IllegalArgumentException("Unknown AttributeType for OID " +<br>
oid);<br>
}<br>
<br>
That seems to be limiting the possible OIDs to a fixed set, which is, I<br>
think, not practical.<br>
<br>
<br>
I think the normal practice, such as it is, is to just return the OID<br>
string as the "name" of the attribute, if it's not recognized. Maybe<br>
Daniel/Marvin could patch that?</blockquote><div><br></div><div>Can you send me the cert that causes the problem?</div><div>I'll file an issue.</div><div><br></div><div>--Daniel Fisher</div><div> </div></div></div></div>