problem with pidgin and open fire

2015-08-07 Thread Łożyński Mariusz
Hi,

I have problem with connecting pidgin to my own openfire server. Openfire 
3.10.2 is working on Ubuntu
Below I attached logs from pidgin - its look like Server does not use any 
supported authentication method
My openfire server has in /etc/hosts entry: 127.0.0.1  op.test.com
I've changed some real names in logs for e.g test.com



(11:30:24) account: Connecting to account a...@op.test.com/.
(11:30:24) connection: Connecting. gc = 06378F30
(11:30:24) dnsquery: Performing DNS lookup for a...@op.test.com
(11:30:24) dnsquery: IP resolved for a...@op.test.com
(11:30:24) proxy: Attempting connection to 192.168.4.21
(11:30:24) proxy: Connecting to a...@op.test.com:5222 with no proxy
(11:30:24) proxy: Connection in progress
(11:30:24) proxy: Connecting to a...@op.test.com:5222.
(11:30:24) proxy: Connected to a...@op.test.com:5222.
(11:30:24) jabber: Sending (a...@op.test.com): ?xml version='1.0' ?
(11:30:24) jabber: Sending (a...@op.test.com): stream:stream 
to='a...@op.test.com' xmlns='jabber:client' 
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
(11:30:24) jabber: Recv (186): ?xml version='1.0' 
encoding='UTF-8'?stream:stream 
xmlns:stream=http://etherx.jabber.org/streams; xmlns=jabber:client 
from=a...@op.test.com id=a3c861df xml:lang=en version=1.0
(11:30:24) jabber: Recv (335): stream:featuresstarttls 
xmlns=urn:ietf:params:xml:ns:xmpp-tls/starttlsmechanisms 
xmlns=urn:ietf:params:xml:ns:xmpp-saslmechanismEXTERNAL/mechanism/mechanismscompression
 
xmlns=http://jabber.org/features/compress;methodzlib/method/compressionauth
 xmlns=http://jabber.org/features/iq-auth//stream:features
(11:30:24) jabber: Sending (a...@op.test.com): starttls 
xmlns='urn:ietf:params:xml:ns:xmpp-tls'/
(11:30:24) jabber: Recv (50): proceed xmlns=urn:ietf:params:xml:ns:xmpp-tls/
(11:30:24) nss: SSL version 3.3 using 128-bit AES with 160-bit SHA1 MAC
Server Auth: 2048-bit RSA, Key Exchange: 256-bit ECDHE, Compression: NULL
Cipher Suite Name: TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
(11:30:24) nss: 
subject=CN=a...@op.test.com,OU=IT,O=Company,L=City,ST=Region,C=CU 
issuer=E=administra...@op.test.com,CN=CA Root 
Company,OU=IT,O=Company,L=City,ST=Region,C=CU
(11:30:24) nss: subject=E=administra...@test.com,CN=CA Root 
Company,OU=IT,O=Company,L=City,ST=Region,C=CU 
issuer=E=administra...@test.com,CN=CA Root 
Company,OU=IT,O=Company,L=City,ST=Region,C=CU
(11:30:24) certificate/x509/tls_cached: Starting verify for a...@op.test.com
(11:30:24) certificate/x509/tls_cached: Checking for cached cert...
(11:30:24) certificate/x509/tls_cached: ...Found cached cert
(11:30:24) nss/x509: Loading certificate from 
C:\Users\abc\AppData\Roaming\.purple\certificates\x509\tls_peers\a...@op.test.com
(11:30:24) certificate/x509/tls_cached: Peer cert matched cached
(11:30:24) nss/x509: Exporting certificate to 
C:\Users\abc\AppData\Roaming\.purple\certificates\x509\tls_peers\a...@op.test.com
(11:30:24) util: Writing file 
C:\Users\abc\AppData\Roaming\.purple\certificates\x509\tls_peers\a...@op.test.com
(11:30:24) nss: Trusting 
CN=a...@op.test.com,OU=IT,O=Company,L=City,ST=Region,C=CU
(11:30:24) certificate: Successfully verified certificate for a...@op.test.com
(11:30:24) jabber: Sending (ssl) (a...@op.test.com): stream:stream 
to='a...@op.test.com' xmlns='jabber:client' 
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
(11:30:24) jabber: Recv (ssl)(460): ?xml version='1.0' 
encoding='UTF-8'?stream:stream 
xmlns:stream=http://etherx.jabber.org/streams; xmlns=jabber:client 
from=a...@op.test.com id=a3c861df xml:lang=en 
version=1.0stream:featuresmechanisms 
xmlns=urn:ietf:params:xml:ns:xmpp-saslmechanismEXTERNAL/mechanism/mechanismscompression
 
xmlns=http://jabber.org/features/compress;methodzlib/method/compressionauth
 xmlns=http://jabber.org/features/iq-auth//stream:features
(11:30:24) sasl: Mechs found:
(11:30:24) connection: Connection error on 06378F30 (reason: 3 description: 
Server does not use any supported authentication method)
(11:30:24) account: Disconnecting account a...@op.test.com/ (008B3FB8)
(11:30:24) connection: Disconnecting connection 06378F30
(11:30:24) jabber: Sending (ssl) (a...@op.test.com): /stream:stream
(11:30:24) connection: Destroying connection 06378F30
(11:30:25) util: Writing file prefs.xml to directory 
C:\Users\abc\AppData\Roaming\.purple
(11:30:25) util: Writing file C:\Users\abc\AppData\Roaming\.purple\prefs.xml

Thank you veru much in advance

Regards,

Mariusz Lozynski

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support

Re: Not showing logs

2015-08-07 Thread Michael McConville
John Abney wrote:
 Hi, I was wondering how to get the jabber channel I am in to show me
 the pings I missed while I had it closed, like I want them to pop up
 when i open pidgin.
 
 My previous accounts all did this, turn off pidgin for the night, turn
 it back on in the morning and all pings that where sent pop up along
 with the rooms i auto join.

You're saying that this works with only some accounts on the same client
(Pidgin)? If so, it might be because some of your Jabber providers don't
support it.

___
Support@pidgin.im mailing list
Want to unsubscribe?  Use this link:
https://pidgin.im/cgi-bin/mailman/listinfo/support