[jdev] subjectAltName in X.509 certificate

2005-12-20 Thread Vinod Panicker
Hi, Was looking at creating an X.509 certificate for the server, and was reading the requirements in the RFC. There are two places where requirements are stated in RFC 3920 - The certificate SHOULD then be checked against the expected identity of the peer following the rules

[jdev] Wildfire Optimization Article

2005-12-20 Thread Matt Tucker
Hello All, We just published an article with detailed information about optimization work done for Wildfire 2.4.0. It covers some of the performance issues that all XMPP servers face, but may be especially interesting to Java developers:

Re: [jdev] subjectAltName in X.509 certificate

2005-12-20 Thread Justin Karneges
On Tuesday 20 December 2005 00:46, Vinod Panicker wrote: What the first para says isn't making sense to me. AFAIK, there is no xmpp extension for subjectAltName (did it mean to say otherName entity? if so, what abt the oid?) Maybe it could use clarification, but saying an 'xmpp subjectAltName

Re: [jdev] subjectAltName in X.509 certificate

2005-12-20 Thread Peter Saint-Andre
Follow this: If a JID for any kind of XMPP entity (e.g., client or server) is represented in a certificate, it MUST be represented as a UTF8String within an otherName entity inside the subjectAltName, using the [ASN.1] Object Identifier id-on-xmppAddr