Any answers to this? Do I only need the s2s port, or if I need further jabber ports opened (e.g in addition to the jabber client port..)? Also, for the common name/domain name for the certificate, should it be the full domain (example.com) or wave.* (wave.example.com)?
On Sat, Nov 7, 2009 at 8:15 PM, Matt Richards <[email protected]> wrote: > Okay, > > Then I guess the solution is to use SartSSL or something that is more > universally accepted, seems these CACert.org certs aren't sufficient. > > Port wise, do I only need to open up 5269 (and the wave client port) - > the s2s port for Jabber, or are there some others that need to be > opened as well? > > On Sat, Nov 7, 2009 at 8:05 PM, Ben Kalman <[email protected]> wrote: >> >>> >>> >>> In terms of Ben's question, I've added the Root Certificate for CAOrg >>> to Sun Java's keystore, now I can at least successfully load a >>> certificate in FedOne. >>> >> >> Right, but whoever you send your certificate to presumably wouldn't have >> done the same. >> >> >> >> > > > > -- > --Matt > -- --Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
