On Sep 27, 8:14 am, Lan Mind <[EMAIL PROTECTED]> wrote: > > The database connection information is in a separate file other than > the PHP file used to access the database. Is this good enough? Could > somebody access and see it? I type it in the URL but it shows nothing > in the browser.
That's the way PHP works. The interpreter only outputs to the browser what it's told to. The point about putting database connection data in a separate file is that you can distribute the main PHP file if you need to, for debugging for example. If you place the connection file outside the served "website" tree on the server, so that the main file can get at it but a browser client can't, then that is secure subject to the next tip... > Can you think of any good tips? Make sure that the FTP and database passwords are strong and anonymous access turned off, so that no-one can get at your code or the database itself. > I'm worried as my database is what makes my site relevant. If somebody > were to copy it a lot of hard work would be lost. I put in many hours > geocaching points not available elsewhere, I don't want them copied. Once they have arrived on a webpage there's nothing to stop anyone making use of them, of course. You can ensure that a copyright notice appears in the page, and it might be possible to add a couple of spurious points, or to slightly misplace some real points, so that copied data is obvious. Mapmakers use that technique to allow them to prove infringing copies of maps. The bottom line is: if you don't to make your data copyable, don't make it public. Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
