Accessing and viewing information in a database without a login/password?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I still am not sure what you mean or want to say. Connecting to a database using some client will always need a username and password. Not all databases are password protected but will still need user name. But I do not understand what you are trying to compare with Google or Bing?
One way is you give the Apache user access rights to database content and hardcode the username/passwd in the program. You could put them in a cfg file and have the prog read them (better imho).
For programs that run independently, you could supply them on the cmd line. There's an awful lot of processing that goes on in the real business world that has nothing to do with a webserver or end users generally: think billing for a start. I've written loads of programs like that.
You can encrypt the cfg files, but that makes it more of a pain if you need to change the values.