Environment vars will only be seen if you pipe them to the script, as you've done in your link.
However, if you set them on a line by line basis in a shell script they won't be visible.
Malk. | [reply] |
If you are on a linux box, try 'ps e'! On other systems I don't know the parameter.
Your other point would be deserved, if we wouldn't talk about ksh (or bash for that matter).
Echo is an internal command and will not be shown as a separate process, but as fork
of the ksh. No params to see here, please go away;-)
| [reply] |
Yep, 'ps e' shows loads of parameters. All those in the shell .rc file, and sundry that are also put in at various stages by anything else the shell uses.
Now, however, unless someone is willing to pull out all the set env variables by this method, and get the relevant spam, just to catch out this guy, then it's all but invisible.
If it's a case of this is too visible for the poster, then, so be it, I just feel that it's 'within reasonable bounds' of not being visible to ps, and all the commonly used forms.
Malk
| [reply] |
'ps e' only shows the environment for your own processes, if someone untrustworthy is running ps with your uid you've got bigger problems than whether he can parse the output and find some variables in it.
| [reply] |