The DN input mechanism used by certtool when creating certificates is
braindamaged. Instead of asking for a fully-formed DN, it asks for a
handful of attributes, and enforces a particlar order on them. This is
useless when you wanted a certificate that has a given attribute more
than once, or in a more normal order (who the heck puts O before OU,
or C at the start?).

Not exactly complete, because I couldn't remember all the attribute
names offhand, but here's a quickly hacked up patch that does it
properly. Supports c, ou, o, and cn, which is enough for most things
and lets me create my "cn=foo, ou=bar, ou=baz, o=quux" certificates.

Hi, your patch seem useful, so we'd like to incorporate it up-stream,
if possible.  But to be able to do this, we would need a copyright
assignment for it.  Is this OK with you?  If so, please use the form
below.

Thanks.

Please email the following information to assign@gnu.org, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.
----------------------------------------------------------------------
REQUEST: SEND FORM FOR PAST AND FUTURE CHANGES

[What is the name of the program or package you're contributing to?]


[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]


[For the copyright registration, what country are you a citizen of?]


[What year were you born?]


[Please write your email address here.]


[Please write your postal address here.]





[Which files have you changed so far, and which new files have you written
so far?]

Hi,

did you get / fill-out-and-return the copyright assignment form
(bug #304571)?

Hi,

In bug 304571 you provided a patch to gnutls certtool to change the CN
that could be provided. Upstream expressed a wish to include it in their
code, but they required more information from you to proceed. The
details can be seen in the bug report. Could you please fill out the
form to allow your patch to be included.

Thanks,

James