search

segler-alex / Pidgin-GPG

GPG plugin for Pidgin
GNU General Public License v3.0
99 stars 35 forks source link

Plugin not available #2

Open G-Lo opened 13 years ago

G-Lo commented 13 years ago

I'm running Pidgin 2.7.10 on WinXP. I downloaded this version: https://github.com/downloads/segler-alex/Pidgin-GPG/PidginGPG-0.9.exe The install setup worked fine: Found GnuPG at: C:\Program Files\winpt\GPG Found Pidgin at: C:\Program Files\Pidgin Added gnupg directory to path Output folder: C:\Program Files\Pidgin\plugins Extract: pidgin_gpg.dll... 100% Completed

But when i relaunched Pidgin, the plugin was not displayed in my plugin list.

elmuSSo commented 13 years ago

I have the same!

(23:25:33) plugins: C:\Program Files\Pidgin\plugins\pidgin_gpg.dll is not loadable: `C:\Program Files\Pidgin\plugins\pidgin_gpg.dll': Nie można odnaleźć określonego modułu. (Could not find this module)

I tested that on two different machines. In both cases ALSO C:\Program Files\Pidgin\plugins\perl.dll is not loadable.

I'm waiting for the answer one month now, but it looks that segler-alex is not logging to github anymore:/

lamero commented 13 years ago

Same problem on Windows 7

Andro1d commented 12 years ago

Copy https://github.com/segler-alex/Pidgin-GPG/blob/master/win32libs/libgpgme.dll -> C:\Program Files\Pidgin && HaveFun :)

Seems to be an installer bug ;) Im not dev of this plug anyway...

G-Lo commented 12 years ago

Nice try but... still nothing :)

Andro1d commented 12 years ago
  1. You copied the dll into C:\Program Files\Pidgin\ ? Dont copy it into the plugin folder ! It has to go into the "application" folder. The dll itself is 230 KB (235'520 Bytes) and should finally reside inside the same folder like the pidgin.exe itself.
  2. You installed GPG4Win ?
  3. You fully terminated Pidgin and started the program again ?

it worked for me...

Windows7 Professional with Pidgin 2.10.0

G-Lo commented 12 years ago
  1. Yes
  2. No, i have another GPG manager i want to keep using (Portable GPGshell on an encrypted virtual disk)
  3. Yes
hurradiegams commented 10 years ago

Hi there,

I've got the same problem, using Windows 7 and Pidgin 2.10.7. It works fine under Arch Linux. I have tried to copy the dll-files to the main directory and the plugin directory, both with no result.

marsjaninzmarsa commented 10 years ago

Also the same problem, fix from @Andro1d don't work (Win 7 Pro x64, Pidgin 2.10.7).

Catscratch commented 10 years ago

Same here. But I think plugin is dead.

shougeki commented 10 years ago

I copied "libgpgme-11.dll" from the gpg4win install directory to the pidgin dir, seems to work now. I used dependencywalker to see what was missing.

pidd89 commented 10 years ago

I copied "libgpgme-11.dll" to pidgin dir, still haven't work.. can you explain how did you integrate it in your pidgin. (Win 7 Pro x64, Pidgin 2.10.7).

shougeki commented 10 years ago

It is probably a better idea to add gnupg to your system path variable than to copy dlls (control panel->system->advanced system settings->Environment varaibles) and if you have the default path to gnupg, add both "c:\program files (x86)\gnu\gnupg\pub;c:\program files (x86)\gnu\gnupg" this way you would have fixed gnupg for every application that wish to use it, and you can use gnupg from the command line.

stop5 commented 10 years ago

if this dont work try (this must be in the pidgin folder): mklink libgpgme.dll ..\GNU\GnuPG\gpgme-11.dll because the plugin wants a "libgpgme.dll" not "libgpgme-11.dll"

Draghtnod commented 9 years ago

The library names depend on the compilation process. And that is very tricky on some systems when cross compiling this plugin for windows. I wrote a Dockerfile which compiles the latest build of Pidgin including a XEP-0280 patch and this plugin with all the pull requests and some more bugfixes. I had to put libgpgme-11.dll libgpg-error-0.dll into my pidgin main folder, plus _pidgingpg.dll in the plugins folder of course.

So many people demanding this. Since the maintainer disappeared, maybe ill clean up my fork and host the precompiled files on my repo. I don't have time to maintain this in long term tho. But at least you get a working plugin with the latest fixes until someone new stands up to maintain this. (Finally XEP-0280 and XEP-0027 on Pidgin! Yayy! But open-keychain/open-keychain/issues/1016 still prevents me from using this with https://github.com/siacs/Conversations -.-)

t2d commented 9 years ago

This would be awesome. The current state of encryption and XMPP in Pidgin is very concerning.

On 14.12.2014 11:06, Draghtnod wrote:

The library names depend on the compilation process. And that is very tricky on some systems when cross compiling this plugin for windows. I wrote a Dockerfile which compiles the latest build of Pidgin including a XEP-0280 patch and this plugin with all the pull requests and some more bugfixes. I had to put /libgpgme-11.dll/ /libgpg-error-0.dll/ into my pidgin main folder, plus /pidgin_gpg.dll/ in the plugins folder of course.

So many people demanding this. Since the maintainer disappeared, maybe ill clean up my fork and host the precompiled files on my repo. I don't have time to maintain this in long term tho. But at least you get a working plugin with the latest fixes until someone new stands up to maintain this. (Finally XEP-0280 and XEP-0027 on Pidgin! Yayy! But open-keychain/open-keychain#1016 https://github.com/open-keychain/open-keychain/issues/1016 still prevents me from using this with https://github.com/siacs/Conversations -.-)

— Reply to this email directly or view it on GitHub https://github.com/segler-alex/Pidgin-GPG/issues/2#issuecomment-66908283.

metaclassing commented 9 years ago

First of all, thank you Draghtnod for helping pick this up, it is an important extension.

I have been fiddling for a little with this and got it working on one machine, but copied the folder to another 64bit machine with the same version of gpg4win installed and have been unable to get pidgin to recognize this plugin...

Wondering if there are any troubleshooting tips you guys could share, how can i collect some debug output to determine WHY its not loading?

Crypto is not really my area of expertise but please let me know if there is anything we can do to help.

Draghtnod commented 9 years ago

I got a 64bit system. Pidgin is by default compiled as a 32bit app. This plugin too. Make sure you compile both in 32bit mode and then use the Depencency Walker (also 32bit version of course) on pidgin_gpg.dll to find out what is missing. The pidgin log output only tells you if it could load the DLL or not, but not what is missing. The missing DLLs have to be put in the Pidgin main directory. libglib should be ignored, because it is already compiled somewhere into Pidgin.

Draghtnod commented 9 years ago

The new version is ready. Get it here: https://github.com/Draghtnod/Pidgin-GPG/releases

Neustradamus commented 5 years ago

No official binaries?