Page 21 - Open Soource Technologies 304.indd

Open Source Technologies

Notes Securing My SQL: Securing My SQL begins with the server startup procedure. If you are not
the administrator of the server, you won’t be able to change this, but you can certainly check it
out and report vulnerabilities to your Internet service provider.
1. Explain My SQL Query Analyzer.

2. Explain directory listing of My SQL applications.

1.6 Self Assessment Questions

1. Telnet is a perfectly acceptable method to securely connect to My SQL from a remote host.
(a) True (b) False

2. Which three pieces of information does My SQL check each time a request is made?
(a) Who you are?
(b) Where you are accessing from?

(c) What actions you’re allowed to perform?
(d) All of the above.
3. What command would you use to grant SELECT, INSERT, and UPDATE privileges to
a user named bill on localhost to all tables on the BillDB database? Also, what piece of
information is missing from this statement that is recommended for security purposes?
(a) GRANT SELECT, INSERT, UPDATE
ON BillDB.*
TO bill@localcost

(b) GRANT SELECT, INSERT, UPDATE
ON BillDB.*

TO bill@localhost
(c) GRANT SELECT, INSERT, UPDATE
ON BillDB.*
TO bill@localhost

(d) None of the above.
4. My SQL provides slow transaction speed to serve over 300,000 simultaneous users on
BigFishGames.com
(a) True (b) False
5. What are common problems in My SQL connection?

(a) On Linux/Unix and Mac OS X, incorrect permissions do not allow you to start the
My SQL daemon. If this is the case, be sure you have changed owners and groups
to match those indicated in the installation instructions.
(b) If you see the message Access denied when connecting to My SQL, be sure you are
using the correct username and password.
(c) If you see the message Can’t connect to server, make sure the My SQL daemon is
running.
(d) All of the above.

16 LOVELY PROFESSIONAL UNIVERSITY