basic/env-util: drop the validation when deserializing environment
The environment variables we've serialized can quite possibly contain characters outside the set allowed by env_assignment_is_valid(). In fact, my environment seems to contain a couple of these: * TERMCAP set by screen contains a '\x7f' character * BASH_FUNC_module%% variable has a '%' character in name Strict check of environment variables name and value certainly makes sense for unit files, but not so much for deserialization of values we already had in our environment.
This commit is contained in:
@@ -809,10 +809,5 @@ int deserialize_environment(char ***environment, const char *line) {
|
||||
if (r < 0)
|
||||
return r;
|
||||
|
||||
if (!env_assignment_is_valid(uce)) {
|
||||
free(uce);
|
||||
return -EINVAL;
|
||||
}
|
||||
|
||||
return strv_env_replace(environment, uce);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user