You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the expected behaviour is to remove that variable from the environment. But the parser does not check for '=' signs, so if have this in the conf file (NOT in the env file):
this_does_not_do_what_expected=yeah
or even this:
neither_does_this=ohyeah! DEFAULT=
the module tries to remove the variable "this_does_not_do_what_expected=yeah" from the environment (as per debug log: remove variable "this_does_not_do_what_expected=yeah"), but this results in adding the variable "this_does_not_do_what_expected" instead, with value = "yeah".
Note that this is the reason why the parsing of the user environment file seems to work (see #6)
The text was updated successfully, but these errors were encountered:
I believe we should make this behavior official and documented. Of course the attempt to remove the "this_does_not_do_what_expected=yeah" should be dropped too.
ldv-alt
changed the title
Equal sign not properly handled in conf file
pam_env: Equal sign not properly handled in conf file
Apr 15, 2020
If in conf file I write:
variable
or
variable DEFAULT=
the expected behaviour is to remove that variable from the environment. But the parser does not check for '=' signs, so if have this in the conf file (NOT in the env file):
this_does_not_do_what_expected=yeah
or even this:
neither_does_this=ohyeah! DEFAULT=
the module tries to remove the variable "this_does_not_do_what_expected=yeah" from the environment (as per debug log: remove variable "this_does_not_do_what_expected=yeah"), but this results in adding the variable "this_does_not_do_what_expected" instead, with value = "yeah".
Note that this is the reason why the parsing of the user environment file seems to work (see #6)
The text was updated successfully, but these errors were encountered: