RE: [suse-security] Securityaspects of mysql
Hi Ruprecht, At the www.e-secure-db.us site you can check out all current and historical vulnerabilties of MySQl. Location: Folder - MySQl Vulnerabilities: http://www.e-secure-db.us/dscgi/ds.py/View/Collection-853 It is contained in a parent folder: Databases and SQL related vulnerabilities: http://www.e-secure-db.us/dscgi/ds.py/View/Collection-55 where you can find all major (and many other) databases and what vulnerabilities on each one has been recorded. Information on SQl injection etc vulns and methods is located in: http://www.e-secure-db.us/dscgi/ds.py/View/Collection-1451 Have fun with the site; you will find thousands of other IT Security subjects and let me know how you go. Best regards, Arjen de Landgraaf New Zealand www.e-secure-it.us -----Original Message----- From: Ruprecht Helms [mailto:rhelms@mayn.de] Sent: Sunday, 29 September 2002 8:07 p.m. To: suse-security@suse.com Subject: [suse-security] Securityaspects of mysql Hi, I want to know how secure is mysql. At the moment I'm contaced by a firm for planing a database with connections to a department in spain in a few years. So I've some points that are interessting to me. How secure is the securitymanager of mysql? How secure are the content in the database saved internal? How secure is the communication between mysqlserver and mysql-client? What is nessessary for security for using the database in the internet. The internetpart is used by customers and the external stuff of the firm. How can I secure the communication between the firms headquarter and the department in spain. Regards, Ruprecht ------------------------------------------------------------ Ruprecht Helms IT-Service und Softwareentwicklung Tel/Fax: +49[0]7621 16 99 16 email: info@rheyn.de Homepage: http://www.rheyn.de ------------------------------------------------------------- -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
participants (1)
-
Arjen De Landgraaf