|
|
Sponsored Content
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
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...
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...
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT OSF1
rhosts
rhosts(4) Kernel Interfaces Manual rhosts(4) NAME
rhosts, .rhosts - Specifies remote users that can use a local user account SYNOPSIS
$HOME/.rhosts DESCRIPTION
The .rhosts file contains a list of remote users who are not required to supply a login password when they execute the rcp, rlogin, and rsh commands using a local user account. The .rhosts file is a hidden file in your home directory. It must be owned by you or the root user and it must not be writable by group or world, otherwise, it is not used. Moreover, although it is not required, it is sensible to set the permissions of the file to 600, so the file is not readable by group or world. Each entry in the file is of the following form: host [user] where: The name of the remote host. If the remote host is in a different domain than the local host, the full domain name must be speci- fied. The login name of the remote user. This field is optional. If this field is not specified, any user on the specified remote host is exempt from providing a password, and is assumed to have the same username on both the local and remote hosts. Optionally, an NIS netgroup name can be specified for the host name, user name, or both. Entries in the .rhosts file are either positive or negative. Positive entries allow access; negative entries deny access. The following entries are positive: hostname username +@netgroup In addition, the plus sign (+) can be used in place of the hostname or username. In place of the hostname, it means any remote host. In place of the username, it means any user. The following entries are negative: -hostname -username -@netgroup EXAMPLES
The following sample entries in the /u/chen/.rhosts file on host zeus allow users moshe and pierre at remote host venus and user robert at the hosts specified in the NIS netgroup chicago to log in to user chen's home directory on host zeus: venus moshe venus pierre +@chicago robert FILES
Specifies remote users who can use a local user account. RELATED INFORMATION
Commands: rcp(1), rlogin(1), rsh(1). Functions: ruserok(3). Files: hosts.equiv(4), netgroup(4). Functions: rcmd(3). delim off rhosts(4)