topic Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error in Operating System - HP-UX

stdin & ssh: "Pseudo-terminal will not be allocated..." error

Haralambos — Mon, 23 Jan 2006 10:34:16 GMT

Hi,

Is there a good way to programmatically pass my password or public key to ssh (OpenSsh 3.91)?

When I do either:

echo "mypasswd" > ssh myhost -l user

or

ssh myhost -l user << EOF
mypasswd
EOF

I get the following error:
"Pseudo-terminal will not be allocated because stdin is not a terminal"

So, the real question is how do I have scripts/applications use ssh without user intervention? Ok, I can use public key authentication with ssh-agents but in my environment do not have time for the users to enter data in the agent. I want the server to come up with no user input wharsoever.

regards,

haralambos

Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error

Victor Fridyev — Mon, 23 Jan 2006 11:27:37 GMT

Hi,

ssh_keygen -t dsa
scp ~.ssh/dsa_pub host:/root/.ssh/authorized_keys

The procedure for root, change it accordingly.

HTH

Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error

Simon Hargrave — Mon, 23 Jan 2006 11:39:13 GMT

The only way to have no interaction and not to have to use agents is to have passphraseless keys. Obviously these are less secure than keys with passphrases, however clearly they are many times more secure than rlogin! It's your call to weigh up convenience with security.

Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error

TwoProc — Mon, 23 Jan 2006 11:41:48 GMT

If you don't want to generate a key as per the previous posting, you can use the program called "expect". It's at the HPUX porting archive. I've used it sucessfully for exactly what you're needing. http://hpux.cs.utah.edu/hppd/hpux/Tcl/expect-5.43/

Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error

Haralambos — Mon, 23 Jan 2006 12:19:08 GMT

Yeah!!!

I really want to keep my keys passphrase encrypted and at the same time have the convinience of no-human interaction at boot time. I mean, ssh-agents can be actually used but again the requirement is to not have the users enter the passphrase.

So, how can the "expect" scripts work in this case? Can you provide an example? When and how are they being kicked-off and how is the passphrase/passwd passed to them; is it hardcoded?

Regards,

Haralambos

Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error

TwoProc — Tue, 24 Jan 2006 08:33:55 GMT

It's a scripting language that has the ability to listen (to the screen I/O) and "wait-for" events, and then reply. Yes, you hard code the password in the expect script, so you have to watch the security level on the file very closely.

I don't have any working examples handy, but if you search these forums for "expect" you'll find some.

Re: stdin & ssh: "Pseudo-terminal will not be allocated..." error

Haralambos — Fri, 27 Jan 2006 09:48:41 GMT

Well, I am not sure if this is solution will work in our environment but I will give it a shot anyway.

Thanks for the tips!

regards