Restricting Telnet to IPs Post: 25463

10 More Discussions You Might Find Interesting

1. Cybersecurity

restricting access...

restricted access... Hi I need to restrict users shell access to only $HOME under /home for each user. I don't want them getting out of their own directories. From what I understand chroot is something I could use, but I want to avoid this since it involves creating symbolic links to a number...

2. UNIX for Dummies Questions & Answers

Restricting access

I need to create a user that only has access to 1 directory (e.g. /vol/mita/test). The user needs to be able to rsh into that directory to run a script. The user should not be able to navigate to any other directories above /vol/mita/test. Any help would be appreciated!

3. UNIX for Dummies Questions & Answers

Restricting Telnet to IPs

Dear Experts, Is it possible to restrict telnet to specific ips in Digital Unix Thanks

4. Solaris

restricting access

Hi All, I'm on Solaris 8, I need to provide Read-only access to a user to 2 directories only. Using rsh (restricted shell) as the user's login shell, I can restrict the user's access to a certain directory only, but how can I set in such a way that the user can access only the 2 directories...

5. Shell Programming and Scripting

Webpage to Telnet via Perl and Expect: Telnet problem?

Somewhat long story: I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage. This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only...

6. Linux

Restricting IPs on Linux?

I have a need to allow only certain IP addresses to access a machine running Linux. I don't know how would i do it, not an expert at CMD? Thanks in advance for your help.

7. UNIX for Dummies Questions & Answers

Automatically login in the telnet from present telnet

Hi, I was writing one script which includes to switch to the another telnet automatically from the present telnet server. I was using rlogin but firstly it takes the same user name of the present telnet and secondly it is prompting for the password. But i want to switch to the another telnet...

8. Shell Programming and Scripting

restricting users

how can i make my users to not use particular commands in the network like:wall....... pl z help me regarding this

9. UNIX for Dummies Questions & Answers

Difference Between Krb5-telnet And Ekrb5-telnet

Hi, I want to know the difference between these two services. Both are under xinetd. Both are used for enabling and disabling Telnet service. So, can somebody please explain me the difference between the two ? Thanks in advance :)

10. Solaris

Restricting use of su - (Solaris 11)

OK. So I can prevent remote systems from logging in as root by uncommenting the CONSOLE entry /etc/default/login. BUT, is there a way to stop su - (when already logged in as own user)? The way we do it is to set up sudoers so users who need access can do sudo su -

LEARN ABOUT OPENSOLARIS

systemd-halt.service

SYSTEMD-HALT.SERVICE(8) 				       systemd-halt.service					   SYSTEMD-HALT.SERVICE(8)

NAME

       systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic

SYNOPSIS

       systemd-halt.service

       systemd-poweroff.service

       systemd-reboot.service

       systemd-kexec.service

       /lib/systemd/systemd-shutdown

       /lib/systemd/system-shutdown/

DESCRIPTION

       systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly,
       systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target
       to execute the respective actions.

       When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the
       actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices,
       detach all remaining storage devices and kill all remaining processes.

       It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1
       could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted
       read-only.

       Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in
       /lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen
       action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables
       finished.

       Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command
       such as "systemctl halt" or suchlike.

SEE ALSO

       systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8)

systemd 237														   SYSTEMD-HALT.SERVICE(8)

10 More Discussions You Might Find Interesting

1. Cybersecurity

restricting access...

Discussion started by: alwayslearningunix

2. UNIX for Dummies Questions & Answers

Restricting access

Discussion started by: ngagne

3. UNIX for Dummies Questions & Answers

Restricting Telnet to IPs

Discussion started by: geraldwilson

4. Solaris

restricting access

Discussion started by: max_min