Sponsored Content
Full Discussion: Automation of telnet and ftp
Top Forums UNIX for Dummies Questions & Answers Automation of telnet and ftp Post 9945 by Kelam_Magnus on Monday 5th of November 2001 10:43:32 PM
Old 11-05-2001
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...


Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Urgent FTP script automation

Hi guys, Here is my requirement for ftp script that i have to automate in unix using shell script: 1) Find the files that atre created one week from the present day. 2) ftp them to the backup server. 3) At the end of the month make a new directory on my backup server with the new month(eg:Once... (1 Reply)
Discussion started by: koduri0475
1 Replies

2. UNIX Desktop Questions & Answers

Urgent FTP script automation

Hi guys, Here is my requirement for ftp script that i have to automate in unix using shell script: 1) Find the files that atre created one week from the present day. 2) ftp them to the backup server. 3) At the end of the month make a new directory on my backup server with the new month(eg:Once... (1 Reply)
Discussion started by: koduri0475
1 Replies

3. Filesystems, Disks and Memory

Urgent FTP script automation

Hi guys, Here is my requirement for ftp script that i have to automate in unix using shell script: 1) Find the files that atre created one week from the present day. 2) ftp them to the backup server. 3) At the end of the month make a new directory on my backup server with the new month(eg:Once... (1 Reply)
Discussion started by: koduri0475
1 Replies

4. Cybersecurity

FTP Automation Windows <> Unix <> Remote

Hi All, I am a newbie to unix and scripting. I need to do the following job: 1. Create a batch file in windows that will call a script in a remote unix box. 2. The script now ftp files from the Remote windows machine and get them back to the local windows. Actually, I have written the script... (3 Replies)
Discussion started by: Ankur
3 Replies

5. UNIX for Advanced & Expert Users

FTP automation Job scheduling

Hi, I am working in Unix and Teradata fastload. I need to automate file transfer through ftp from windows path to Unix directory at a specific time, then I should call fastload scripts execution. I have got the fastload script. Entire process should be automated without any manual intervention. It... (1 Reply)
Discussion started by: SATYAPRIYA_D
1 Replies

6. Shell Programming and Scripting

How to track exit status of ftp automation

ftp automation code is ftp -v -n -i $host_name << EOF user $u_name $u_pass bi mput $tar_file bye EOF How to check whether the file is successfully transfered or not. Suppose the user name or password is provided wrongly then the code should track the error and ask the end user to enter... (2 Replies)
Discussion started by: Dip
2 Replies

7. Shell Programming and Scripting

FTP automation script

Hi, I have got a requirement like this. a parameterized function custFtp which will take 5 i/ps and will do the following tasks. p1) server name p2) username p3) password p4) path name of the server where the file resides p5) file name pattern the function will work like this. ... (1 Reply)
Discussion started by: ani_datta
1 Replies

8. AIX

Automation from Windows to Linux - Telnet and su using perl

Here is my requirement to automate the deployment procedure for my project. Telnet to AIX box (say SERVER1) from windows machine (with USER1) Select the server to login say "SERVER2" su as different user say "USER2"(Owner of the deployed files) Execute the script (Script has so many... (1 Reply)
Discussion started by: nurainos
1 Replies

9. Shell Programming and Scripting

FTP automation with special characters in userid

Hi, i am trying to automate an ftp script which is as below.But my user id has special characters(aaa\$ifg). So it is not working correctly.Can anyone help on this?I tried providing both of them in double & singe quoted. But somehow it is not picking the "\". Also tried keeping \ before the... (3 Replies)
Discussion started by: aeroticman
3 Replies

10. Shell Programming and Scripting

EXPECT script for Telnet automation. Need your support.

Dear experts, please help me . I've found simple EXPECT scripts and all works fine. But I need more automation in error handling and sending list of commands/output logging from multiple remote hosts. I have 10 hosts, for example: host1 192.168.1.1 LOGIN1 PASSWORD1 ...... ... (2 Replies)
Discussion started by: starchen
2 Replies
HOSTS.EQUIV(5)						      BSD File Formats Manual						    HOSTS.EQUIV(5)

NAME
hosts.equiv, .rhosts -- trusted remote host and user name data base DESCRIPTION
The hosts.equiv and .rhosts files contain information regarding trusted hosts and users on the network. For each host a single line should be present with the following information: simple hostname [username] or the more verbose [+-][hostname|@netgroup] [[+-][username|@netgroup]] A ``@'' indicates a host by netgroup or user by netgroup. A single ``+'' matches all hosts or users. A host name with a leading ``-'' will reject all matching hosts and all their users. A user name with leading ``-'' will reject all matching users from matching hosts. Items are separated by any number of blanks and/or tab characters. A ``#'' indicates the beginning of a comment; characters up to the end of the line are not interpreted by routines which search the file. Host names are specified in the conventional Internet DNS dotted-domains ``.'' (dot) notation using the inet_addr(3) routine from the Inter- net address manipulation library, inet(3). Host names may contain any printable character other than a field delimiter, newline, or comment character. For security reasons, a user's .rhosts file will be ignored if it is not a regular file, or if it is not owned by the user, or if it is writable by anyone other than the user. FILES
/etc/hosts.equiv The hosts.equiv file resides in /etc. $HOME/.rhosts .rhosts file resides in $HOME. EXAMPLES
bar.com foo Trust user ``foo'' from host ``bar.com''. +@allclient Trust all hosts from netgroup ``allclient''. +@allclient -@dau Trust all hosts from netgroup ``allclient'' and their users except users from netgroup ``dau''. SEE ALSO
rcp(1), rlogin(1), rsh(1), gethostbyname(3), inet(3), innetgr(3), ruserok(3), netgroup(5), ifconfig(8), yp(8) BUGS
This manual page is incomplete. For more information read the source in src/lib/libc/net/rcmd.c or the SunOS manual page. BSD
December 25, 2013 BSD
All times are GMT -4. The time now is 09:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy