On 2013-02-02 09:24, Steve Langasek wrote:
> Yes, setresuid() does make a difference over NFS, but it's the wrong
> interface. You should be using setfsuid(), *not* setresuid().
Sorry, but that distinction is above my head. You may want to fight with
pitti about it (he suggested setresuid() when sponsoring the
accountsservice code). ;-)
> If pam_env is already calling setfsuid() (which makes sense, as this is
> mature and well-exercised code, including on NFS),
That's what I found from reading the code, at least (when I was about to
write a patch...). But I may have missed something.
> Someone who can reproduce this will need to trace the issue to see
> what's happening.
Right.
** Changed in: pam (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1083605
Title:
env not changed in acc. with ~/.pam_environment if /home is on nfs
Status in “accountsservice” package in Ubuntu:
Fix Released
Status in “pam” package in Ubuntu:
Incomplete
Bug description:
When using localization setup from the login screen, the choice
doesn't work because of a permission error, if the user's home
directory is mounted with nfs. The problem happens because this is
done by root, usually not able to write over nfs shares. The problem
disappears if home directories are exported with no_root_squash
option. So, something is making access as root, instead as user.
I'm using Precise.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1083605/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
