said by severely depressed:

---

Since you bring up the sshd_config script, I do have a question.

Can you prohibit the login of other users besides root this way? If so, how?

I ask because my leetle old mother compete with foo-foo dog (pomeranian) insists on simple login passwords. She claims to be feeble minded (-heh-). So I'd like to have remote access for me via 'ssh' and prohibit remote login of all other users on her machine.

TIA

---

said by fritzmp :

---

You can

edit and add to /etc/pam.d/login

easier and better

edit /etc/security/access.config

This is good to use with the previous post above.

---

If you don't use PAM or are running a distro that doesn't have /etc/security/access.conf (Slack has neither), you can use the sshd_config to set this:
AllowUsers
This keyword can be followed by a list of user name patterns,
separated by spaces. If specified, login is allowed only for
users names that match one of the patterns. `*' and `'? can be
used as wildcards in the patterns. Only user names are valid; a
numerical user ID is not recognized. By default, login is
allowed for all users. If the pattern takes the form USER@HOST
then USER and HOST are separately checked, restricting logins to
particular users from particular hosts.

said by cwnorris :

---

said by fritzmp :

---

You can

edit and add to /etc/pam.d/login

easier and better

edit /etc/security/access.config

This is good to use with the previous post above.

---

If you don't use PAM or are running a distro that doesn't have /etc/security/access.conf (Slack has neither), you can use the sshd_config to set this:
AllowUsers
This keyword can be followed by a list of user name patterns,
separated by spaces. If specified, login is allowed only for
users names that match one of the patterns. `*' and `'? can be
used as wildcards in the patterns. Only user names are valid; a
numerical user ID is not recognized. By default, login is
allowed for all users. If the pattern takes the form USER@HOST
then USER and HOST are separately checked, restricting logins to
particular users from particular hosts.

---

I was playing around and find that for ssh sessions cwnorris method is the easiest and safests for no0bs.

NEXT BIG TIP

When working on tightening up authentication and security have Two Terminals Open because if you lock your self out of your box you will then learn about single user login to recover.:)

PAM and Login will lock you out at the box, so take heed.
--
NTFS Killed My Parents. Get Freed A small band of FreeBSD users are working together in the shadows, observing, honing their skills, building their numbers, and plotting their future.

said by fritzmp :

---

NEXT BIG TIP

When working on tightening up authentication and security have Two Terminals Open because if you lock your self out of your box you will then learn about single user login to recover.:)

PAM and Login will lock you out at the box, so take heed.

---

quote:

---

Having Problems with the kernel or hardware? Use this command:

tail /var/log/messages

---

said by rocketspeed :

---

Just don't forget to restart the sshd .

> service sshd restart

---

said by sporkme :

---

ps -auxwww | grep "daemonname" | awk '{print $2}' | xargs kill -9

---

Turbo mode logins using ssh keys.

1) On local-machine type this command...

   $ ssh-keygen -t rsa

TIP: When it asks for a passphrase just hit enter.
     ie: Do not give it a passphrase.

2) This will create a file ~/.ssh/id_rsa.pub

3) This will be used for your *PUBLIC* key.

4) On local-machine issue this command...

   $ scp ~/.ssh/id_rsa.pub user@remote-machine:.ssh/authorized_keys2

  Assuming you have the same username on both local-machine
  and remote-machine you do not have to use the
  user@remote-machine. Just remote-machine will do in the
  'scp' line above in this case. For the purpose of being
  "proper" this is the syntax I used above...
  user@remote-machine

IMPORTANT NOTE: NEVER EVER copy the file ~/.ssh/id_rsa to another machine.
ONLY ~/.ssh/id_rsa.pub ok?
You do not need to do this for any reason.
Don't do it.
You have been warned.

5) On local-machine issue this command...

   $ ssh remote-machine

6) Badabing. Sweet.

You want more automation ?
Check this out...

7) I personally have a ~/bin directory that is in my $PATH.
   You will need a directory in your home that is in your
   $PATH. We will assume from this point that you have such
   directory already in your $PATH.

8) Create a file called ssh-to on local-machine and put it in your ~/bin directory.

   In this file put this sweet little script ...

#-------------snip------------
#!/bin/sh

ssh `basename $0` $*
#-------------snip------------

9) Save the file to ~/bin/ssh-to on local-machine and make it executable.
   ie: $ chmod 700 ~/bin/ssh-to

10) On local-machine type this command...

    $ cd ~/bin

11) On local-machine type this command...

    $ ln -s ssh-to remote-machine

    Tip: If you have an alias in your /etc/hosts file for
    the remote-machine use those it will make it even nicer.

12) On local-machine type this command...

    $ remote-machine

     Sweet. You should have logged right in to the remote-machine.

13) Now that you have this setup try this cool stuff....
    On local-machine of course.

    $ remote-machine uptime

    $ remote-machine ls

    $ remote-machine any-command-you-want-to-execute-on-remote-machine

14) Now just repeat these steps for each remote-machine
    that you choose.

15) Another nice side affect of this is that "scp"
    and "sftp" will not require a passwd either :)

I hope this helps someone.

»linuxtux.org/howtos/ssh-stuff.txt

code:

---

# 1 the first field denotes the minute,
# 2 the second the hour,
# 3 the third the day of month,
# 4 the fourth the month (by number or short name)
# 5 the fifth the day of the week (by number or short name)

---

code:

---

 # partition  mountpoint type  opts dump/pass

---

said by Skipdawg :

---

An Introduction to the Linux Command Line Interface, The Core 15 Commands
»www.wtlug.org/story.php/view/54/

---

said by elluzion :

---

There's a way to do it with GRUB also, but i don't know how.

---

said by elluzion :

---

This may be old news to many...
You can get access to a Linux computer without logging in by typing "linux single" at the LILO "boot:" prompt. I think you can type "linux emergency" as well and get the same effect.

---

quote:

---

It boots the computer to runlevel 1

---

#!/bin/bash
echo =====
echo The following accounts have root access:
echo =====
cut /etc/passwd -f1,3 -d: |grep :0 | cut -f1 -d: