Metro PuTTY - port of PuTTY to the Windows Store (SSH app)

[BannanaNinja]

Hey guys,

 

I have been working on a port of PuTTY to the Windows Store for quite some time and I finally have it to the point where I can release it. Many of the options of PuTTY are supported and I hope to add many more features in the next few weeks. I'd appreciate any feedback and feature requests so I know what features to prioritize. There is a trial version so you do not have to buy it.

 

Thanks!

Matt

 

http://apps.microsoft.com/windows/en-us/app/metro-putty/29c3210d-11c2-4348-83d3-79d2f414cc98

 

Supported features include:

- Save session settings that sync with MS account

- Copy and Paste

- UTF-8

- Private key authentication with PuTTY keys

 

Screenshots attached.

[greenwizard88]

Awesome, I've been waiting for a good SSH app in the store! I'll give it a try later tonight and let you know if there's any feedback.

[BannanaNinja]

Cool thanks!

[greenwizard88]

Well, I just tried it to simply SSH into my server at work, and it was pretty fantastic. I'm testing this on my Surface next, but I'll probably buy it today or next week sometime.

[snaphat (Myles Landwehr) Member]

You need to add the following license information somewhere, otherwise you are in violation of the license even though you state that it's a port and link to the documentation: http://www.chiark.greenend.org.uk/~sgtatham/putty/licence.html

[BannanaNinja]

You need to add the following license information somewhere, otherwise you are in violation of the license even though you state that it's a port and link to the documentation: http://www.chiark.greenend.org.uk/~sgtatham/putty/licence.html

 

I have it in the about page inside the app. In the first screenshot you can see the about button at the bottom of the page. Clicking that will show the copyright information and show another button labeled license. Clicking the license button will then show that license. This is mimicking PuTTY's behavior exactly. Do you think I should also put it in the app description somewhere?

[snaphat (Myles Landwehr) Member]

I have it in the about page inside the app. In the first screenshot you can see the about button at the bottom of the page. Clicking that will show the copyright information and show another button labeled license. Clicking the license button will then show that license. This is mimicking PuTTY's behavior exactly. Do you think I should also put it in the app description somewhere?

 

I somehow missed that when I was looking. Just add the information on your additional terms page.

[BannanaNinja]

Well, I just tried it to simply SSH into my server at work, and it was pretty fantastic. I'm testing this on my Surface next, but I'll probably buy it today or next week sometime.

 

Awesome! I am trying to get an update out by the end of today or tomorrow to fix a private key issue and then some font size/type customizing. If you have any feature requests please let me know!

[BannanaNinja]

I somehow missed that when I was looking. Just add the information on your additional terms page.

 

Ok, that's fair. The next update (which is as soon as I fix a crashing bug) will include that. Thanks for making sure I'm following all the licenses!

[snaphat (Myles Landwehr) Member]

Ok, that's fair. The next update (which is as soon as I fix a crashing bug) will include that. Thanks for making sure I'm following all the licenses!

 

you should be glad it's a BSD/MIT license since that isn't copy-left and makes it easy to incorporate into apps (and make derivative products) and make monies ;-)

[BannanaNinja]

you should be glad it's a BSD/MIT license since that isn't copy-left and makes it easy to incorporate into apps (and make derivative products) and make monies ;-)

 

:) Yes. When I was first joking with my friend about porting it to the Windows Store I wasn't expecting such a lenient license. That's when it stopped being a joke and I began to dig through the code to see if I could seriously port it.

[Shaun N.]

I'm happy to see this, I'll give it a whirl 

[riahc3]

Hello,

you should be glad it's a BSD/MIT license since that isn't copy-left and makes it easy to incorporate into apps (and make derivative products) and make monies ;-)

Personally, I find it disgusting that the license allows you to copy the code, close source it, then sell it if you wish (like OP). Easy money.

[MorganX]

Excellent

[snaphat (Myles Landwehr) Member]

Hello,

Personally, I find it disgusting that the license allows you to copy the code, close source it, then sell it if you wish (like OP). Easy money.

 

To each his own, the author didn't want a copy-left license for whatever reason, the same as the *BSDs. I've released code under similar licenses in the past.

 

The OP put more effort into it than simply copying the code anyway. There's a ton of software that incorporates PUTTY code similar to the OPs code. 

 

LLVM has the the same license. Without a permissive license like that, LLVM would not be the research platform it is today. People generally dislike the restrictions that come with GPL code for research for the very reason that distribution requires distributing ones code. Moreover, in many cases it can be incompatible with the terms of research grants.

 

In my opinion, building upon an existing code base is perfectly acceptable if you are offering something that wasn't available before. It's one thing to just compile the code and then pretend you did something, and quite another to use it to make a product that wasn't available before.

[greenwizard88]

Hello,

Personally, I find it disgusting that the license allows you to copy the code, close source it, then sell it if you wish (like OP). Easy money.

While I can understand that, I wouldn't be so quick to judge. Sometimes, it's nice to be able to use components in this manner.

 

For example, I worked on a project last month where we needed to be able to use an Android tablet in a non-standard way. I had code from Google, that did exactly what I wanted it to do, but because of the GPL license, couldn't use it as even a component of a much larger project for my company.

 

Why did Google choose to give it a GPL license? Because their project used a component that had a GPL component in it.

[Wannes]

Looks great, I might even spend a few bucks on this one. :)

[goretsky Supervisor]

Hello,

 

Sounds useful!  Just bought a copy to play with later...

 

Regards,

 

Aryeh Goretsky

[+Fahim S. MVC]

Hello,

Personally, I find it disgusting that the license allows you to copy the code, close source it, then sell it if you wish (like OP). Easy money.

 

Like all the open source components of VMWare ESXi, Mac OS X, Google Chrome etc?

Hey guys,

 

I have been working on a port of PuTTY to the Windows Store for quite some time and I finally have it to the point where I can release it. Many of the options of PuTTY are supported and I hope to add many more features in the next few weeks. I'd appreciate any feedback and feature requests so I know what features to prioritize. There is a trial version so you do not have to buy it.

 

Thanks!

Matt

 

http://apps.microsoft.com/windows/en-us/app/metro-putty/29c3210d-11c2-4348-83d3-79d2f414cc98

 

Supported features include:

- Save session settings that sync with MS account

- Copy and Paste

- UTF-8

- Private key authentication with PuTTY keys

 

Screenshots attached.

 

How does it deal with application suspension and maintaining connectivity? Am I going to have to log in every time I want to switch to the app?

[BannanaNinja]

 

How does it deal with application suspension and maintaining connectivity? Am I going to have to log in every time I want to switch to the app?

 

It currently does not do anything. However, Windows does not close your socket right away, so the connection will stay open for some time while it is minimized (or even suspended). I think the best route is to do some kind of background task to keep the connection alive but I haven't had much time to look into this. Once I finish the current release (it's in testing now so shouldn't be long) this is one of the next major issues I want to tackle.