| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 25 May 2009 16:44:57 +0200 From: Christoph Pleger <Christoph.Pleger@...tu-dortmund.de> To: linux-kernel@...r.kernel.org Subject: chmod fails though it pretends to succeed Hello, I have a strange problem here with a C program that calls chmod. The C program is a PAM module called pam-devperm. The purpose of this module is to set appropriate device ownerships and permissions when a user logs in. But the module does not work as expected on my Ubuntu 9.04 system. When a user logs in the first time after system boot, only the device ownerships are changed, the permissions are not. When the user logs out and in again, permissions are changed, too. I added some lines of code to the the source of of pam-devperm so that it produces more debug output when changing the properties of /dev/dsp. The debug output showed me that chmod has been called to set the permissions of /dev/dsp to 0600 and that chmod returned 0, which means success. In spite of that, device permissions remain at 660. Now I have two questions: 1. What can be the reason for chmod to return a value of 0 though device permissions have not been changed? 2. What can be the reason why this chmod fails on the first login of a user, but succeeds on further logins? Regards Christoph -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists