Shell Programming and Scripting

I want to store the passwords in a global file, so that all the users will not use them to login but a process should use it. One way is to keep the passwords in a .ini file and execute the file in the start of the script and use that variable.

But with this, one can echo the variable in the script and see the value.

How are you guys storing, let's say production database password, and use that in the script while writing the database connect statements.

Hello karumudi7,

It is NEVER EVER recommended to store passwords either in plain text or in encrypted format. Why don't you try to use some certificate kind of thing(not sure in your app case), perfect example if password-less SSH which requires public key copied at target server and while making ssh it makes sure that user is NOT being asked for password etc.

Again DO NOT save passwords in any form, it is NEVER recommended at all.

Note: after Neo' comment adding this, you could not avoid writing passwords always but still use them safely.

Thanks,
R. Singh

Moderator's Comments:

Neo: Please do not delete "mistakes and wrong" answers that others have replied do. Everyone makes mistaken. Accept it and "move on".

Yes, I understand and I use SSH keys for password-less connections.
But it is more like when you are interacting with other services like database etc.

Ravinder,

Many systems on the network require passwords to be stored in a flat file.

It's not always avoidable, so you can't say "NEVER NEVER DO THIS"... spoken much like someone who has not built a production application which uses clear text passwords.

Theory is not always the same in practice.

Normally, these kind of DB passwords are stored in plaintext in files which are hidden from users, so we must look at who has access to the system, the risk, the criticality of the application and other risk management factors.

This is correct. Many CMS programs like WordPress store the DB passwords in clear text in a flat configuration file.

Thank you Neo for correcting me, I have deleted my answer now, considering it was not adding any value add to post.

Thanks,
R. Singh

Ravinder,

Please do not delete "wrong answers or mistakes" which people have replied to.

Everyone makes mistakes.

However, deleting posts which two people have replied is not really correct and is a "bigger mistake", in my view.

Just accept that you learned something and moved on; but I do recommend caution when you have strong opinions based on theory that do not match practical 'the way things are'... we all make mistakes. That's what makes life fun and interesting,

Plus, others can learn for your mistake, so please see it as a way to help others learn, thanks!

The approach to manage risk in IT should be based on a risk analysis.

For example, a person running their own blog who has not much to lose if their DB password is compromised has a much different risk profile than a bank doing financial transactions.

Security controls come with "costs" and so the controls used should be appropriate to the risk profile of the system.

All WordPress blocks, Wikipedia Wikis and indeed most all CMS apps freely available on the network store DB password as clear text in config files which with various standard unix / linux file system permissions and controls.