I’m asking myself this reading the last time various threads here and elsewhere about how to install and use putty under Linux. What is putty? Originally it was written for windows cause that system didn’t have a built in ssh-client. Very nice toy. You can download it and start it without any installation. You can even start it from floppy disk. Using windows putty imho is the best ssh-client.
But why using it with Linux? Linux has a built in client. Just open a terminal and type ssh … Everything you can do with ssh you can do with that built in command. So why another tool? Is there any extra use offered by putty?
> But why using it with Linux? Linux has a built in client. Just open a
> terminal and type ssh … Everything you can do with ssh you can do with
> that built in command. So why another tool? Is there any extra use
> offered by putty?
Maybe admins in mixed environments just want to use the same tool?
> But why using it with Linux? Linux has a built in client. Just open a
> terminal and type ssh … Everything you can do with ssh you can do with
> that built in command. So why another tool? Is there any extra use
> offered by putty?
I have told that it is nice.
I haven’t tried it, but if it has a similar configuration to the windows cousin, then you can have
clickable configurations for different machines, ready to run. Some machines you have to connect to
maybe are not linux, they need some special setting, maybe some keys don’t work, or you have to
change fontset or charset… of course it is doable with plain xterm and such, but you need to
change a lot of things each time or have your own script.
Having entries for each machine can be handy.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
PuTTY does have a nice gui interface and it’s easy to configure.
But since it uses wine it could bring some overhead with it.
I found Minicom works just fine for my needs though, configuring routers.
If someone wanted ssh under Wine?
Most of us agree with you about opening a terminal window and typing ssh.
Putty does have a GUI to configure all options including certificates, passphrases, authentication not found in terminal.
With Putty you run Puttygen or Putty-keygen, generate the keys and tell Putty where note where the private and public keys were placed.
OTOH, terminal leaves it up to the user to hunt down the manpages and onliine help for ssh.
On 2010-08-20 09:06, ns89 wrote:
>
> PuTTY does have a nice gui interface and it’s easy to configure.
> But since it uses wine it could bring some overhead with it.
Not really.
Note that it is not the same using a native windows app via wine as an emulator, than a native linux
app that links to wine libraries, so that the devs do not need to redesign the program when
migrating from windows to linux - which is the case here, IMO.
As an emulator, there is an overhead. As a library, no.
> I found Minicom works just fine for my needs though, configuring
> routers.
For me, minicom is very good. But putty handles also ssh, telnet…
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Elessar))
On 2012-11-28 02:16, clarencedold wrote:
>
> ns89;2209276 Wrote:
>>
>> But since it uses wine it could bring some overhead with it.
>>
>
> I don’t think putty uses wine.
> /usr/bin/putty: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> dynamically linked (uses shared libs), for GNU/Linux 2.6.18, stripped
There are two ways of using wine.
One is by a native Windows program, via wine “emulator”.
Another is via a native Linux program that instead of calling typical
Linux functions instead call Linux functions of the Wine API. It is a
port of a Windows program making calls similar to those it would make in
Windows, but instead done to Linux native calls. It is easier to port in
this manner, you don’t have to redesign the interface code.
To know if putty uses Wine you have to find out what it links.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I have never seen a use for putty on linux - until yesterday.
After reading the discussion, I checked and saw that putty is in the standard repos. So I installed it on one system. I was not expecting to find it useful.
But I discovered why it is useful.
When I first tried it to login to a campus system, it asked for the loginid.
It turns out, that is what I find useful (though it can be turned off). I sometimes have students during office hours, who want to login to a department system to demonstrate something. And, with command line ssh, I have to first ask them their loginid. With putty, I can just start the application, and turn the screen over to them.
Oh, and in case somebody wanted to know: putty does use the running ssh-agent, and any keys that it might hold. However, it does not use $HOME/.ssh/known_hosts nor does it use /etc/ssh/ssh_known_hosts
For most of what I do, I continue to use the standard ssh client (from openssh). But I have found a use for putty.
I like using PuTTY in Windows at work because it does make it easy for me to pre-configure my connections and control the screen/system colors (red for production, basic for test environments). I would have to research how to use the private key option and such in the terminal.
Can any RDP clients or something similar contain saved sessions/login information so connecting is easier once set up?
On 2012-12-05 15:56, redhatlinux10 wrote:
>
> putty support X11 forward, is this feature supported by openSUSE or
> other distro’s default ssh client ?
If you use putty in Windows, a very interesting tool is MobaXterm. It is
a terminal with an X server included, so that you can launch graphical
Linux tools directly.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
