Also if someone managed to hack your account then I'd think you have worse things to worry about
Yeah, like how (with your hack for this) to get my access back when they change my password. And it doesn't have to be a hacker. It can be one of your "trusted" co-Admins that you shared things you shouldn't have with.
Yeah, like how (with your hack for this) to get my access back when they change my password. And it doesn't have to be a hacker. It can be one of your "trusted" co-Admins that you shared things you shouldn't have with.
phpMyAdmin, or telnet/SSH> mysql CLI ...
In addition, as Jasper Johannsen [Security Engineer with microsoft] says ...
"The best solution to an employee who is doing things they shouldn't - make them an ex-employee."
True, but how much damage can they do before you find out about it? That's the reason they made the $nodelete variable in the config.php. All it takes is once for things to be unrecoverable. Better safe than sorry.
True, but how much damage can they do before you find out about it? That's the reason they made the $nodelete variable in the config.php. All it takes is once for things to be unrecoverable. Better safe than sorry.
I'm betting that many admins who trust another admin will also give their FTP info. Once you have FTP info, you basically can do anything you want, even remove the admin from $nodelete variable.
I'm betting that many admins who trust another admin will also give their FTP info. Once you have FTP info, you basically can do anything you want, even remove the admin from $nodelete variable.
Then you'd lose that bet. Most Admins won't go that far, for just that reason. But a few of them were surprised to see they couldn't log on after one of their co-Admins turned on them and changed the password in their account. Didn't you read any of the pre-vB3 messages here?