I see "Unable to RSA encrypt the password" when Pidgin tries to connect. According to https://github.com/eionrobb/pidgin-opensteamworks/issues/70 it does not work if compiled with nss, but works with polarssl. With the following changes Pidgin is able to connect to the Steam chat: --- /var/portage/gentoo/x11-plugins/pidgin-opensteamworks/files/pidgin-opensteamworks-1.3-Makefile 2015-08-09 22:34:56.000000000 +0200 +++ pidgin-opensteamworks/files/pidgin-opensteamworks-1.3-Makefile 2016-01-05 19:22:19.445767104 +0100 @@ -8,8 +8,8 @@ CFLAGS ?= -O2 -pipe CFLAGS += -Wall -fPIC LDFLAGS += -shared -CPPFLAGS += $(shell $(PKG_CONFIG) --cflags glib-2.0 json-glib-1.0 purple nss gnome-keyring-1) -LIBS += $(shell $(PKG_CONFIG) --libs glib-2.0 json-glib-1.0 purple nss) +CPPFLAGS += $(shell $(PKG_CONFIG) --cflags glib-2.0 json-glib-1.0 purple gnome-keyring-1) -DUSE_POLARSSL_CRYPTO +LIBS += $(shell $(PKG_CONFIG) --libs glib-2.0 json-glib-1.0 purple) -lpolarssl TARGET = libsteam.so --- /var/portage/gentoo/x11-plugins/pidgin-opensteamworks/pidgin-opensteamworks-1.6.1.ebuild 2015-09-08 02:31:01.000000000 +0200 +++ pidgin-opensteamworks/pidgin-opensteamworks-1.6.1.ebuild 2016-01-08 23:45:08.584696733 +0100 @@ -17,7 +17,7 @@ RDEPEND="dev-libs/glib:2 dev-libs/json-glib - dev-libs/nss + net-libs/polarssl gnome-base/libgnome-keyring net-im/pidgin" DEPEND="${RDEPEND}
Appears the actual issue here that current ebuilds of x11-plugins/pidgin-opensteamworks can only use the nss crypto backend and thus depends on pidgin itself using nss, too. If pidgin is emerged with the gnutls use flag, it uses that in place of nss and thus the plugin fails. The proper fix would be, I guess, to depend on pidgin having the gnutls use flag unset. At least on this version of the plugin. git master of the plugin can now be trivially made to use either backend. I have written an ebuild to leverage that and can provide it here if needed.
Just to comment, I had this issue as well, and the steps I did to resolve it were to change the USE flag for pidgin to include python (may not be important), and then when I saw the error message again, I enabled "Pidgin-Encryption 3.1" plugin from the interface. Once I did that, the error message went away. I still have the gnutls use flag enabled.
I tried 1.6.1 with pidgin-encryption, it didn't work oob. Tried adding the python use flag to pidgin, still nothing. So I'm not sure what you did that got it to work.
polarssl is going to be removed -> bug 618354, then, a different "fix" needs to be found :/
Is any of the suggested solutions working for you? is 1.4 affected by this?
(In reply to Fletch Hasues from comment #2) > Just to comment, I had this issue as well, and the steps I did to resolve it > were to change the USE flag for pidgin to include python (may not be > important), and then when I saw the error message again, I enabled > "Pidgin-Encryption 3.1" plugin from the interface. Once I did that, the > error message went away. I still have the gnutls use flag enabled. I had this problem and enabling "Pidgin-Encryption 3.1" plugin from the interface solved it for me too, thanks!
