![]() |
|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
|
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| S-174: Vulnerability in OLE Automation | iBot | Security Advisories (RSS) | 0 | 02-12-2008 04:30 PM |
| Web automation using perl | gurukottur | Shell Programming and Scripting | 1 | 10-10-2007 09:22 PM |
| FTP automation Job scheduling | SATYAPRIYA_D | UNIX for Advanced & Expert Users | 1 | 04-27-2007 07:13 AM |
| X11 automation? | dlundh | OS X (Apple) | 1 | 04-18-2007 05:20 AM |
| Urgent FTP script automation | koduri0475 | UNIX for Dummies Questions & Answers | 1 | 11-10-2005 07:58 AM |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
|
Automation of telnet and ftp
I have a basic query. I use telnet and ftp very frequently. I want to do it without spending time in typing username and password everytime. I know that if I have .netrc file which contains server address, username, pasword, then just typing ftp will conect to that server with that username and password. Similarly is it possible to do that for telnet? Will be grateful if someone can help me. Thanks and regards
Asutosh |
| Forum Sponsor | ||
|
|
|
#2
|
||||
|
||||
|
No. I do not think it is possible. The most you can do is "telnet -l <I>username</I>", but that is not supported on many systems. You can use ssh as an alternative which will do what you want.
|
|
#3
|
|||
|
|||
|
Telnet isn't very secure
I would advise against telnet at all costs if it can be avoided. The username and password get transmitted in clear text. Try ssh2 or even ssh (but ssh and openssh have problems with security) if at all possible. One major advantage of ssh is that you can place your public key on the remote machines and gain auto login abilities.
|
|
#4
|
||||
|
||||
|
Re: Telnet isn't very secure
Quote:
|
|
#5
|
|||
|
|||
|
Thanks. But on solaris, telnet -l username works. But that again asks for username and password.
I could not find any documentation on ssh and ssh2. On solaris, it is not working. I work on solaris. Can U tell something? |
|
#6
|
|||
|
|||
|
I am aware of at least 3 major problems with OpenSSH recently. These I believe are 2.x versions. 1.x versions have problems associated with SSH1 which have been addressed by SSH2, but the OpenSSH problems recently found (which have been addressed) are 2.x problems in OpenSSH not found in the commercial SSH2, to my knowledge.
I don't have the specifics off hand, but searching through some of the security sites such as Bugtrax should turn these up. |
|
#7
|
||||
|
||||
|
trusted vs non-trusted environments
If your systems exist in a trusted "secure" environment, inside a firewall, and you don't go outside that firewall, then you can use .rhosts and rlogin.
Each user has to be defined on the other system in a .rhosts file in the home directory of the user. For root, it should be in / or /root depending on the version. Then you can use the command rlogin hostname -l username, and it will get you right in. Your syntax may vary. Telnet is risky in an exposed environment, but I work for a very large telecom company in Dallas and we use it all the time. The key is to disable the .rhosts file when it is not in use and also restrict it to the System Admin only while preventing users from creating .rhosts files in their home directories. By limiting the use of .rhosts, you can prevent unscruplous users from allowing people into your systems. I hope that doesn't sound preachy, but it is true. Security doesn't mean shutting everyone out all the time. You have to have a certain level of trust some of the time, for any work to get done. Sorry, preachy again... I'll get off my soapbox now...
__________________
My brain is your brain |
||||
| Google The UNIX and Linux Forums |