RSS Feeds29 results. Narrow Selection By Tag SSH AND
Other:
- Shell - Kernel - Mail - Networking
- Administration - Blog - DirkHart - FAQ - Forum - Kermit
- Unix - Unix Words
- Shell - Kernel - Mail - Networking
- Administration - Blog - DirkHart - FAQ - Forum - Kermit
- Unix - Unix Words
IP spoofing and automatic blocking
So.. for this to make sense our hacker has to first come in with a real ip address and fail to login the magic number of times. He then notices that he's been blocked, and revengefully decides to spoof ip's
| Title | Date | Comments | |||
|---|---|---|---|---|---|
| How can I restrict who can login with ssh? | 1997-2003 | 2010/06/27 anonymous | |||
| - There's no reason to allow every user access by ssh. You can restrict ssh logins to a specific set of users by an entry in the config file. - | |||||
| SSH passphrases and keys | 2005 02 | ||||
| - You then need to put the public key (.ssh/id_dsa.pub by default) into the authorized_keys2 file on the server. Once that's done, if you attempt an ssh to the server, you'll be asked for your passphrase rather than the password of the user on the server. Here's the most important thing to understand at this point: The password at the server doesn't matter anymore. You could log into the server and change the password, and ssh is still going to let you in because of the public key and the passphrase you've provided. You could even edit (as root, of course) /etc/shadow on the server and put a * in the password field, which would mean that no password could EVER be used to login as that user, but you could still login as that user using ssh and your key files/passphrase. - | |||||
| SSH Login Attacks | 2005 01 | ||||
| - Failed password for illegal user [username]. in your logs may indicate brute force password guessing attempts. - | |||||
| SSH | 2001 05 | ||||
| - Standard Unix tools like telnet and ftp are not encrypted- everything you type, including your precious passwords, travels in packets that can at least potentially be seen by every machine they pass by or through. - | |||||
| Security Paranoia - restricting ssh access | 2004 10 | ||||
| - I had email from someone today whose system was hacked, apparently by a dictionary attack over ssh. There is no reason to let that happen to you. - | |||||
| ssh forwarding | 2006 06 | ||||
| - Ssh forwarding can be confusing. Let's say we have a machine that our firewall will send traffic to, but we actually want to ssh to another internal machine. - | |||||
| SSH_CLIENT, SSH_CONNECTION (OpenSSH Variables) | 2005 05 | ||||
| - 2005/05/31 SSH_CLIENT, SSH_CONNECTION (OpenSSH Variables) - | |||||
| DSL and Cable Modem Security with SSH | 2000 02 | ||||
| - An old article about securing ancient SCO Unix when the Internet access is through DSL. - | |||||
| Where can I get ssh? | 1997-2003 | ||||
| - This is an old article about obtaining ssh for older SCO Unix and is only left here for historical purposes. - | |||||
| IP spoofing and automatic blocking | 2005 03 | ||||
| - For this to make sense our hacker has to first come in with a real ip address and fail to login the magic number of times. - | |||||
| Centos ssh failure | 2009 06 | ||||
| - I have a customer who uses a fairly new Centos server to function as an ssh gateway to his ancient SCO box. On Friday he told me that no one could ssh in. - | |||||
| Questions on ssh | 2008 10 | ||||
| - How to reinstall ssh on SCO 5.0.7 using Custom and the original installation CD. - | |||||
 | |||||
| SSH Risk from known_hosts? | 2005 05 | ||||
| - This whole concept starts with a compromised machine - | |||||
| More ssh ideas | 2005 02 | ||||
| - A friend recently got 'rooted'. He was using ssh (not ssh2). He was getting pages on his phone and processes were dying and such, so he installed "chkrootkit" which is a program that checks your system to see if there is any of a number of root kits installed. He had SuckIt installed on his machine and now has a server to rebuild. - | |||||
| scponly | 2004 06 | ||||
| - A restricted shell for specific use with scp and sftp. It is configurable, o you can add or subtract apps it can use, but the base purpose is to provide security for file transfers. Often used in conjunction with chroot for even greater lockdown. - | |||||
| Securing POP mail access in Mac OS X | 2003 03 | ||||
| - Securing POP mail access in MacOSX by tunneling through ssh is possible but doeshave some disadvantages. - | |||||
| SSH- The Secure Shell | 2001 05 | ||||
| - Everything you'd ever need to know about SSH. Well written, very complete- I liked this book! Some of the Amazon reviewers weren't quite so happy with it (one found the lack of NT coverage disappointing), but I enjoyed it start to end. I particularly liked that important concepts were always well explained and not just glossed over. - | |||||
| I ssh to a Linux box and am immediately disconnected | 1997-2003 | ||||
| - ssh to Linux, ssh disconnects from bad TERM setting. - | |||||
| How can I tell if a user logged in locally, used rlogin, telnet or ssh? | 1997-2003 | ||||
| - You can use the concept here to back trace any process. This script will find the first ancestor process after init. This would be sshd or telnet or just a getty, etc. - | |||||
| linux ssh -->Re sshd/Linux problems | 1997-2004 | ||||
| - Packet too long. ssh1 and ssh2 protocol issues. Easier to change to OpenSSH.. - | |||||
| sshd restricted users -->Re SSHD restricted users. | 1997-2004 | ||||
| - Can somebody say me how to allow only some defined users aailable to login on a server? - | |||||
| openssh oss646b, you don't exist, go away | 1997-2004 | ||||
| - openssh oss646b, you don't exist, go away - | |||||
| SCO_OSR5 libsocket.so.2 | 1997-2004 | ||||
| - You need /usr/lib/libsocket.so.2 and /usr/lib/libresolv.so.1. RS506a will have installed them, but if you have OSR 5.0.5, they are also in CSSA-2002-SCO.39 - | |||||
| sshd stty raw cooked -->Re sco-list Re New OpenSSHpackages available | 1997-2004 | ||||
| - On SCO Open Server, when the sshd daemon establishes a connection, the line - | |||||
| root login over ssh -->Re telnet as rootquestion | 1997-2004 | ||||
| - Allowing root logins via ssh isn't anywhere as insecure as allowing them via telnet, but I'd still recommend NOT allowing these. - | |||||
| Preventing ssh login attacks | 1997-2004 | ||||
| - There are a number of simple and not so simple things you can do to eliminate the chance of getting hacked. - | |||||
| sshd -->Re SCO 5.0.5 SSH 2.9p2 login error | 1997-2004 | ||||
| - sshd -->Re: SCO 5.0.5 SSH 2.9p2 login error - | |||||
| Kermit ssh -->Re Announcing C-Kermit 8.0 Beta.03 | 1997-2004 | ||||
| - Kermit changes its mind about ssh - or does it?0 - | |||||
| Explaining SOCKS vs. NAT -->Re Oddball Networking Question | 1997-2004 | ||||
| - iSOCKS is proxying, not masquerading. The difference can be confusing; this post explains it all. - | |||||
 | |||||
