Timeline for Linux firewall techniques: MySql-Account
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 7, 2014 at 21:01 | vote | accept | Dennis Ziolkowski | ||
| Nov 7, 2014 at 19:58 | answer | added | Ashish | timeline score: 0 | |
| Nov 7, 2014 at 19:44 | comment | added | Dennis Ziolkowski | The problem is, that the mysql account is always exact the same and port is always 3306 (mysql-daemons default). | |
| Nov 7, 2014 at 19:40 | comment | added | Ashish | You know who are authentic Users Using some authentic port. Allow those users & ports | |
| Nov 7, 2014 at 19:35 | comment | added | Dennis Ziolkowski | Yes. What came on my mind: Is there a special mysql packet flag that can be analyzed by the firewall and not been sent by mysqli but by libmysql.dll? | |
| Nov 7, 2014 at 19:33 | history | edited | Dennis Ziolkowski | CC BY-SA 3.0 |
added 51 characters in body
|
| Nov 7, 2014 at 19:18 | comment | added | Ashish |
anyways if you have Linux then Use iptables or on any unix/linux platform use hosts.allow & hosts.deny files where you can allow or disallow specific IPs, Ports, Services etc.
|
|
| Nov 7, 2014 at 19:15 | comment | added | Ashish | I would appreciate if you mention OS platform you are running | |
| Nov 7, 2014 at 19:09 | review | First posts | |||
| Nov 7, 2014 at 19:21 | |||||
| Nov 7, 2014 at 19:07 | history | asked | Dennis Ziolkowski | CC BY-SA 3.0 |