HiHO...

> The reason is very simple. If you follow the discussions about OpenSSL's
> DN-handling then you understand my intention. If OpenSSL changes the
> names of an extension then we must only change the name in OpenSSL.pm. I
> think the best way is to have a hash with the original names and a hash
> with our names. So the question is only which names we should use for
> the hashs. EXT, EXT_OPENCA, EXT_OPENSSL ..., any ideas?

O.K. i don't know this discussion, but i got the point. I think it sounds
good to have both hashes, so you have a central point, where you can do
changes for all applications, which refer to special extensions which are
known by name *and* you have a hash with all the original names, if you
e.g. want to display everything included in a certificate, which was not
created by yourself, and which maybe uses some extensions that are missing
in the hash with the constant abstract names. But i would find it
annoying, if you always would be restricted to the named extensions.

> > That's the same problem, like the different ways of parsing
> > the Subject-DN in OpenSSL.pm  and REQ.pm (I think, it was there??)
> > The one parses in a generic way everything and provides a hash with all
> > existent data and you can look, what you want to use. And the other one
> > looks only for specific parts and you will never be able to see the rest.
> 
> Robert wrotes a new module X500::DN. You can load the DN via
> OpenCA::(X509|REQ), put it into X500::DN via parseRFC2253 and then you
> can do all what you want via X500::DN->get*.

The documentation looks good :-)

Another point: do you think, it's possible to release the perl-modules
more regularly as a snapshot version?? This would make it much more easy
to have an quite actual version in the existing linux distributions as
it's quite difficult to include a rpm in a distribution, which is based on
a CVS snapshot.

      stephan

-- 
t="\$_='for(\$i=-2;\$_=substr(\"2720ab25409d2500f82310a6272\",\$i+=2,3);)
   .~.
   /V\           [  [EMAIL PROTECTED]     GnuPG: 0x7E30CD6D  ]
 /(   )\
  ^ ~ ^  {\$_=\$i++%2?hex:oct;\$_=chr(\$_%(2**2*22));\$_=\$i?lc:{};print;
}';s/\( +\)|[.\/V~^\\\]+| {2,}|\\[\s+.+\s+\\]//g;eval \$_;"&&echo $t|perl

Attachment: msg00693/pgp00000.pgp
Description: PGP signature

Reply via email to