ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i have the web server running with user1 from the group users.
and the appl needs to be able to read that file anytime it must connect to the db, so i guess that user1 from the group users mut have read permissions on that file, and the user and passwd on the file stills are clear text...
i need to know if i can encript the passwd on the file...so the people that makes vi, cat or more.... doesnt see the passwd
How would you unencrypt the file? Another password? if so where would you keep that other password?
The only way to make it secure is for the user to provide the password, but if the users who have access to an editor don't have rights to the file then you are on the right track.
The principle is that you encrypt information on both sides (server and client), send over the encrypted information and do a compare at the server side.
The principle is that you encrypt information on both sides (server and client), send over the encrypted information and do a compare at the server side.
That's fine for when the client is logging into the server but the database password is normally different, and Mysql expects the password to be in plain text (as far as I am aware), remember MD5 is a one-way translation. But this idea works well with client to server authentication.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.