Comments on: SSH Programming with Paramiko | Completely Different

By: jnoller

jnoller — Fri, 13 Nov 2009 16:18:05 +0000

You should email the paramiko mailing list for support

By: hima

hima — Fri, 13 Nov 2009 15:08:51 +0000

sudo over paramiko doesn't work. It gives exception that ” U require a tty to run sudo”.
My server is having requiretty = true . Due to security problem, this setting cant be changed. I will have to handle it through paramiko.
Pls Help……..

By: jnoller

jnoller — Fri, 13 Nov 2009 10:18:05 +0000

You should email the paramiko mailing list for support

By: hima

hima — Fri, 13 Nov 2009 09:08:51 +0000

By: jnoller

jnoller — Fri, 30 Oct 2009 21:48:55 +0000

Given the article was about SSH programming, and paramiko is for SSH
programming - I think it's a much better fundamental solution to SSH
programming than pexpect. I've had plenty of expect-like scripts, and
expect-base script break because assumption on output, regexes, etc
broke. I agree that paramiko isn't a generalized tool, but for the
problem it tries to solve it is the best tool (in my opinion).

If we were talking a general "watch something and react" tool, then
yeah - pexpect makes sense, but we're not.

By: Mike

Mike — Fri, 30 Oct 2009 21:35:54 +0000

Actually something expect-like doesn't care what the output is if you code the same way you do with paramiko. pexpect.expect takes a list of args… that list can be regular expressions or perhaps pexpect.TIMEOUT or pexpect.EOF. Based on that which one in that list matches, you make a decision; this is not an issue of a small decision tree. I'm ok with people using other tools, but lets be fair to the tools available. pexpect is a much more generalized solution than paramiko; paramiko gives you more granular visibility into stderr than pexpect does, but paramiko is limited to ssh.

By: jnoller

jnoller — Fri, 30 Oct 2009 18:36:31 +0000

Personally, I've found any tool which waits for specific output from
commands to be terribly brittle. Output from remote sources can (and
does) frequently change - sure, something expect-like does the job if
you can count on the same output over and over again.

I know pexpect has gotten better since the time I used it, which
admittedly was awhile ago and at this point I go out of my way to
avoid it/expect-like tools unless I simply can't. I'm also much more a
fan of tackling things with tools like paramiko, which is more
programmatic/reliable in my mind.

By: Mike

Mike — Tue, 27 Oct 2009 15:47:05 +0000

I'm curious about something mentioned above... you seem to discourage use of pexpect for driving ssh sessions, but you launched into issues with 'subprocess' without specific comments about why pexpect isn't a winner for you. Have you had bad experiences with pexpect, and if so please elaborate...

Having used pexpect to drive cisco routers for the last 3 years, I have to say it's been nothing but pleasant to me.

Thoughts?
m

By: xav.vijay

xav.vijay — Thu, 24 Sep 2009 01:18:33 +0000

Hi

I followed ur example for paramiko and my code is like this..

import paramiko
import os

ssh = paramiko.SSHClient()
ssh.load_system_host_keys()
ssh.set_missing_host_key_policy(paramiko.AutoAddPolicy())
ssh.connect('server-name',22,'root','password')
stdin, stdout, stderr = ssh.exec_command("ssh -V")
stdout.readlines()

But, I am getting the following error!! ... I am not sure why...Can u please help!!
Traceback (most recent call last):
File "C:Documents and Settingsaannas01My DocumentsDownloadsssh-ver.py", line 18, in
in
ssh.connect('server-name',22,'root','password')
File "C:Python26libsite-packagesparamikoclient.py", line 309, in connect
self._auth(username, password, pkey, key_filename, allow_agent, look_for_keys)
File "C:Python26libsite-packagesparamikoclient.py", line 463, in _auth
raise saved_exception
BadAuthenticationType: Bad authentication type (allowed_types=['publickey', 'keyboard-interactive'])

I have no clue why the error is asking for a different set of parameter. I am on a Windows XP machine, and trying to login to a Linux machine...

By: Rachael

Rachael — Fri, 26 Jun 2009 20:12:49 +0000

Minor thing that probably no one else noticed, but when you talk about putting and getting, you say “ftp.get” both times, but if you're putting the command is actually “ftp.put”. I'm probably an idiot for not picking up on that, but it is mildly confusing.