Application: WinPT
Category: privacy/security
Description: WinPT is "A graphical taskbar front-end for GnuPG with integrated key management and the ability for file and clipboard encryption." WinPT Portable uses GnuPGPortable.nsh as described in this thread to portablize GnuPG dependencies. WinPT requires an installation of GnuPG. My GnuPG Portable 1.4.10 Dev Test 14 is highly recommended.
Download WinPTPortable 1.4.2 Dev Test 6[1.6MB download/2.2MB installed]
(MD5: 1964A588E7C3136B63A9BD740B6106F5 )
Release Notes:
1.4.2 Development Test 6 (2009-09-03):
- Update--Installer built with PA.c Installer 0.91.7
- Update--Updated to WinPT 1.4.2
Development Test 6 (2009-06-24):
- Update--Installer built with PA.c Installer 0.91.4
-
Update--Updated to WinPT version 1.4.1
NOTE:1.4.1 fixes a problem with utf-8 passphrases. If you have used any prior version of WinPT (portable or not) with an utf-8 passphrase then refer to the file \WinPTPortabl\App\WinPT\8Bit-Passphrase.txt for directions on how to transition your files and or keys - Update--WinPT has started including .sig files for all critical files. Repacking these files would only save a few hundred KB and would invalidate the .sig files. To respect the original author's efforts to provide authentication of binaries these files have been left unaltered.
Development Test 5 (2009-04-23):
- Updated installer to 0.13.3
-
Updated WinPT to 1.3.2 read changelog here
Includes fixes from 1.3.1 which was skipped for portablization due to launch problems. - Updated the launcher code. No longer uses a default .reg or .ini
- New WinPTPortable.ini option DisplayPaths. true by default. Causes WinPTPortable.exe to report what GPG.exe and keyring paths it will use before it launches WinPT so the user can confirm or cancel.
- Compacted with AppCompactor.
- New readme.txt in the source folder.
- WinPT.exe supports Russian and German automatically so russian and german launcher language files have been included for compiling to these languages.
Development Test 4 (2009-01-02):
- Updated WinPT to version 1.3.0
- Updated PortableApps.comInstaller to 0.10.4.0
- Compiled against GnuPGPortable.nsh Dev Test 9
Development Test 3 (2008-03-27):
- Recompiled against GnuPGPortable.nsh Dev Test 3
- include for GnuPGPortable.nsh now points to CommonFiles (thanks for the idea rab040ma.)
Development Test 2.3 (2008-02-27):
Development Test 2.2 (2008-02-15):
Development Test 2 (2008-02-13): changed to use GnuPGPortable.nsh instead of GnuPGPortable.exe
Development Test 1 (2008-02-08): Initial release
Dev Notes:
2009-01-02:
Timo Schluz is back working on WinPT after a two year hiatus. His time is contributed to this project on a limited basis so please be patient. And if you find this program useful please send him your appreciation.
I will also be monitoring his rss feed, so as new versions come out I will be updating the portable package.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
I have found an issue that I could use help solving. With WinPT Portable and GnuPG Portable installed I can not use Keepass(local or portable) to autotype the passphrase for file signing. Keepass just crashes with an instruction at foo cannot access mem at bar, memory cannot be written. Any ideas?
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
I just retested this after un packing the WinPT.exe and then repacking WinPT.exe libgpg-error-0.dll and libgpgme-11.dll according to the paf standard and now it all seems to work fine.
Side note. PTD.dll would not pack due to "writeable shared sections"
I will update WinPT Portable as soon as I get home.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
I'll try this out.
Edit:Download link doesn't work. Maybe a file extension?
I've had a dickens of a time trying to get WinPT Portable to run consistently on different computers, but the one thing that has consistently worked for me is the download. I'm just hosting this off my family's wordpress based site using the download monitor plugin. so the link is more of a permalink than a direct link, hence no extension. I'm seeing a few downloads of it. Maybe try another browser? Or is my site being blocked by a firewall of some sort on your end? BitBucketMonster?
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
So I test everything out at home on a different computer using the PAF standard UPX packing. Keepass still crashes when I try to do an autotype into WinPT Portable. So I have just uncompressed the whole thing, adding about 400k to the size and now everything works everywhere I have tested. This version is now uploaded
I understand the premise of executable packing but I am unclear on the mechanics. My big questions are:
1. For what possible reasons would a packed exe that runs on one computer not run on another computer?
2. How would the method of packing used on WinPT Portable be causing other apps to crash, namely Keepass? and who is to blame? Keepass? WinPT? UPX? El Diablo?
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
Yes.
MC
42 ?
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
Even is a little late this comment, i wish to inform that I don't use WinPT, but Kee Pass shows me an unconsistent behaviour with the automatic filling of user id and passwords fields.
Denis J Navas
After installation the GnuPG preferences point at my local installation rather than the portable installation. The keys are also created on the main C drive and not the portable drive.
Maybe you could set the portable installation directories as default for both.
The portable installation of GnuPG has higher priority by default. WinPT Portable is supposed to search in the following order:
1. CommonFiles
2. ThunderbirdPortable
3. Local installation
Have you installed GnuPG Portable? If you have and WinPT still loads the keys from C: then we have an issue.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
I installed GnuPG portable before WinPT as it said it had dependencies on it.
My other installation already existed. My memory stick is loaded as drive G: if that makes any difference.
what are the contents of WinPTPortable\Data\Settings\WinPT.reg and WinPTPortableSettings.ini ?
And in WinPTPortable\Other\Source\PortableApps.comInstaller.nsi look for this line
!define PORTABLEAPPSINSTALLERVERSION "0.2.2.0"
0.2.2.0 is the latest
Then if you are comfortable with regedit:
Without WinPTPortable running navigate to HKCU\Software\GNU\GnuPG
What are the paths?
then with WinPTPortable running what are the paths? (don't forget to hit f5 to refresh)
is there a key at HKCU\Software\GnuPGPortable when WinPT is not running? if so delete it and try again running WinPTPortable again.
Again, thank you so much for your time and effort.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
WinPTPortable\Data\Settings\WinPT.reg
WinPTPortableSettings.ini
Yes. 0.2.2.0 is the value in WinPTPortable\Other\Source\PortableApps.comInstaller.nsi
Regedit when WinPTPortable not running
Regedit when WinPTPortable running
HKCU\Software\GnuPGPortable has ClientCount set to 1 when running and is deleted when app is closed.
Hope this helps.
Like I thought. It isn't finding the keyring because one doesn't exist yet. There are two viable solutions
1. create a file named "foo.gpg" in your \PortableApps\CommonFiles\Data\GnuPG\ folder.
This will cause WinPT Portable 2.2 to think it has found a keyring and return a valid path.
or
2. Install 2.3 of WinPT Portable (will be posted in an hour)
WintPT Portable will only look for a valid directory structure, even if it is empty. If it is then WinPT will prompt to create a new keypair or import a keyring.
Thank you Rusty Muppet.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
As far as creating the keyrings in the wrong location I think I Found it!
the GnuPG finder code first looks for gpg.exe in the order
commonfiles
thunderbirdportable
local
the first instance is what it returns as the path to gpg.exe
Then it searches for the keyrings in the order
commonfiles
thunderbirdportable
local
by testing for *.gpg! so if there is no keyring in /PortableApps/CommonFiles/Data/GnuPG then it just moves along to thunderbird and then local!
This could be solved a few ways
1. have a dummy keyring created in commonfiles at installation
2. have the test only look for the existence of the directory
either way I could set up to the GnuPG Portable installer copy exsiting Thunderbird Portable Keyrings (if found) over at install. Any reason not to?
Expect a version .3 of WinPT Portable and GnuPG Portable soon.
Thank you for all the time and effort in testing!
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
Have you thought about using gpg.conf as the thing to search for to find the keyring directory?
Actually, we should have an interim WinPT release that uses ThunderbirdPortable\Data\gpg for its default until John does another release. I don't think TBP will use CommonFiles at all, in its current incarnation, so people using WinPT will end up moving their keyrings to TBP directory.
MC
Actually, if GnuPG Portable is not installed WinPT Portable (which was built using GnuPGPortable.nsh) will use ThunderbirdPortable.
I can understand the confusion. launchers built with GnuPGPortable.nsh don't require a GnuPGPortable installation as much as the name may seem to imply that it does.
If users would like to have WinPT Portable reference the TBP keyring then just make sure that \ProgramFiles\CommonFiles\Data\GnuPG and \ProgramFiles\CommonFiles\GnuPG do not exist.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
In experimenting with GpaPortable, I found that the following would set up the GnuPGhome directory with empty files -- as a way to make the default directory work if it hasn't been set up yet.
It would work with the gnupghome in TBP too -- just makes sure there's something there for the various programs to detect. Once the programs run, they'll populate the files with appropriate things.
You may have found another way already, but I figured I'd drop this in for the record.
MC
while it will find the correct way to the gpg installed, my one is in the thunderbird path, it seems to make mess of the use of it.
The thb will provide right signatures, it ca verify them correctly and so can any other correspondent with pgp.
The winpt will encrypt and decrypt, but when it comes to signatures it will sig with some wrong key (settings appear correct) and it stat any of its sig are bad. This will be approved also by pgp or enigma thunderbird .
winpt can not verify its own signarture except the text is saved as text file and opened again on same place.
Otto Sykora
Basel, Switzerland
Sorry, I'm not clear on what problem you are having. It sounds like you are expecting WinPT signature files to not be detached, but detached sig files are the only ones that WinPT (and GnuPG, as far as I know) can deal with on files.
I was not aware that Enigma on Thunderbird could process signatures for files. If you use WinPT to sign text (e.g. on the clipboard) and paste it into a mail message, Enigma should be able to handle the result ok. But I don't think that is what you are asking about.
If that is not the problem you are having, perhaps you could give some steps to reproduce the problem.
You could also check the sig files created with WinPT using GPA (Gnu Privacy Assistant).
Again, my apologies for not being able to perceive what the problem is. Thanks for your patience.
MC
The basic problems with winpt on my side are not in fact with detached sig on files as such. This part seems to work, howevewer winpt will tell you wrong key ID number when verifying such sig. Probably reading the output of the gpg somehow shifted or what. (gpg on cmd will display correct key ID).
Problem is more that when signing text either in clipbord or via the current window, such sig will later fail when vrified. The key is recognised, the user ID displayed correctly, the key ID displayed incorrectly, but all that does not matter so much, simply the text in the clipbord seems to be once more modified after the sig was created and inserted around the text.
Little hint: when let say signed a text in notepad, the clipboard can be flushed, the signed text selected again, but will still give sig =ok.
When such file is closed and opened again, the sig will turn bad.
Same will come up if such text is sent by mail or newsreader etc. Yes I am aware of the line length etc, but in this case all line lenghts are set so that messages and sigs will not be disturbed.
Eg: text with lines of not more then 60 chars, winpt set to 70 and mailclient to 74.
Such text will not be changed, nor will be the sig when passing via the same mailclient in and out (sent to myself)
I am using it with the defoult installation of TB/GPG, the gpg was fould well, so were the keyrings etc. But when I observed why the TB/GPG can also not verify such text, I have seen that apparently the winpt is beside other things asking:
gpg.exe --charset ut8 .....
I have not found the command charset in the manual of gpg (147 and 149) so it could be that there are some commands inserted or applied to gpg which do not exist any more. Should not disturb, but who knows.
I have informed the original author, (TIM) but somehow he has no stright answer and apparently no time to search the problem.
BTW, I checked the functions again some pgp 658, 658ckt, 7.11. When the sig is bad, it will be bad there too, which means not the sig check itself is wrong, but the text was modified after the sig done.
No problems at all when encrypting&signing or enc alone with clipboard functions.
Otto Sykora
Basel, Switzerland
I have not been able to reproduce these failures yet. But I will keep working at it. You mention character sets. what character set are you operating in?
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
well in general the charset on my side will 8859-1, but could be also utf-8 , depending on appalication, today those things are mixing without one does notice.
My further experiments show, that winpt does slightly modify the original text when used in the clipbord functions. It adds some spaces, this would not harm too much, but on some occasions some chars which have actually no proper graphics attached under windows to it. When I open such text then in word, just to get overwiew, there can be some extra chars found on some beginings of line.
Such text however mostly still can be verified, thought the key ID displayed is wrong.
When such text is sent via some media like mail or news etc, this special char will be converted to two spaces. Latests here, the verif ends.
I will try to prepare collection of texts clearsigned under different circuumstnaces in different apps , before and after transmission and will let you know.
At present I am not able to operate the winpt at home, on my home computer, w2k, with no gpg or winpt installed, the winpt does not start, it finds some 'preexisting key conflict' .
What is that? Any idea?
Otto Sykora
Basel, Switzerland
I assume you've already checked to make sure you are using the same keyfile directory (GNUPGHOME) with all the applications.
Could you post an example of a text file that you can copy to the clipboard, sign, and then have the signature fail? We might be able to replicate it and see what is going on. Maybe you could post the signature along with it.
So far, it doesn't sound like what you are describing has anything to do with the portablizing of WinPT. Perhaps you could confirm it by going to gpg4win.org and installing it on your desktop computer (for a test). If WinPT can sign text in the clipboard when installed directly, but not when it is installed via WinPT Portable, that will be helpful to know; but if the installed version behaves the same, the bug report needs to be posted on that gpg4win.org site.
MC
My day job has kept me very busy of late but I have had a little time to work on this. I have been able to reproduce some defects, and I have gotten a working build environment for WinPT.exe. So far it does not look like an issue due to portablization but just some oddity in the code. I will post again when I start narrowing in on the issue.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
Great! I need this one. Please don`t let this project be forever beta like many others. Try to become final.
I would appreciate if this could become an official portableapps.com release later.
Thanks for the interest. I initially created this to scratch an itch, but I am excited that other people are interested in it. By all means please download it, try it out, and let me know how it works for you. The most needed resource to get it out of dev test and into release is testing!
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
It created the keys successfully in the right place and the GnuPG home directory is now correct.
But .... the GnuPG exe location is still pointing to the original installation on the C drive.
excellent! thank you for testing it out. I will look into the exe location issue.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
I am monitoring this thread and also testing it inside emulator. But currently I have no more bugreports then anyone else have posted already. So, I am glad to see further versions.
If there is a local copy of GnuPG installed on a machine the gpg settings box on WinPT will report the path to that gpg.exe.
However if you replace that gpg.exe with a zero byte file everything still works as it is actually using the portable GnuPG! (assuming GnuPG CommonFiles or GnuPG for Thunderbird are installed)
This can also be verified by launching a long encrypt or decrypt and then searching for gpg.exe with process explorer. If I have time I may open up the WinPT source and see about fixing it.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
If you are fit with C and want to change the GnuPG / WinPT source the guys from WinPT would also apprecicate if you post a fix. Making it portable could be also done on source/application level (would be the harder and better way).
I know this because I was reading their mailing list / forum. This frequently requested feature has been accepted but no one of the old developers wanted to add it or had not time. So if you want to provide a patch, ask them and then them may be happy about it. Just an idea...
So, any news?
I've tried contacting the original devs to get some help setting up a compatible build environment but haven't heard anything back yet. I am still pushing ahead, just getting delayed by that silly thing called life.
If anyone has contact with the original devs let me know what their current contact info is please.
Thanks
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
Hello
The link to download winPT portable is dead!
I fall on a 404 page from the site "stinaff.com" but... it's a 404! I've many times since a week and impossible to download the app...
huhuuuu pleaaase I really need this app...
thanks a lot
Looks like Michael's site is getting redone, plus it might be that Michael is a new parent. If the latter, he may have other things occupying his time.
If he doesn't fix the link in a reasonable time, I'll post my copy on my site.
MC
Seems some files got clobbered in a website upgrade. And I have been busy with my new niece.
Glad to know that people are geting use out of WinPT Portable. I am still planning to work some bug fixes and updates into the WinPT code, but it is a back burner project right now.
You may also want to try GPA-Portable. It works with GPG Portable and does almost all the same stuff.
Key ID: 0xDAE3095F
Fingerprint: 5D98 65D2 1844 21A5 76C1 F0F6 4BE6 D689 DAE3 095F
since it refuses to do any ops on portable drive itself. What I mean, it runs from the stick, it uses the gpg on the stick fine, but when I point it to a file on the stick to be encrypted or signed it tells me this path does not exist.
Then when the file is moved to hard drive, it wants to do something, but fails half of the time with different kind of error msg, like gpa crashed , it ties to recover..
I have gpg only on the stick (pgp localy) but they do not bite each other. So I have no issues with getting response from the local gpg.exe or registry or so, but the progie behaves strange. What ever it is asked to do will work from cmd by hand, so it is just the question haw does it deal with the in/out of the gpg.
Otto Sykora
Basel, Switzerland
>
I assume you've already checked to make sure you are using the same keyfile directory (GNUPGHOME) with all the applications.So far not sure which part of it is purely winpt, which portable and which part concerns the gpg itself.
>Could you post an example of a text file that you can copy to the clipboard, sign, and then have the signature fail? We might be able to replicate it and see what is going on. Maybe you could post the signature along with it.So far, it doesn't sound like what you are describing has anything to do with the portablizing of WinPT. Perhaps you could confirm it by going to gpg4win.org and installing it on your desktop computer (for a test). If WinPT can sign text in the clipboard when installed directly, but not when it is installed via WinPT Portable, that will be helpful to know; but if the installed version behaves the same, the bug report needs to be posted on that gpg4win.org site.
Otto Sykora
Basel, Switzerland
When proxy with authentification set and I press search button program crashes with following error:
AppName: winpt.exe AppVer: 1.2.0.0 ModName: msvcrt.dll
ModVer: 7.0.2600.3085 Offset: 000378c0
version of the winpt and so far most problems I had before were solved.
Try to simply replace files from the new package and all might work.
Otto Sykora
Basel, Switzerland
Same problem after upgrading to 1.3.0. Looks like GnuPG have problems working with proxy rquiring authentification.
Hi
I'm very interrested in your effort to make GNUpg and WinPT a portable application set, but I have a little problem with these files.
Actually, for my needs, I'd like to put this application in another directory than
keyroot:\PortableApps\CommonFiles\
keyroot:\PortableApps\WinPTPortable\
But I can't figure out how to indicate to WinPT portable the path I want it to look for GNUpg lib.
So I was wondering whether there is a way to compile WinPT install with directives for it to look for GNUpg through a relative path...
For example, i'd like to be able to have this kind of structure:
keyroot:\softs\security\CommonFiles
keyroot:\softs\security\WinPTPortable
or even:
keyroot:\a_path\WinPTPortable
keyroot:\a_path\WinPTPortable\GnuPG
and this indistinctly, or by using a config file where I'd be able to set a relative path for the lib
Is there any way to achieve this?
In addition, I tried to find the GNUpg *.nsh file in order to try compiling the NSIS installer by myself with the directory structure adapted for my needs, but I wasn't be able to find it...
Where would I be able to download it, please?
Hope to be clear enough (sorry for my english)
cebelab°
Just a bump, and a big up for this from 2016.
WinPT 1.53 was released some time ago.
Can WinPT Portable be upgraded to use the latest GPG 1.4.20 ?
Now uses GPG under Thunderbird. Could a GPGlegacy for the GPG 1.4.20 branch be created in CommonFiles?
Download from:
Windows Privacy Tray - WinPT http://winpt.wald.intevation.org/
or
WinPT: Windows Privacy Tools http://winpt.sourceforge.net/
That way could manage keys and also encrypt / decrypt files.
Wikipedia says only compatible with the old GPG version. Perhaps GPA would be better https://portableapps.com/node/11600
you can use it with the gpg 1.4.20 sure. You can point it to the gpg under common files sure.
But: the winpt also in the version 1.53 is still rather buggy. So just be not too surprised when this and that does not work.
You can simply replace the winpt in the app winpt folder.
Otto Sykora
Basel, Switzerland