Bug#307293: gradm2: requires /sbin in user's PATH
Package: gradm2 Version: 2.1.5-2 Severity: normal Tags: patch gradm2's wrapper script, /sbin/gradm2, will only work if the user invoking it has /sbin in their PATH. For cp convenience, here's a patch: sed -i 's/gradm/\/sbin\/gradm/' gradm2 Best regards, Jan 'jast' Krueger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307293: gradm2: requires /sbin in user's PATH
Ups, you misunderstood me. I'm asking how someone can start gradm2 (the wrapper) without /sbin in PATH? You have to have /sbin in PATH to start Well, some people start these things using an absolute path instead of adding /sbin to their PATH. Don't ask me why they'd do that but I've seen it several times. Also, if I recall correctly, Debian doesn't include /sbin in PATH by default (except for root). Anyway, thanks! Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#307293: gradm2: requires /sbin in user's PATH
Well, if /sbin is not in the user's PATH, then s/he can't start the wrapper even, only with full path. Can you please give me some information when such thing happens that user can start the wrapper, but s/he has not /sbin in PATH? You're, of course, right. Nothing prevents people from running gradm2_2x without having /sbin in PATH but the wrapper script won't work, and this will confuse less experienced users (and annoy those who manage to identify the problem). Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#305176: gradm2: Wrapper script breaks role authentication
Subject: gradm2: Wrapper script breaks role authentication Package: gradm2 Version: 2.1.5-1 Severity: important Tags: patch I'm using Grsecurity 2.1.5 (upstream version) together with Linux 2.6.11.7 (upstream version). When authenticating to a special role using a password, for example gradm2 -a admin, syslog indicates that I am immediately unauthenticated from the role. Consequently, I can't use any special roles at all; in particular, admin access is not possible. Apparently Grsecurity unauths a role when the parent process of the authenticator exits. In Debian, this is the wrapper script /sbin/gradm2. I could fix the bug by having the wrapper script 'exec' the real gradm2. This way, gradm2_2* replaces the wrapper process and Grsecurity will keep the role authenticated. I marked this bug important instead of grave because a) RBAC can still be turned off by using gradm2 -D, b) RBAC itself works, authentication doesn't, c) Authentication works when you call gradm2_2* directly. Thanks and best regards Jan -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.7-grsec -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
