Bash allows to export read-only variables and functions to the environment.

Also, when a Bash script is run, Bash sources the file BASH_ENV was set to, unless invoked with -p.

How do you protect against a hostile environment from within your Bash script? (In a portable way?)

'builtin' or 'unset' could be redefined by an attacker.

Is there any way, a Bash script can protect itself against a hostile environment?

Bash allows to export read-only variables and functions to the environment.

Also, when a bash script is run, Bash sources the file BASH_ENV was set to, unless invoked with -p.

How do you protect against a hostile environment from within your Bash script? (In a portable way?)

builtin or unset could be redefined by an attacker.

Is there any way, a bash script can protect itself against a hostile environment?

Bash allows to export read-only variables and functions to the environment.

Also, when a Bash script is run, Bash sources the file $BASH_ENV was set to, unless invoked with -p.

How do you protect against a hostile environment from within your Bash script? (In a portable way?)

'builtin' or 'unset' could be redefined by an attacker.

Is there any way, a Bash script can protect itself against a hostile environment?

Bash allows to export read-only variables and functions to the environment.

Also, when a Bash script is run, Bash sources the file BASH_ENV was set to, unless invoked with -p.

How do you protect against a hostile environment from within your Bash script? (In a portable way?)

'builtin' or 'unset' could be redefined by an attacker.

Is there any way, a Bash script can protect itself against a hostile environment?