Ray Strode wrote:
From: Ray Strode <rstrode@xxxxxxxxxx>
If the user is using a systemd system, then its useful to grab the
environment from the systemd user manager process.
----
The other issue you don't really touch on, is why should this be hard-
coded in various programs when this is seems exactly like why PAM was
invented.
I.e. why not have a PAM module, say "pam_sysd_env", that gets the
env from the systemd user module(s), so any programs using
PAM can include in their security/authentication stack, the same
way pam_env might be used now (not that they are necessarily mutually
exclusive).
One of the issues with systemd is that it is doesn't re-use
existing interfaces, but tends to force programs to make changes to work
with sysd, where if it used the existing interfaces, no program-specific
changes might be required and no explicit dependencies are built in
tools so that the same tools can be used on sysd systems, vs. non-sysd
systems.
Minimizing code changes in existing, working code seems like a
safer design decision. It is especially true that the more code paths
that are added to programs, the more test paths and opportunities for
failure
are added.
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
