Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to pass user name and password when telnet to a machine

11,206 views
Skip to first unread message

gvelm...@gmail.com

unread,
Oct 7, 2005, 7:17:55 AM10/7/05
to
Hello,

How I can pass username and password as an argument when I telnet or
rlogin to a machine to avoid user interaction.

Thanks,

Velmurugan G

Thobias Vakayil

unread,
Oct 7, 2005, 7:29:55 AM10/7/05
to
Hello,

You can put the machine name, username and password in the .netrc file
and the execute the rlogin command like this :
rlogin -l <user name> <hostname>

Regards,
Thobias
gvelm...@gmail.com wrote:


--
Thobias Vakayil
Alcatel Development India (ADI)
PH: 2349961/72/86 EXTN :7018

gvelm...@gmail.com

unread,
Oct 7, 2005, 8:06:12 AM10/7/05
to
Hello Thobias,

I have tried this but it is asking for password.
What I have did is, in root's home directory:

# vi .netrc
<hostname> root <passsword>
#rlogin -l root <hostname>
password:

Any more suggestion.

Thanks
Velmurugan G

Martin Paul

unread,
Oct 7, 2005, 8:22:25 AM10/7/05
to
Thobias Vakayil <Vakayil...@alcatel.com> wrote:

> gvelm...@gmail.com wrote:
>>How I can pass username and password as an argument when I telnet or
>>rlogin to a machine to avoid user interaction.
>
> You can put the machine name, username and password in the .netrc file
> and the execute the rlogin command like this :
> rlogin -l <user name> <hostname>

I guess you haven't actually tested that ? From `man netrc`:

The .netrc file contains data for logging in to a remote
host over the network for file transfers by ftp(1).

To the OP - use ssh instead. If you think you can't use ssh, re-think.
If you *still* think that ssh is absolutely no alternative, take a
look at expect ( http://expect.nist.gov/ ).

mp.
--
Systems Administrator | Institute of Scientific Computing | Univ. of Vienna

kaming

unread,
Oct 7, 2005, 8:26:09 AM10/7/05
to
Is that your wanted to automate some procedures that require telnet to other
server and run some commands? If so, you can use an "expect" script (expect
is an command interrupters (like perl, awk ... etc.) using TCL language).

Regards,

Henry

"Thobias Vakayil" <Vakayil...@alcatel.com> wrote in message
news:1128685136.826734@slbhw0...

Rodrick Brown

unread,
Oct 7, 2005, 8:30:44 AM10/7/05
to

<gvelm...@gmail.com> wrote in message
news:1128683875.8...@g47g2000cwa.googlegroups.com...

You should really look into using ssh/ssh-agent/+keys

--
Rodrick R. Brown
http://www.rodrickbrown.com


Daniel Rock

unread,
Oct 7, 2005, 8:35:53 AM10/7/05
to
Thobias Vakayil <Vakayil...@alcatel.com> wrote:
> Hello,
>
> You can put the machine name, username and password in the .netrc file
> and the execute the rlogin command like this :
> rlogin -l <user name> <hostname>

.netrc is for ftp, you have to edit .rhosts

But don't do this. Instead use ssh with public/private keypair.

Suppose you want to login from host A to host B:

- On host A create a ssh keypair:
ssh-keygen -t dsa -N "" -f $HOME/.ssh/id_dsa

- Copy (or append) the contents of $HOME/.ssh/id_dsa.pub from host A to
$HOME/.ssh/authorized_keys on host B:
scp $HOME/.ssh/id_dsa.pub USER@HOST-B:.ssh/authorized_keys
(copy)
ssh USER@HOST-B "cat >> .ssh/authorized_keys" < $HOME/.ssh/id_dsa.pub
(append)
Make sure the $HOME/.ssh directory exists on host B and has permissions 700.

- If you want a passwordless root-login you have to enable direct root-logins
via ssh. On Host B edit /etc/ssh/sshd_config and change the relevant line to
PermitRootLogin no
or
PermitRootLogin without-password
For details read the manual page sshd_config(4).
Then restart the ssh daemon:
svcadm restart ssh (Solaris 10)
or
/etc/init.d/sshd stop; /etc/init.d/sshd start (Solaris 9)


--
Daniel

gvelm...@gmail.com

unread,
Oct 7, 2005, 8:52:07 AM10/7/05
to
Hello Daniel,

yep .netrc is for ftp, anyhow thanks for the tips Thobias. SSH sounds
good, but is there is anyway to pass username and password as a
parameter for telnet or rlogin without interaction of user. I dont
wanna edit .rhosts.

Thanks,

Velmurugan G

Edward M.

unread,
Oct 7, 2005, 8:59:24 AM10/7/05
to
Message has been deleted

gvelm...@gmail.com

unread,
Oct 8, 2005, 8:59:47 AM10/8/05
to
Hello Edward,

I have tried this site " http://steve-parker.org/sh/hints.shtml " and
came across one script.

telnet1.sh :

#!/bin/sh
host=sunfi75
port=23
login=root
passwd=Gan@Kri
cmd="ls /tmp"

echo open ${host} ${port}
sleep 1
echo ${login}
sleep 1
echo ${passwd}
sleep 1
echo ${cmd}
sleep 1
echo exit


#telnet1.sh | telnet

It is working fine and what the problem is, it exits after 1 second
even when I commented out the line.
.............
...........
#echo exit
.............

Any suggestion ?


Thanks,

Velmurugan G

gvelm...@gmail.com

unread,
Oct 8, 2005, 9:20:25 AM10/8/05
to

Bruce D Porter

unread,
Oct 8, 2005, 9:53:32 AM10/8/05
to

Yes, do as huge suggests and use ssh
:-)

