I’ve heard several reports in the last few days of an increase in attemps to break in to vulnerable SSH servers, so if you manage one, you may want to heed the warnings on this page and install an IDS (such as SNORT) so you know when it’s happening to you.
Picture of TrinityFor those of you who did not understand the first paragraph, the makers of “Matrix Reloaded” were kind enough to provide you with an example. This is right after Trinity jumps to that building on her motorcycle, and has to break in to the computer system.
Picture of computer screenShe uses a program called NMap to scan a range of addresses for a system that is running a vulnerable SSH server, and then uses a program called “sshnuke” (yes, Trinity was a lowly script kiddie) to exploit a known vulnerability in that particular version of the SSH server to allow her to reset the password so that she can get in.
3 Comments
Since you are talking about ssh, I have a problem. I have made a cronjob and saved it to my directory and I know its written and chmoded correctly but when I type cron -e for cron to come up I type in the command
02*** /root/path/backup.sh
the root and path are the correct path.
Everytime I get bad day of the month and I have tried different variables like
0101**** —
and that still doesnt work.
CAn you clue me in?
Thanks.
I believe you need spaces between the minute / hour / day / month, etc.
So for 2:00 AM every day you would start with
00 02 * * *For 1 minute past every hour of every day you would start with
01 * * * *You need to have either a number or an asterisk (for all) for each of the five schedule indicators, which are (in order):
For more info, here is a link to a pretty good CRON overview:
http://tinyurl.com/xbn2
Perfect, Thank you so much.
The spaces were the trick.