Changelog

Changelog of the changes in PuTTYwincrypt

0.68 - 20170226

1. Upgraded patch to PuTTY 0.68.

0.67 - 20160503

1. Upgraded patch to PuTTY 0.67.

0.64 - 20150514

1. Upgraded patch to PuTTY 0.64.

0.63 - 20140201

1. Upgraded patch to PuTTY 0.63.
2. Added CNG/KSP support.
3. Fixed pageant issue in which users were prompted for PIN every time after smartcard reinsertion.

0.62 - 20120424

1. Faster load times of keys.
2. Double click on key in pageant to export public part to clipboard.
3. Cygwin build support.
4. Major refactoring of the code in order to better follow the PuTTY code.

0.62 - 20120320

1. Initial release

[Charlie Watson]

Do you intend to update this fork with the current release puTTY 0.64?

[Ulf Frisk]

Yes. An update will be published shortly. Hopefully within a few Days, a few weeks at the very most.

[Ulf Frisk]

The 0.64 update is now published. Thank you for the reminder.

[Darren DeHaven]

Hi Ulf, great project!

I've tested putty-wincrypt to connect from my windows machine to my linux servers via SSH.

Results are as follows:
-- Success: putty-wincrypt via SmartCard Cert and Pin
-- Failure: putty-wincrypt via SmartCard Cert and Pin, when all the following are true:
* pageant-wincrypt was open
* pageant-wincrypt had my certificate in its key list
* my putty-wincrypt session has the check box enabled for "Attempt Authentication using pageant"
* After using my cert with putty-wincrypt (the first connection would work with pageant-wincrypt (it would ask for my pin the first time, but the second attempt would fail as it wouldn't ask for my pin again.)
* Workaround: I either close pageant-wincrypt, remove the cert from pageant-wincrypt key list, or uncheck the attempt to using pageant box.

-- Success: putty via a software self-signed certficate that I generated and installed into the windows certificate store.
Here's how to generate a Client-side self-signed certificate, which you install into your local windows system, then add the ssh-rsa line to your remote server's authorized_keys file.
https://gist.github.com/mtigas/952344

-- Failure: using the self-signed software cert, but with "Strong Private Key Encryption" enabled (with either medium or high security).
* Workaround: Uncheck the "Strong Private Key Encryption" box when using the certificate import wizard.

[Bilou]

Not a valid Win32 application error message when launching 20150514_064 build.

My OS is 32-bit. [Windows Embedded Standard 2009, componentized version of Windows XP.]

Is build compiled only for 64-bit OS or OS is missing dependencies to run this build?

Previous build 20140201 runs fine.

[Ulf Frisk]

It's a 32-bit application - but it's compiled with the standard settings in Visual Studio 2013. This means that there is no XP support. I'll look into adding XP-support when I update to PuTTY 0.65. Meanwhile an erlier version should work okay.

[Bilou]

I need to switch to more recent PuTTY release because older releases fails with key exchange protocols OpenSSH 6.9 and implementing secure settings
https://stribika.github.io/2015/01/04/secure-secure-shell.html
sshd_config

KexAlgorithms diffie-hellman-group-exchange-sha256

http://rakhesh.com/linux-bsd/kitty-with-fedora-22-openssh-6-9-gives-a-blank-screen-and-hangs/
same issue with putty_wincrypt_20140201 and OpenSSH 7.1

Will wait new 0.65 based build. hope you can also targeting Windows XP.
http://stackoverflow.com/questions/11305633/xxxxxx-exe-is-not-a-valid-win32-application

Thanks

[Ulf Frisk]

Okay, thanks, I'll see what I can do when I update to 0.65 (within a few weeks). You could also try to download an earlier version of pageant_wincrypt and the latest standard putty and use them together.

[Bilou]

Hi,

Thanks for the latest release.

One annoying popup

warning message that says “The Publisher Could Not Be Verified” when i
run binary in Microsoft Windows XP.

bin launched from local disk, not from network share or download folder.

no problem with previous release.

Regards.

On Sun, Sep 27, 2015 at 6:54 PM, Ulf Frisk ufrisk@users.sf.net wrote:

Okay, thanks, I'll see what I can do when I update to 0.65 (within a few
weeks). You could also try to download an earlier version of
pageant_wincrypt and the latest standard putty and use them together.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/puttywincrypt/wiki/Changelog/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Ulf Frisk]

The .exe isn't signed, hence the warning message. The reason why the .exe isn't signed is that I'm not too keen paying lots of money to symantec for a code signing certificate for individuals. You should be able to uncheck the "Always ask before opening the file" in the warning dialogue and it will go away permanently.

[Chris van Marle]

Are you planning to update to 0.68, released on Feb 21?

[Ulf Frisk]

Yes, I plan to look into it this weekend.

[Chris van Marle]

Nice! Much appreciated!

[Al B]

Hello, thanks for your hard work on the matter!
Please advise if I can autoload my certificate on pageant start, as it is with key files in original software.
Thanks in advance!