> Not wanting to look like one of those *ahem* credit orientated crunchers =)
> just an FYI that the stats haven't updated since the 16th

It seems the automated task for doing this is failing, due to library problems. I'm able to run the task by hand and will do so when I can.


- Eric Myers

ID: 2135  / Rate: or   / Rating: 0

[Reply to this post]

Not wanting to look like one of those *ahem* credit orientated crunchers =) just an FYI that the stats haven't updated since the 16th

ID: 2081  / Rate: or   / Rating: 0

[Reply to this post]

Aye , all's ship shape now. Thanks ! =)

ID: 1957  / Rate: or   / Rating: 0

[Reply to this post]

> Just incase you didn't know , the xml stats haven't been updated since you
> were hacked on the 12th =/
>

Yup, and the Phantom has been User of the Day for much too long. :-)

We lost the crontab that triggered all periodic tasks. It'll be back today.

-- Rusty McGee Johnson

ID: 1954  / Rate: or   / Rating: 0

[Reply to this post]

Just incase you didn't know , the xml stats haven't been updated since you were hacked on the 12th =/

ID: 1952  / Rate: or   / Rating: 0

[Reply to this post]

Seeing where my original post in this thread is, it almost looks like I did it. ;)

I didn't.
-------------------------
Jord.

ID: 1939  / Rate: or   / Rating: 0

[Reply to this post]

It's a shame!

thankyou Captn,

to keep the wind in the projects sails +++


What could make sad, even with a protection behind the hosting (*nix-)server,

the intrusion could happen.

The only way to have security nearly 100% is to unplug the net access, but
this would be bad for all users...

It's a luck, no more disadvantages are been installed or "sensible" datas have been stolen

All the best for further migration and hoping there will be no more unconfortable situations:(

ID: 1937  / Rate: or   / Rating: 0

[Reply to this post]

> I now have quite an impressive collection
> of Linux exploits, if I ever decide to go over to the dark side.


Don't do it!
We have to uphold the honor and good name of the Pirates, and not go down to the level of them pirate wannabe's that attack their foes from behind a computer... heck, I bet most of them haven't even been on board of a ship! Let alone sail to the seven seas in search for treasure and adventure like us! :P
________________________________________________

ID: 1932  / Rate: or   / Rating: 0

[Reply to this post]

The Pirates@Home server was hacked on Sunday morning, June 12th, at 9:41AM EDT.

It appears that the initial intrusion was from an automated scan, followed up by someone getting into the system and installing something to scan other systems. This was noticed almost immediately by network security and the port was blocked.

I spent yesterday morning going through the machine to verify that no user data files were affected (they were not) and finding all the root-kit and scanner software they installed. I now have quite an impressive collection of Linux exploits, if I ever decide to go over to the dark side.

We had been wanting to upgrade the operating system anyway, and since you should always do a fresh install after an intrusion we took the opportunity to upgrade to Fedora Core 3. (I should mention that the initial intrusion was not due to any outdated software on the server, though we don't know how they got from a user account to root.)

Since the machine has been upgraded, various systems need to be tweaked and prodded, but hopefully we will be back to trying out the new starboard app soon.


- Eric Myers

ID: 1925  / Rate: or   / Rating: 0

[Reply to this post]

At least it's back. You had me worried there for a bit, since everything was gone.
I hope you managed to get a track onto whoever did it and will tell him that Pirates@Home isn't what he thought it was? ;)


-------------------------
Jord.

ID: 1930  / Rate: or   / Rating: 0

[Reply to this post]

>
> Since the machine has been upgraded, various systems need to be tweaked and
> prodded,

Including the system clock, which has now been properly set.



- Eric Myers

ID: 1928  / Rate: or   / Rating: 0

[Reply to this post]