|
|
Security |
| There are lots of people out there ("crackers") who would
be delighted to break into your Linux box. As soon as you
are connected to the internet they will start trying. So it
is important to secure your machine against intrusions. | |
| Major Topics:
General Questions: | |
| [New Answer in "Security"] | |
| 2000-Mar-30 2:24pm | |
|
|
ssh (secure shell) |
| Use it!
| |
| Major Topics:
General Questions: | |
| [New Answer in "ssh (secure shell)"] | |
| 2003-Apr-07 7:10pm | |
|
|
How do I set up passwordless RSA/DSA authentication with OpenSSH? |
| A good reference is http://www-106.ibm.com/developerworks/linux/library/l-keyc.html and http://www-106.ibm.com/developerworks/library/l-keyc2/.
Here are the basic steps for DSA, which is relevant for ssh2 (which is what you should use!): 1. Set up a pair of keys (public and private) on one of your machines. ssh-keygen -t dsaYou will be prompted for a passphrase. This is like a password. Use a good one! The default names for the public and private keys (~/.ssh/id_dsa and ~/.ssh/id_dsa.pub) should be fine. 2. Copy the public key over to the any remote machines you want to access into the file ~/.ssh/authorized_keys2 (the 2 is for ssh2). (You can just append it to the end of the file.) 3. Protect the private key! IMPORTANT: You need to have the correct file protections on the ~/.ssh directory AND on the files. The ~/.ssh directory, the authorized_keys2 file, and the id_dsa file must be only accessible to you. These commands will do this: chmod 700 ~/.ssh chmod 600 ~/.ssh/id_dsa chmod 600 ~/.ssh/authorized_keys2
4. At this point, we still need to use the passphrase. If you check the second reference at the top, however, you'll find instructions for how to avoid typing the passphrase all the time. | |
| [Append to This Answer] | |
| 2003-Apr-08 8:19am | |
|
|
How do I know if my password (/etc/passwd) file has been compromised? |
| Look for these things in your /etc/passwd file:
* the last field in a passwd entry is the shell. Nothing should have a shell except for root and any user accounts that you have set up (and possibly a database like postgres). These things have something else in that entry: sync (/bin/sync), shutdown (/sbin/shutdown), xfs (/bin/false). * check the UID, which is the number in the third field (delimited by :'s). Only root should be UID 0.
* look for user names you don't recognize. | |
| [Append to This Answer] | |
| 2000-Mar-23 9:19am | |
|
|
How do I find all of the SUID and SGID files? |
You can list all of the SUID and SGID files on your system with the command
(executed as root; don't type the "#"):# find / \( -perm -004000 -o -perm -002000 \) -type f -print[If you don't run this as root, you'll get a lot of "Permission denied" commands 2000-Mar-23 9:27am furnstahl.1@osu.edu | |
| [Append to This Answer] | |
| 2000-Mar-23 9:27am | |
|
|
How can I tell if my machine has been cracked? |
| * Check the /etc/passwd file
see (http://ntg4004.mps.ohio-state.edu/cgi-bin/fom?file=89) for details.
* Look for /.bash_history linked to /dev/null
| |
| [Append to This Answer] | |
| 2000-Mar-23 9:31am | |
|
|
How can I automatically keep track of my system log files? |
| One possibility is the program Logcheck
http://www.psionic.com/abacus/logcheck/.
I'm trying this out: stay tuned!
Some steps in the installation: 1. Change the protection of the log files so that they are
only readable by root.
2000-Mar-30 2:52pm furnstahl.1@osu.edu | |
| [Append to This Answer] | |
| 2000-Mar-30 2:52pm |
| Previous: |
|
| Next: |
|
| ||||||||||