Dnia 2013-11-04, pon o godzinie 14:41 -0800, Peter Saint-Andre pisze:
Would someone in the jabberd2 community consider writing a brief howto
about configuring jabberd2 so that it allows only encypted
connections?
Our separate documentation tends to rot, so the only authoritative (and
actively
On Tue, 05 Nov 2013 10:45:49 +0100
Tomasz Sterna wrote:
Dnia 2013-11-04, pon o godzinie 14:41 -0800, Peter Saint-Andre pisze:
Would someone in the jabberd2 community consider writing a brief howto
about configuring jabberd2 so that it allows only encypted
connections?
Our separate
On Mon, Nov 04, 2013 at 02:41:16PM -0800, Peter Saint-Andre wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Would someone in the jabberd2 community consider writing a brief howto
about configuring jabberd2 so that it allows only encypted
connections? Someone at the IETF meeting asked
On Monday, November 04 2013, Justin T. Pryzby wrote:
If you mean in C2S: id require-starttls='1'.
You can also set ssl-port5223/ssl-port, which will naturally
reject anything that's not valid SSL (different from xmpp+starttls).
Also, if you want to allow *only* encrypted connections between
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/4/13 3:18 PM, Sergio Durigan Junior wrote:
On Monday, November 04 2013, Justin T. Pryzby wrote:
If you mean in C2S: id require-starttls='1'.
You can also set ssl-port5223/ssl-port, which will naturally
reject anything that's not valid
