Re: Properties files to read the tokes and passwords outside of the perl scripts.

These days it is unusual to store passwords. Most often cryptographic hashes of passwords are stored and compared against hashes calculated for candidate passwords. This may not apply to your situation, but you haven't told us what that is. Maybe if you tell us more about the problem you are trying to solve we can give a better answer?

Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond

Comment on Re: Properties files to read the tokes and passwords outside of the perl scripts.

Replies are listed 'Best First'.
Re^2: Properties files to read the tokes and passwords outside of the perl scripts. by Bod (Parson) on Dec 14, 2020 at 21:04 UTC
These days it is unusual to store passwords. I read the question differently to you GrandFather - I took it that the OP wants to store passwords that they want to use rather than check. Something like a password that the script needs to connect to a database or similar. Does this difference of understanding come from a badly asked question?	[reply]
Re^3: Properties files to read the tokes and passwords outside of the perl scripts. by GrandFather (Saint) on Dec 14, 2020 at 23:13 UTC
There are two parts to the answer: The question doesn't make it clear how the passwords might be used If the intended use is to feed the passwords into something else my answer still holds. It is best practice to use a public/private key pair instead of bare passwords. I guess that falls under "This may not apply to your situation, but ..." Yes, it is a badly asked question. Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond	[reply]