- This topic has 3 replies, 2 voices, and was last updated Jan 24-12:13 pm by Bassman.
-
Posts
-
Bassman
antiX 19.1 is running well on my old Acer (dual-core Pentium B 970). I get the following issues after changing authentication (in control-centre)
to “su” (and reboot) : synaptic and gparted won’t accept root-password, can only be used using root-terminal. Cannot create snapshot,
get error-message: “linuxfs can not be established, not enough disk-space” (there is definitely enough space!).
When I switch back to authentication-method “sudo” erverything is working. I could reproduce this behavior.
I always use su-authentication and even deactivate sudo (root-terminal visudo), because in my opinion, “sudo” can be a security risk.
I did this on my antix 17.4.1-machine without any problems. Hope this can be solved, thanks in advance.
Greetings from Lower-saxony
BassmanAnonymous
Yes, several utilities (scripts, called from ControlCenter) are hardcoded to authenticate via gksu–}sudo
You would need to edit antixcc.sh and the affected utilities in order for them to use a different (su, pkexec) authentication mechanism.synaptic and gparted: check the files installed by their packages. IIRC, pkexec rules for them are automatically installed.
Also, if you intend to launch them via “icon” desktop launcher, you would need to call “synaptic-pkexec” instead of “synaptic”If you choose to forego use of sudo, you will need to examine the antixers file (in etc subdirectory) and decide alternative authentication handling for each of the commands listed. Also “cd /usr/local/bin && grep -inr sudo” and revise each of the sudo-dependent scripts.
5.3.2. Semantics for using environment variables for su changed
su has changed semantics in buster and no longer preserves the user environment variables DISPLAY and XAUTHORITY. If you need to run graphical applications with su, you will have to explicitly set them to allow access to your display. See bug #905409 for an extensive discussion.
.
https://wiki.debian.org/NewInBuster
The su command in buster is provided by the util-linux source package, instead of the shadow source package, and no longer alters the PATH variable by default. This means that after doing su, your PATH may not contain directories like /sbin, and many system administration commands will fail. There are several workarounds:
Use su – instead; this launches a login shell, which forces PATH to be changed, but also changes everything else including the working directory.
Use sudo instead. sudo still runs commands with an altered PATH variable.
To get a regular root shell with the correct PATH, you may use sudo -s.
To get a login shell as root (equivalent to su -), you may use sudo -i.
Put ALWAYS_SET_PATH yes in /etc/login.defs to get an approximation of the old behavior. This is documented in su(1) but not in login.defs(5). It may also cause a harmless error message to appear in some situations (see 905564).
Put the system administration directories (/sbin, /usr/sbin, /usr/local/sbin) in your regular account’s PATH (see EnvironmentVariables for help with this).
FWIW, included the debian.org links b/c you wrote “I did this on my antix 17.4.1-machine without any problems”
…but you might not yet be aware of those changes (gotchas) introduced by upstream debian.Thank you very much for your reply, skidoo. You’re right, I did not know about the changes in buster. Now i have clear and detailed informations
and will consider using sudo further on.
- You must be logged in to reply to this topic.
