executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases login attemps are logged to syslog (if available). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Note The

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Note The

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases login attemps are logged to syslog (if available). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Note: The

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Note The

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Type: Default

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Note The

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Type: Default

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Note The

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Type: Default

executed for either of these. To allow editing configuration invoke: /usr/sbin/pma-configure To block editing configuration invoke: /usr/sbin/pma-secure Setup script on openSUSE Some openSUSE releases logged to syslog (if available, see $cfg['AuthLog']). This can allow using a tool such as fail2ban to block brute-force attempts. Note that the log file used by syslog is not the same as the Apache error or section for server definition, however you can put as many as you need in config.inc.php, copy that block or needed parts (you don’t have to define all settings, just those you need to change). Type: Default