Shoichi Sakane wrote:
>
> > > No they aren't handled currently. I haven't really looked into IPv6 and
> > > how the things should be displayed and parsed.
> >
> > I can supply the display and parsing grammar. As for the address encoding,
> > it's just 16 octets (in network byte order) encoded as an octet string,
> > just as for IPv4. More later.
> >
> > (we'd like to make this work with IPv6 IPSec certs)
>
> i sent the patch to deal with ipv6 address in subjectaltname last month.
> http://marc.theaimsgroup.com/?l=openssl-dev&m=99769011626596&w=2
> isn't it enough for you ?
It would be better if it could handle ipv6 addresses in certificates
without requiring ipv6 support on the host system. That is if it
encountered such a beast it would display something sensible even if the
host system didn't support ipv6 rather than just "<Invalid>".
I've had a quick look at RFC1884 and this doesn't seem too hard to do.
Steve.
--
Dr Stephen N. Henson. http://www.drh-consultancy.demon.co.uk/
Personal Email: [EMAIL PROTECTED]
Senior crypto engineer, Celo Communications: http://www.celocom.com/
Core developer of the OpenSSL project: http://www.openssl.org/
Business Email: [EMAIL PROTECTED] PGP key: via homepage.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
