Sponsored Content
Operating Systems Solaris Not able to disable finger & telnet command in Solaris 8 Post 303040576 by Neo on Friday 1st of November 2019 02:06:58 AM
Old 11-01-2019
Just disable the daemon processes so they do not start when the system is booted.

Or, better yet, just remove or move the daemon executables so they cannot be executive from any scripts (because the name has been changed).

For example, if telnetd is located in /usr/bin just rename it to disabled_telnetd, kill the existing running process and you are done.

Of course, the most secure is to just remove those executables from the server altogether... End of story. Remove them, kill any running processes... system more secure Smilie

If you think you might need them again someday, move them to a backup server, or external disk or media and be happy.
 

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
pcastctl(8)						    BSD System Manager's Manual 					       pcastctl(8)

NAME
pcastctl -- Podcast Producer daemons control interface SYNOPSIS
pcastctl status target on|off|start|stop|restart OPTIONS
The available options are as follows: status print status of running daemons target affect agent or server daemon start|stop|restart explicitly start/stop/restart daemon. Note that 'restart' will kill all instances of a given daemon, as will 'stop' if none is specified in the pid file. RETURN VALUES
0 Completed succesfully. 1 Action failed 10 Not run as root. 50 Target not recognized: use 'a', or 's'. 51 Action not recognized: use start|stop|restart 52 Executables not found; may need to reinstall Podcast Producer. 53 Process directory not found; may need to reinstall Mac OS X. 54 Timeout waiting for action to complete. 55 Launchd manipulation failure. FILES
/usr/libexec/podcastproducer/pcastagentd Podcast Producer agent daemon /usr/share/podcastproducer/pcastserverd Podcast Producer server daemon /var/run/pcastagentd.pid Podcast Producer agent process ID /var/run/pcastserverd.pid Podcast Producer server process ID /System/Library/LaunchDaemons/com.apple.pcastagentd.plist Launchd agent daemon control file /System/Library/LaunchDaemons/com.apple.pcastserverd.plist Launchd server daemon control file EXAMPLES
status of Podcast Producer agent daemon $ pcastctl agent status edit launchd configuration to launch server on system startup $ pcastctl server on DIAGNOSTICS
Warning: Warning: ## copies of (pcastagentd|pcastserverd) already running Trying to launch another daemon when one or more already running; will usually succeed, but may cause unpredictable behavior. See also RETURN VALUES, above. ERRORS
Error: failed to launch (executable) Tried to start/restart a give daemon, but failed. Error: process 'executable' not currently running Tried to kill a process which did not exist. SEE ALSO
pcast(1) launchd(8) HISTORY
This program was first introduced in Mac OS X 10.5 "Leopard". It was inspired by xgridctl(8). BUGS
pcastctl(8) uses kill -TERM to allow the daemons a chance to die gracefully; there is currently no way to force a kill -KILL. Bug reports can be sent to bugreport.apple.com Feedback can be sent to podcastproducer@apple.com Mac OS September 29, 2004 Mac OS
All times are GMT -4. The time now is 07:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy