On Mon, Aug 9, 2010 at 8:20 PM, Tony Graziano <[email protected]> wrote: > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > In-Reply-To: <[email protected]> > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <50140> > Message-ID: <[email protected]> > > > > Confused. Why would one need an ssl certificate for openfire > anyway? sipxecs has a method for importing a standard issued > ssl cert and importing it. The openfire web interface isn't > "really" used. > > What do you do that requires one "for openfire specifically" > so I might understand why this should be easier to do, as > you've suggested? > > As I understand the implementation, the openfire console is > disabled and not used by most admins. Even the admins who > use it usually keep it closed since most settings changes > are overwritten by sipx anyway... > -- > ===================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: mailto:[email protected][/email] > Fax: 434.984.8431 > > Email: mailto:[email protected][/email] > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
You can do Server to Server encryption using SSL on most IM servers, so maybe it's for that. Haven't really looked at it yet, so I may be way off base here. Matt P. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
