That's not necessarily true. The coder can run the script in the dev environment, so they can see the dev database password. But the production db passwords remains hidden to them.
Moreover, the coder can't change the code to show the password. Such a change wouldn't pass the code review.
($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,
| [reply] [d/l] |
Note that the OP wants to hide the password *from the script*. Even in that scenario, the script will still see the password.
But yeah, it's a good point that access to both the production password and the production script should be controlled.
| [reply] |
For the record, I never asked to hide the password from the script.
| [reply] |