So, this is going to sound odd, but its true.
As a precaution a few months ago, I disabled log in via root/ssh because several "over seas" people were trying to brute force their way in via root account.
When I configured cphulk, I set the times to be VERY long, for my customers have never had an issue with it. Seems that other than would be hackers, i'm the only one to get caught up by the bloody thing.
And as a good business practice, I changed all admin passwords every 30-60 days, however, I buggered and forgot one of the passwords. As I attempted to log in a few times, it finally locked me, and the account, out. As such, now i am completely unable to flush the hulk db to allow me back in to add my ISP as a trusted source.
So, is there a way around this, or am i stuck waiting the long time period i have it set for? I am hoping for a work around.
Thanks and happy holiday!
J



LinkBack URL
About LinkBacks

Reply With Quote
or a variation of it so the hackers





