5 Commits

Author	SHA1	Message	Date
Harald Hoyer	ebc05a09ad	core/execute: report invalid environment variables from files ... Because "export key=val" is not supported by systemd, an error is logged where the invalid assignment is coming from. Introduce strv_env_clean_log() to log invalid environment assignments, where logging is possible and allowed. parse_env_file_internal() is modified to allow WHITESPACE in keys, to report the issues later on.	2013-04-17 15:31:45 +02:00
Zbigniew Jędrzejewski-Szmek	5f9cfd4c38	man: rename systemd.conf to systemd-system.conf ... Alias as systemd-user.conf is also provided. This should help users running systemd in session mode. https://bugzilla.redhat.com/show_bug.cgi?id=690868	2013-02-13 09:48:32 -05:00
Thomas Hindoe Paaboel Andersen	641906e936	use strneq instead of strncmp	2013-02-13 00:56:13 +01:00
Lennart Poettering	123b964a53	manager: validate environment parameters for SetEnvironment(), UnsetEnvironment() bus calls	2013-02-11 23:54:30 +01:00
Lennart Poettering	4d1a690438	env: considerably beef up environment cleaning logic ... Now, actually check if the environment variable names and values used are valid, before accepting them. With this in place are at some places more rigid than POSIX, and less rigid at others. For example, this code allows lower-case environment variables (which POSIX suggests not to use), but it will not allow non-UTF8 variable values. All in all this should be a good middle ground of what to allow and what not to allow as environment variables. (This also splits out all environment related calls into env-util.[ch])	2013-02-11 03:54:50 +01:00