12-06-2012
Quote:
Originally Posted by
rbatte1
I am being pushed from AIX onto RHEL 6 and after our first 'chuck it on' install, I have a problem. Where is the old (okay insecure) telnet & ftp server? I know that they are probably regarded as archaic now, but the source servers do not have the SSH tools, so I've got to somehow transfer the data.
Install the 'ftp' and 'telnet' packages for the commandline utilities, I think 'telnetd' for telnet server(unsure), and 'proftpd' for a pretty decent FTP server.
Maybe you have xinetd instead of inetd? Being a service wrapper, it's always been kind of optional -- I've personally never understood the use, some distros have it, some don't. On systems which don't, network daemons would just be system services.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi All,
I need to stop all the services for telnet & FTP as we want our
server to be more secure.
Please give me some steps for jumping to SSH protocol.
How can i disable telnet & ftp service on my server. (1 Reply)
Discussion started by: pradeep_desh
1 Replies
2. Red Hat
hi,
i installed linux as4, i need telnet and ftp with root account. anybody show me how to configure.
TIA,
Bong (3 Replies)
Discussion started by: bong02
3 Replies
3. Red Hat
Hi Users,
Kindly help me with below query of mine.
Using Red Hat Linux Enterprise Edition as the client how many simultaneous
1) Maximum FTP sessions are allowed
2) Maximum Telnet sessions are allowed
3) any special settings need to be enabled for maximum telnet and ftp sessions on... (2 Replies)
Discussion started by: newbie07
2 Replies
4. UNIX for Advanced & Expert Users
Hi Users,
Kindly help me with below query of mine.
Using Red Hat Linux Enterprise Edition as the client how many simultaneous
1) Maximum FTP sessions are allowed
2) Maximum Telnet sessions are allowed
3) any special settings need to be enabled for maximum telnet and ftp sessions on... (2 Replies)
Discussion started by: newbie07
2 Replies
5. Shell Programming and Scripting
Hi all,
I'm using the following script to automated ftp files to 1 ftp servers
host=192.168.0.1
/usr/bin/ftp -vi >> $bkplog 2>&1 <<ftp
open $host
bin
cd ${directory}
put $files
quit
ftp
and the .netrc file contain
machine 192.168.0.1
login abc... (4 Replies)
Discussion started by: varu0612
4 Replies
6. Red Hat
Hello all,
I am planning to deploy a configuration / auditing software package for about 100 new nodes that we are planning to install. I am hearing many good things in regards to cfengine and puppet. Can someone shed some light in regards to these solutions?
Thanks,
jaysunn (1 Reply)
Discussion started by: jaysunn
1 Replies
7. Red Hat
Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured
server:
/etc/hosts.allow:
all : all
all :all@all
setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies
8. Red Hat
RHEL 7.1 client using autofs to mount a NIS map of home directories being exported by a Solaris 10x86 nfs server.
The owner and group are correct on the NFS server, but on the RHEL client, the owner and group end up being nobody nobody. The USERS and GROUPS are NIS maps as well. They are... (2 Replies)
Discussion started by: mrmurdock
2 Replies
9. UNIX for Beginners Questions & Answers
H Forum,
I was thankful in getting help from this post that allowed me to connect to multiple severs at once using here documents to gather data into variables. But I've discovered that the same bash command that works on my RHEL 7 servers do not work on RHEL 6? What's strange about my... (4 Replies)
Discussion started by: greavette
4 Replies
LEARN ABOUT LINUX
tcpdmatch
TCPDMATCH(8) System Manager's Manual TCPDMATCH(8)
NAME
tcpdmatch - tcp wrapper oracle
SYNOPSIS
tcpdmatch [-d] [-i inet_conf] daemon client
tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client
DESCRIPTION
tcpdmatch predicts how the tcp wrapper would handle a specific request for service. Examples are given below.
The program examines the tcpd access control tables (default /etc/hosts.allow and /etc/hosts.deny) and prints its conclusion. For maximal
accuracy, it extracts additional information from your inetd network configuration file.
When tcpdmatch finds a match in the access control tables, it identifies the matched rule. In addition, it displays the optional shell com-
mands or options in a pretty-printed format; this makes it easier for you to spot any discrepancies between what you want and what the pro-
gram understands.
ARGUMENTS
The following two arguments are always required:
daemon A daemon process name. Typically, the last component of a daemon executable pathname.
client A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns.
When a client host name is specified, tcpdmatch gives a prediction for each address listed for that client.
When a client address is specified, tcpdmatch predicts what tcpd would do when client name lookup fails.
Optional information specified with the daemon@server form:
server A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns. The default server name is `unknown'.
Optional information specified with the user@client form:
user A client user identifier. Typically, a login name or a numeric userid. The default user name is `unknown'.
OPTIONS
-d Examine hosts.allow and hosts.deny files in the current directory instead of the default ones.
-i inet_conf
Specify this option when tcpdmatch is unable to find your inetd.conf network configuration file, or when you suspect that the pro-
gram uses the wrong one.
EXAMPLES
To predict how tcpd would handle a telnet request from the local system:
tcpdmatch in.telnetd localhost
The same request, pretending that hostname lookup failed:
tcpdmatch in.telnetd 127.0.0.1
To predict what tcpd would do when the client name does not match the client address:
tcpdmatch in.telnetd paranoid
On some systems, daemon names have no `in.' prefix, or tcpdmatch may need some help to locate the inetd configuration file.
FILES
The default locations of the tcpd access control tables are:
/etc/hosts.allow
/etc/hosts.deny
SEE ALSO
tcpdchk(8), tcpd configuration checker
hosts_access(5), format of the tcpd access control tables.
hosts_options(5), format of the language extensions.
inetd.conf(5), format of the inetd control file.
AUTHORS
Wietse Venema (wietse@wzv.win.tue.nl),
Department of Mathematics and Computing Science,
Eindhoven University of Technology
Den Dolech 2, P.O. Box 513,
5600 MB Eindhoven, The Netherlands
TCPDMATCH(8)