Or, if you really really really want to use telnet, use expect


--
Bruce

"The internet is a huge and diverse community and
not every one is friendly"
http://www.ytc1.co.uk

Logan Shaw

unread,
Oct 8, 2005, 12:05:17 PM10/8/05
to

If it exits not matter what you do, and if you want it not to exit,
then how does that qualify as "working fine"?

The fact of the matter is, it is not working fine, and there is no
way to modify this script to do what you want. As soon as the script
exits, telnet will get an end-of-file on its standard input, and it
will close the connection and exit. There is no way to modify the
script to provide an *interactive* login session.

> Any suggestion ?

Yes, use ssh. telnet does not have the feature you want.

- Logan

rudrasamal

unread,
Aug 17, 2012, 4:02:31 PM8/17/12
to
Most of people know abt ssh and its Automation. There are few case u cant modify a remote server authentication file, so u need a way to pass your username and password while write a non user interactive one script. instead of suggesting a way for that you guys only say ssh and all abt its authentication. All know that, say something if you know more.

--http://compgroups.net/comp.unix.solaris/how-to-pass-user-name-and-password-when-tel/40654


Gary R. Schmidt

unread,
Aug 17, 2012, 8:40:45 PM8/17/12
to
On 18/08/2012 6:02 AM, rudrasamal wrote:
> Most of people know abt ssh and its Automation. There are few case u cant modify a remote server authentication file, so u need a way to pass your username and password while write a non user interactive one script. instead of suggesting a way for that you guys only say ssh and all abt its authentication. All know that, say something if you know more.
>
> --http://compgroups.net/comp.unix.solaris/how-to-pass-user-name-and-password-when-tel/40654
>
>
I *think* the answer to what you are asking is "expect"[1], but I could
be wrong, either in that you are actually asking a question or what it
is about.

Cheers,
Gary B-)

1 - here: <http://expect.sourceforge.net/>
--
When men talk to their friends, they insult each other.
They don't really mean it.
When women talk to their friends, they compliment each other.
They don't mean it either.

Michael

unread,
Aug 18, 2012, 2:24:27 PM8/18/12
to
hi,

On 08/17/12 10:02 PM, rudrasamal wrote:
> Most of people know abt ssh and its Automation. There are few case u cant modify a remote server authentication file, so u need a way to pass your username and password while write a non user interactive one script. instead of suggesting a way for that you guys only say ssh and all abt its authentication. All know that, say something if you know more.
>
> --http://compgroups.net/comp.unix.solaris/how-to-pass-user-name-and-password-when-tel/40654
>
>
I use expect for such things, its perfect!

/michael



pndy...@gmail.com

unread,
Apr 8, 2014, 5:40:03 AM4/8/14
to
I think I landed on the same solution years after you. But fortunately I was able to control the command flow and run the script as it is.

Just reminding you that it's still useful.

Thank You.

hume.sp...@bofh.ca

unread,
Apr 8, 2014, 1:11:50 PM4/8/14
to
pndy...@gmail.com wrote:
> Just reminding you that it's still useful.

I would disagree. It was a bad idea in 2005, and it's a REALLY bad idea now.

SSH exists and people should use it. If your organization hasn't updated
their security policies to REQUIRE (not just allow) SSH instead of telnet,
then there's no hope for you.

--
Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

Dirk Heinrichs

unread,
Apr 9, 2014, 12:06:53 PM4/9/14
to
hume.sp...@bofh.ca wrote:

> I would disagree. It was a bad idea in 2005, and it's a REALLY bad idea
> now.

That's what I would have replied too, if you didn't already :)

Bye...

Dirk
--
Dirk Heinrichs <dirk.he...@altum.de>
Tel: +49 (0)2471 209385 | Mobil: +49 (0)176 34473913
GPG Public Key CB614542 | Jabber: dirk.he...@altum.de
Sichere Internetkommunikation: http://www.retroshare.org

0 new messages