Richard Levitte - VMS Whacker wrote:
gianni> If I think hard enough, I could probably think of ways that gianni> this would break things.
Well, let's see, we have two places where this is relevant. One is the simple {host}:{port} combination, the other is the URL http://{host}:{port}/... In both cases, the brackets be part of the {host} part. Brackets can't be part of a IP address or a host name (at least as far as I know), so I'm not really sure what would break.
gianni> I think this is one of those cases where you want to stick to gianni> the standard exactly and not allow any non-standard behaviour.
That makes things tougher, because I had planned on letting getaddrinfo() take care of all the correctness verification. With what you ask for, we get back at having to do it ourselves, which is duplication of functionality (and potentially getting it wrong), which I don't see the benefits of.
Cheers, Richard
As long as OpenSSL only accepts the extended behavior as input and never generates the extended behavior on output I do not see there being a problem.
Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
