LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Security
User Name
Password
Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.

Notices


Reply
  Search this Thread
Old 01-15-2007, 11:20 PM   #1
mintojoseph
LQ Newbie
 
Registered: Nov 2006
Location: Kerala
Distribution: Fedora, Debian, RHEL
Posts: 29
Blog Entries: 1

Rep: Reputation: 15
ssh compromised


Hi all,

This is my first post.


I couldn't access my server today morning via ssh and I had to restart it.

I saw following entries in /var/log/secure.

Jan 16 04:13:25 xxxxx sshd[31964]: refused connect from ::ffff:85.18.94.112 (::ffff:85.18.94.112)
Jan 16 04:26:15 xxxxx sshd[32520]: refused connect from ::ffff:81.209.167.239 (::ffff:81.209.167.239)
Jan 16 04:47:04 xxxxx sshd[3621]: Received signal 15; terminating.
Jan 16 05:20:41 xxxxx sshd[3615]: Server listening on :: port 22.


Somebody send a SIGTERM signal to sshd? How could somebody do that?


My current version of ssh is OpenSSH_3.6.1p2, SSH protocols 1.5/2.0..
Will upgrading the ssh will stop the issue from repeating?
 
Old 01-16-2007, 12:27 AM   #2
zhangmaike
Member
 
Registered: Oct 2004
Distribution: Slackware
Posts: 376

Rep: Reputation: 31
Is it possible that it was the script which restarts sshd that sent the SIGTERM?
 
Old 01-17-2007, 09:04 PM   #3
mintojoseph
LQ Newbie
 
Registered: Nov 2006
Location: Kerala
Distribution: Fedora, Debian, RHEL
Posts: 29

Original Poster
Blog Entries: 1

Rep: Reputation: 15
But no valid user was logged in that time..

Quote:
Originally Posted by zhangmaike
Is it possible that it was the script which restarts sshd that sent the SIGTERM?
 
Old 01-17-2007, 09:42 PM   #4
anomie
Senior Member
 
Registered: Nov 2004
Location: Texas
Distribution: RHEL, Scientific Linux, Debian, Fedora
Posts: 3,935
Blog Entries: 5

Rep: Reputation: Disabled
The log shows a couple users being blocked by (what appears to be) tcp_wrappers.

sshd received its kill instructions, and then it's listening on port 22 awhile later. I'm presuming the kill was not from you rebooting the box...

Upgrade to the latest OpenSSH version, sure, but more importantly: turn off SSH protocol 1.
 
Old 01-17-2007, 11:09 PM   #5
Matir
LQ Guru
 
Registered: Nov 2004
Location: San Jose, CA
Distribution: Debian, Arch
Posts: 8,507

Rep: Reputation: 128Reputation: 128
When you rebooted, was it a "hard" reboot, or could ACPI have initiated a proper shutdown? (i.e., were the shutdown scripts run?)
 
Old 01-18-2007, 09:07 PM   #6
mintojoseph
LQ Newbie
 
Registered: Nov 2006
Location: Kerala
Distribution: Fedora, Debian, RHEL
Posts: 29

Original Poster
Blog Entries: 1

Rep: Reputation: 15
Thank you for the clarification guys...
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Compromised by SSH bruteforce MBH Linux - Security 3 09-16-2005 10:10 PM
SSH brute force.... compromised? heri0n Linux - Security 15 11-21-2004 05:51 PM
compromised by SSH login phennon Linux - Security 2 09-19-2004 08:03 PM
Ssh Compromised!!???help!!! Savedadogs Linux - Security 12 02-10-2004 12:48 AM
Ssh Compromised! Savedadogs Linux - General 1 04-28-2002 03:29 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Security

All times are GMT -5. The time now is 11:48 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration