Koozali.org: home of the SME Server

Should I worry?

spook

Should I worry?
« on: January 03, 2007, 09:41:57 AM »
I get this email daily - How serious is it, and how do I do anything about it?

Quote
/etc/cron.daily/01-rkhunter:

Line:
Watch out Root login possible. Possible risk!
-----------------------------------------------------------------

Found warnings:
[04:03:06] Warning: root login possible. Change for your safety the 'PermitRootLogin'

Offline bpivk

  • *
  • 908
  • +0/-0
    • http://www.bezigrad.com
Should I worry?
« Reply #1 on: January 03, 2007, 03:29:31 PM »
Rkhunter gives you this warning because having ssh configured for root login *is* a security hole.

You can close this hole with the /server-manager/ in remote access.
"It should just work" if it doesn't report it. Thanks!

Offline jumba

  • *****
  • 291
  • +0/-0
  • Donations: July 2007 - $ 20.00
    • Smeserver på svenska!
Should I worry?
« Reply #2 on: January 03, 2007, 07:23:32 PM »
Quote from: "bpivk"


You can close this hole with the /server-manager/ in remote access.


Which setting there are we supposed to change in order to close this hole???

Offline bpivk

  • *
  • 908
  • +0/-0
    • http://www.bezigrad.com
Should I worry?
« Reply #3 on: January 03, 2007, 08:07:39 PM »
Set Secure shell access (under Secure Shell Settings) to no access.
"It should just work" if it doesn't report it. Thanks!

spook

Should I worry?
« Reply #4 on: January 03, 2007, 10:25:50 PM »
I need SSH root access. How do I make it stop warning me?

Offline bpivk

  • *
  • 908
  • +0/-0
    • http://www.bezigrad.com
Should I worry?
« Reply #5 on: January 03, 2007, 11:22:25 PM »
Ignore the message or you could just delete the cronjob. I would recomend ignoring the message.
"It should just work" if it doesn't report it. Thanks!

ryanb006

Should I worry?
« Reply #6 on: January 04, 2007, 02:06:45 AM »
Here are instructions (rough translation from French) to disable the rkhunter check for SSH root login (from http://www.smeserver.fr/astuces.php?astuce=mail_rkhunter_root )
----
The safest solution is to disable the option to allow administrative SSH access in the Remote access page of the server-manager. This of course forces you to be able login with another account to manage the server via SSH.

The simplest solution is removing this check from the rkhunter configuration file.  For that, you must edit the /etc/rkhunter.conf file with your preferred editor and modifying the following line:

Code: [Select]
ALLOW_SSH_ROOT_USER=1

As this file is not templated, this modification is enough.
----

Offline cactus

  • *
  • 4,880
  • +3/-0
    • http://www.snetram.nl
Should I worry?
« Reply #7 on: January 04, 2007, 08:46:42 AM »
Quote from: "spook"
I need SSH root access. How do I make it stop warning me?
You can have secure access as any user even at root level while not being logged in as root. This is the preffered method. you can do this when you give the user sudo access and a prompt, you can than use the sudo and the su command to run commands at root level.
I believe dungog has a contrib for easy configuration of user remote access where you can set things like this.
Be careful whose advice you buy, but be patient with those who supply it. Advice is a form of nostalgia, dispensing it is a way of fishing the past from the disposal, wiping it off, painting over the ugly parts and recycling it for more than its worth ~ Baz Luhrmann - Everybody's Free (To Wear Sunscreen)

Offline mcp_dk

  • **
  • 34
  • +0/-0
    • http://lillenet.dk
Should I worry?
« Reply #8 on: January 10, 2007, 08:53:22 PM »
Quote from: "cactus"
Quote from: "spook"
I need SSH root access. How do I make it stop warning me?
You can have secure access as any user even at root level while not being logged in as root. This is the preffered method. you can do this when you give the user sudo access and a prompt, you can than use the sudo and the su command to run commands at root level.
I believe dungog has a contrib for easy configuration of user remote access where you can set things like this.

I get this same errormessage and i would like to close this securityhole thus still allow remote SSH login with another user.
I use putty via Windows XP to my box.

I allready have Dungog's "User remote access" with Shell access and sudo enabled for the user i want to use instead of root.
And i can perform administrative tasks with this user when Remote access setting is "Secure Shell access - Allow public access (entire internet)" and "Allow administrative command line access over secure shell" and "Allow secure shell access using standard passwords" is both set to yes.
However if i disable these remote access settings as advised i can't use root login which is what i wanted. But i can not use the other user either. I then can not user remote SSH at all with any user. Putty just time out

How should i set it up so root can't have access over ssh and close this security hole but still be able to use another account to adminstrate my sme box via SSH?
Who is General Failure and why is he reading my harddrive?

Offline grattman

  • ****
  • 122
  • +0/-0
Should I worry?
« Reply #9 on: January 10, 2007, 09:41:17 PM »
I also got this message and followed "safe" guidelines. However, using su it did not allow me to signal-event post-upgrade or signal-event reboot after doing some tasks that required this to happen.

Any ideas?
...