Re: securing system after giving away root password
From: Douglas O'Neal (oneal_at_dbi.udel.edu)
Date: 09/20/05
- Next message: matt_left_coast: "Re: Use iptables to block all non-US ssh traffic"
- Previous message: Douglas O'Neal: "Re: Use iptables to block all non-US ssh traffic"
- In reply to: matt_left_coast: "Re: securing system after giving away root password"
- Next in thread: Unruh: "Re: securing system after giving away root password"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 20 Sep 2005 12:14:08 -0400
matt_left_coast wrote:
> Huge wrote:
><snip>
>>
>>And all they have to do is bring the machine up standalone and your remote
>>logging's worth squat.
>>
>>
>
>
> Since the person had to log in as a user the command to go to standalone is
> LOGGED. Since the person did not have the permission to go standalone, they
> are caught.
>
> You are wrong.
>
Unless they pull the network connection for long enough to do their dirty work,
then blame the network down time on their (or your) ISP.
Or maybe they pull the power plug on your system, then boot standalone. To be
complete, they then short your power supply and blame the downtime on a faulty
PDU.
Or possibly a DOS attack on your server to prevent the logged packets from
getting to your server...
- Next message: matt_left_coast: "Re: Use iptables to block all non-US ssh traffic"
- Previous message: Douglas O'Neal: "Re: Use iptables to block all non-US ssh traffic"
- In reply to: matt_left_coast: "Re: securing system after giving away root password"
- Next in thread: Unruh: "Re: securing system after giving away root password"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
