psi-im / psi

XMPP client
https://psi-im.org/
Other
406 stars 122 forks source link

OpenFire server connection fault with infinity modal password window #390

Closed ep4sh closed 6 years ago

ep4sh commented 6 years ago

Openfire 4.2.3 Java: 1.8.0_181 Oracle Corporation – OpenJDK Server VM Psi v1.3

When connect to my server via PSI - it creates a modal window with pass, even i try to input it (password is correct!). Other clients (Pidgin, Gajim) - works well.

This problem only with linux-machines: Ubuntu 18.04, Debian 9, Ubuntu 16

Otherwise, i have an PSI installed on Windows machine - it connect correct.

Here screenshot of modal window: https://imgur.com/a/aYWGDFX

liuch commented 6 years ago

Is this option turned on in your account properties?

Try to turn it off.

tehnick commented 6 years ago

Disable "Use system keyring manager" option in Psi Options Dialog or install package libgnome-keyring0.

ep4sh commented 6 years ago

Im very pleasant for your answers, but:

1) "Store hash instead of plaintext" Option is OFF, tried ON - but no result.

2) looked for "Use system keyring manager" option, but cant see it, we use simple Psi (not Psi+)

3) Installed libgnome-keyring0 but No result.

When i try to connect to server:

root@PCE43:~# strace -e connect -p 18934 
strace: Process 18934 attached
connect(29, {sa_family=AF_INET, sin_port=htons(5222), sin_addr=inet_addr("192.168.1.178")}, 16) = -1 EINPROGRESS (Operation now in progress)
connect(29, {sa_family=AF_INET, sin_port=htons(5222), sin_addr=inet_addr("192.168.1.178")}, 16) = 0
tehnick commented 6 years ago

looked for "Use system keyring manager" option, but cant see it, we use simple Psi (not Psi+)

Sorry, I forgot that there are no such option in Psi-1.3, it is available only in a master branch of Psi now.

ep4sh commented 6 years ago

I made wireshark dump: psi-openfire.pcapng.gz

Here i see crypted password (isnt it?) and server`s reject (for incorrect password).... may be it append additional symbols, so pass can be truly incorret?

ws1

ws2

tehnick commented 6 years ago

Ok, let's check the most stupid things. Which packages with QCA plugins are installed in your system?

dpkg -l | grep qca

Psi v1.3 ... This problem only with linux-machines: Ubuntu 18.04, Debian 9, Ubuntu 16

There are no Psi-1.3 in official repositories of Debian Stretch and Ubuntu Xenial. Have you build the program for these systems yourself? Which version of Qt was used for them?

ldd /usr/bin/psi-plus | grep 'lib.*Qt.*'
ep4sh commented 6 years ago

Sorry for disinformation! correct info:

Ubuntu 18.04.1 LTS -- Psi 1.3 (with trouble)
Ubuntu 16.04.04 LTS -- Psi 0.16.330 (forget about it -- suddenly, but today it works well!   -___-)
Debian 9 -- Psi 0.15-4 (with trouble)

On ubuntu 18.04:

Which packages with QCA plugins are installed in your system?

ii  libqca-qt5-2:amd64                            2.1.3-2ubuntu2                              amd64        libraries for the Qt Cryptographic Architecture
ii  libqca-qt5-2-plugins:amd64                    2.1.3-2ubuntu2                              amd64        QCA plugins for libqca2

Which version of Qt was used for them?

root@PCE43:~# ldd /usr/bin/psi | grep 'lib.*Qt.*'
libQt5Widgets.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 (0x00007f1228edf000)
libQt5X11Extras.so.5 => /usr/lib/x86_64-linux-gnu/libQt5X11Extras.so.5 (0x00007f1228cdb000)
libQt5Gui.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 (0x00007f1228572000)
libQt5Xml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5 (0x00007f1228336000)
libQt5Network.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 (0x00007f1227faa000)
libQt5Concurrent.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Concurrent.so.5 (0x00007f1227da3000)
libQt5DBus.so.5 => /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 (0x00007f1227b19000)
libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 (0x00007f12273ce000)

On Debian 9:

ii  libqca2:amd64                                                    2.1.1-4+b2                                  amd64        libraries for the Qt Cryptographic Architecture
ii  libqca2-plugin-ossl:amd64                                        2.1.1-4+b2                                  amd64        transitional package for libqca2-plugins
ii  libqca2-plugins:amd64                                            2.1.1-4+b2                                  amd64        QCA plugins for libqca2
libQtDBus.so.4 => /usr/lib/x86_64-linux-gnu/libQtDBus.so.4 (0x00007fd7faf8e000)
      libQtXml.so.4 => /usr/lib/x86_64-linux-gnu/libQtXml.so.4 (0x00007fd7fab2b000)
      libQtGui.so.4 => /usr/lib/x86_64-linux-gnu/libQtGui.so.4 (0x00007fd7f9e3d000)
      libQtNetwork.so.4 => /usr/lib/x86_64-linux-gnu/libQtNetwork.so.4 (0x00007fd7f9ae9000)
      libQtCore.so.4 => /usr/lib/x86_64-linux-gnu/libQtCore.so.4 (0x00007fd7f95f6000)
tehnick commented 6 years ago
...
ii  libqca-qt5-2-plugins:amd64                    2.1.3-2ubuntu2
...
ii  libqca2-plugin-ossl:amd64                                        2.1.1-4+b2                                  amd64        transitional package for libqca2-plugins
ii  libqca2-plugins:amd64                                            2.1.1-4+b2   
...

At least you have all necessary QCA plugins.

Ok, next stupid assumption. Try to install:

sudo apt-get install -V libsasl2-modules

It should be installed as a dependency of QCA packages, but we just check it...

ep4sh commented 6 years ago

We have solved this: it was incorrect Domain name (FQDN):

on Ubuntu 18 i used the same user@mail dom

but on Windows it works well... dom2

Thanks for your help!

tehnick commented 6 years ago

Probably you have server with NetBIOS name mail in your LAN and it was used fine in MS Windows, because resolver service of NetBIOS names in enabled in MS Windows by default (IIRC it is called WINS). In Linux based systems you should install Samba and configure it properly for this...