Quote:
Originally Posted by till
ISPConfig uses already a good protection which includes also a brute force attack protection and blocking for the ispconfig login. So if you use the same username and password for the htaccess protection then you use for the ispconfig login you removed the brute force attack prevention of ispconfig.
|
I use different passwords on each, what caused me to do this were 3 things. It started from the phpmyadmin being exposed and I wanted to protect that first (now locked every user out of it

). 2 is, that the actual server admin login area is exposed, it is a common area for users and admins and I consider this a little ..(!) (or I am completely paranoid), maybe the server admin should use a secret address, and 3, the fact that I cannot change the default "admin" username (which is the default and known already to possible attacks) or create/delete server admins, maybe in order to change their default ID. I can create clients but not admins, is that right ?
Quote:
Originally Posted by till
The symlink is a alternative approach to access ispconfig trough the default vhost of the server. Removing the symlink was only relevant for you as you added a additional password protection into the ispconfig vhost and the password protection could have been bypassed when the symlink is there. Removing the symlink is not required for any default install, it was just required for your setup.
|
Thanks for this explanation, I currently don't know "when" or from "where" the symlink could be used to access the control panel and bypass the authentication I added. Some info on this would be greatly appreciated.
Recent comments
20 hours 51 min ago
1 day 1 hour ago
1 day 6 hours ago
1 day 8 hours ago
1 day 22 hours ago
1 day 22 hours ago
2 days 3 hours ago
2 days 10 hours ago
2 days 10 hours ago
2 days 12 hours ago