[Bug 251795] Re: /etc/environment PATH should not have quotes

2011-06-10 Thread Clint Byrum
** Patch added: "fix-quote-expansion.patch" https://bugs.launchpad.net/ubuntu/+source/krb5-appl/+bug/251795/+attachment/2164419/+files/fix-quote-expansion.patch ** Tags added: patch ** Changed in: krb5 (Ubuntu) Importance: Undecided => Low ** Changed in: krb5-appl (Ubuntu) Importance:

[Bug 251795] Re: /etc/environment PATH should not have quotes

2011-06-10 Thread Clint Byrum
Reading the code as suggested by Sam, I see that everything after "=" and before a newline is copied into the environment using 'setenv()'. So no quote expansion is done. I'm not sure what the fix is, but there's certainly the possibility that programs will misinterpret this. I'm marking it as Conf

[Bug 251795] Re: /etc/environment PATH should not have quotes

2011-06-10 Thread Clint Byrum
** Also affects: krb5-appl (Ubuntu) Importance: Undecided Status: New ** Changed in: krb5-appl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.ne

[Bug 251795] Re: /etc/environment PATH should not have quotes

2011-06-10 Thread Clint Byrum
** Changed in: krb5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/251795 Title: /etc/environment PATH should not have quotes To manage notifi

Re: [Bug 251795] Re: /etc/environment PATH should not have quotes

2011-06-06 Thread Sam Hartman
So, fixing this particular bug in krb5-rsh-server is almost certainly relatively easy. Fixing krb5-rsh-server to use PAM directly is more involved; it should be done, but there is not a lot of resources going into krb5-rsh-server and krb5-clients at the moment. Upstream split these into the krb5-

[Bug 251795] Re: /etc/environment PATH should not have quotes

2011-06-06 Thread Steve Langasek
This behavior has persisted in /etc/environment now for at least 3 years, with only one report of misbehavior as a result. I don't believe it's worth the effort to try to correct this now and risk getting inconsistent behavior on upgraded vs. newly-installed systems, especially as pam_env, which o