Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pam_env: Equal sign not properly handled in conf file #12

Open
guidovilla opened this issue Mar 2, 2017 · 1 comment
Open

pam_env: Equal sign not properly handled in conf file #12

guidovilla opened this issue Mar 2, 2017 · 1 comment

Comments

@guidovilla
Copy link

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)

@t8m
Copy link
Member

t8m commented Mar 2, 2017

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 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants