<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Nov 20, 2014 at 10:49 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>On 11/21/14, 3:47 AM, "Daniel Fisher" <<a href="mailto:dfisher@vt.edu" target="_blank">dfisher@vt.edu</a>> wrote:<br>
<br>
<br>
><br>
>That was a different issue, but it did get pulled in.<br>
><a href="https://github.com/vt-middleware/cryptacular/issues/7" target="_blank">https://github.com/vt-middleware/cryptacular/issues/7</a><br>
><br>
>The API could not support multi-value RDNs.<br>
<br>
</span>Yeah, I figured out what it was doing.<br>
<br>
Correct me, but I think Brent concluded that what we wanted was to walk<br>
the RDN sequence backward, but the attributes forward within each RDN?<br>
<br></blockquote><div><br></div><div>Yes, walk the RDN backwards to get the "most specific" RDN.</div><div>Grabbing the first attributes is arbitrary afaict.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In my use case, I'm supposed to extract one single value, and I think that<br>
was what we needed to do?</blockquote><div><br></div><div>I think so.</div><div><br></div><div>--Daniel Fisher</div><div><br></div></div></div></div>