Sponsored Content
Operating Systems Solaris Not able to disable finger & telnet command in Solaris 8 Post 303040572 by amity on Friday 1st of November 2019 01:45:28 AM
Old 11-01-2019
Not able to disable finger & telnet command in Solaris 8

Hi
I need to disable finger & telnet command in solaris 8

I have put the # infront of finger and telnet line in /etc/inetd.conf file. Further I have run the below command

Code:
kill -1 <process id of inetd >

But when I am running finger command it is till giving information for remote machine

--- Post updated at 10:56 AM ---

Just to add that it is showing details of user through which I am login to this server along with details of server thorugh which I login to this server.

For example:

If I currently login to host1 (Solaris 10) then login to host2 ( Solaris 8 where I am facing issue) through host1 then in finger command on host2, I am getting only local user detail through which I login to host2 along with host details

--- Post updated at 11:15 AM ---

As per my understanding we don't even need to run above kill command as finger command will only run when it is invoked through the command line as it happened when command got invoked due to that inetd command will reread the /etc/inetd.conf file and run the finger daemon and if I put the # in front of finger line in /etc/inetd.conf then it should not be invoked. But it is getting invoked. Further same thing is happring in Solaris 9 as well.

Please correct me if I am wrong

I need to disable finger command due to security reason.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

finger command

Hello all, Here is what I am trying to do. If a user exist, then send an echo "EXIST" or else "DOES NOT EXIST". (under HP-UX) Kind of: #!/usr/bin/sh USER=mylogin finger $USER if $? = 0 then echo "EXIST"" else echo "DOES NOT EXIST" fi (10 Replies)
Discussion started by: qfwfq
10 Replies

2. Solaris

disable telnet on Solaris

All - would you please some one help me to disable telnet on Solaris? /etc/inetd.conf Thanks :confused: (11 Replies)
Discussion started by: March_2007
11 Replies

3. Solaris

Disable telnet timeout

Hi, Can someone help me how I can disable telnet timeout? I'm connecting remotely to some machines and after some time my telnet connection was closed. How can I disable this so that I'm always connected to those machines? Thanks! (2 Replies)
Discussion started by: ayhanne
2 Replies

4. Solaris

disable telnet on the startup

Hi All, I want to disable telnet on the startup of solaris 8-10 but still wants for a standby purposes. In case I need to troubleshoot ssh, I can connect thru telnet. Most solution on the internet is to permanently removed it. Best Regards, itik (5 Replies)
Discussion started by: itik
5 Replies

5. Solaris

SSH enable, Telnet disable ...

Hi... How do I enable SSH and disable telnet.. Also - is there anything special I need to do to ensure that a new user can use ssh and su but not telnet? Adel (15 Replies)
Discussion started by: ArabOracle.com
15 Replies

6. Solaris

Disable telnet for a particular user

On Solaris 8 is there anyway to disable telnet for a particular user and not for entire system altogether? I would like the user to retain a shell and so creating a noshell like ftp account is not an option. (14 Replies)
Discussion started by: boshyd
14 Replies

7. AIX

Allow telnet in AIX from specific IP adds, but disable for everyone else

I need to change the security on our AIX servers and disable telnet from all but certain IP addresses. I have hashed the telnet line in /etc/inetd.conf and added filter rules for those IP adds to allow access on port 23, but this didn't work. Does anyone have any ideas? Thanks. (2 Replies)
Discussion started by: Alps
2 Replies

8. Solaris

Having problems with finger on Solaris 10

I have a bunch of Solaris systems and for the 8/9 systems, I can type "finger -s 2" to get a list of all users (whether they are logged in or not) and the last time they logged in. I have some new 10 systems and this command does not work. Does anybody know whether this was changed in Solaris 10?... (6 Replies)
Discussion started by: Muller
6 Replies

9. Solaris

Solaris Finger Service Problem

I have been instructed to disable the finger service for our Solaris 10 box. However when I input #svcadm disable finger I receive: "svcadm: Pattern 'finger' does not match any instances. I have also tried to edit the inetd config file and comment out the finger part but Solaris has basically... (14 Replies)
Discussion started by: mvhoward
14 Replies

10. Shell Programming and Scripting

What is the use of "finger" command & how to use it to kill the online processes ?

Hi there, I am eager to know what exactly is the use of "finger" command & how to use it to kill the online processes ? :b: (1 Reply)
Discussion started by: abhijitpaul0212
1 Replies
FINGERD(8)						    BSD System Manager's Manual 						FINGERD(8)

NAME
fingerd -- remote user information server SYNOPSIS
fingerd [-8ghlmpSsu] [-P filename] DESCRIPTION
fingerd is a simple protocol based on RFC 1288 that provides an interface to the Name and Finger programs at several network sites. The pro- gram is supposed to return a friendly, human-oriented status report on either the system at the moment or a particular person in depth. There is no required format and the protocol consists mostly of specifying a single ``command line''. fingerd is started by inetd(8), which listens for TCP requests at port 79. Once handed a connection, fingerd reads a single command line terminated by a <CRLF> which it then passes to finger(1). fingerd closes its connections as soon as the output is finished. If the line is null (i.e., just a <CRLF> is sent) then finger(1) returns a ``default'' report that lists all people logged into the system at that moment. If a user name is specified (e.g., eric<CRLF>) then the response lists more extended information for only that particular user, whether logged in or not. Allowable ``names'' in the command line include both ``login names'' and ``user names''. If a name is ambiguous, all pos- sible derivations are returned. The following options may be passed to fingerd as server program arguments in /etc/inetd.conf: -8 Enable 8-bit output. -g Do not show any gecos information besides the users' real names. -h Display the name of the remote host in short mode, instead of the office location and office phone. -l Enable logging. The name of the host originating the query, and the actual request is reported via syslog(3) at LOG_NOTICE priority. A request of the form '/W' or '/w' will return long output. Empty requests will return all currently logged in users. All other requests look for specific users. See RFC 1288 for details. -m Prevent matching of user names. User is usually a login name; however, matching will also be done on the users' real names, unless the -m option is supplied. -P filename Use an alternate program as the local information provider. The default local program executed by fingerd is finger(1). By specifying a customized local server, this option allows a system manager to have more control over what information is pro- vided to remote sites. -p Prevents finger(1) from displaying the contents of the ``.plan'' and ``.project'' files. -S Prints user information in short mode, one line per user. This overrides the ``Whois switch'' that may be passed in from the remote client. -s Disable forwarding of queries to other remote hosts. -u Queries without a user name are rejected. SEE ALSO
finger(1), inetd(8) HISTORY
The fingerd command appeared in 4.3BSD. BUGS
Connecting directly to the server from a TIP or an equally narrow-minded TELNET-protocol user program can result in meaningless attempts at option negotiation being sent to the server, which will foul up the command line interpretation. fingerd should be taught to filter out IAC's and perhaps even respond negatively (IAC WON'T) to all option commands received. BSD
September 12, 2002 BSD
All times are GMT -4. The time now is 11:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy