|
|
| There's more than one way to do things | |
| PerlMonks |
Re: Why is it bad to hide the source?by idnopheq (Chaplain) |
| on Aug 28, 2001 at 09:57 UTC ( [id://108383]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
Allow me to add one ...
- "But my code contains ( my | a privilliged | root's ) password!" Hmm! The only way to address this issue is to go ahead and post the code w/ the real password and the IP address of the server. HHOS! Storring any kind of uber sensitive data, like root's password, in a script is not only generally bad form, but a *H*U*G*E* security issue as well. If one feels a necessity to do this, don't. There's usually a better way, like running it as a cron job or daemon or interactively. Ask the monks; read the holy texts. Some monk likely addressed such an issue in the past and devised an elegant yet functional solution ( like encasing the server in concrete and sinking it in the Atlantic ). Worst case, it will provide the Monastary an interesting query. UPDATE: oh, yeah ... it is likely legally sticky to store privilliged info in your code ... due dilligence and all that ...
HTH
In Section
Meditations
|
|
||||||||||||||||||||||||