oh... true... I didn't notice that... here is my working SSL config
<id realm='' verify-mode='2' require-starttls='true' pemfile='/etc/httpd/conf/key.pem' register-enable='true'>domain.com</id> (I replaced the real domain with domain.com here) and for sure, my key.pem contains - private key - local cert (not sure but it's a cert - I should have commented that, can you have comments in a .pem file?) - intermediate cert - root cert In my previous answers I was looking at the "default" pem which is with jabberd2 On Thu, Apr 15, 2010 at 2:57 PM, Tomasz Sterna <[email protected]> wrote: > Dnia 2010-04-14, śro o godzinie 20:16 +0200, Salvatore De Paolis pisze: >> <local> >> <id realm='mysite.com' >> pemfile='/usr/etc/pemfile.pem' >> verify-mode='true' >> register-enable='true' >> password-change='true'>mysite.com</id> >> <ip>0.0.0.0</ip> >> <port>5222</port> >> </local> > > > verify-mode is a number, not boolean. > > http://codex.xiaoka.com/svn/jabberd2/trunk/etc/c2s.xml.dist.in > verify-mode > SSL verify mode - see SSL_CTX_set_verify(3), mode parameter. > Sum of the following options: > SSL_VERIFY_NONE 0x00 > SSL_VERIFY_PEER 0x01 > SSL_VERIFY_FAIL_IF_NO_PEER_CERT 0x02 > SSL_VERIFY_CLIENT_ONCE 0x04 > Use 7 to require all clients to present _valid_ certificates. > > > -- > To unsubscribe send a mail to [email protected] > > -- To unsubscribe send a mail to [email protected]
