diff options
| author | Lennart Poettering <lennart@poettering.net> | 2014-02-10 12:32:03 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2014-02-10 13:18:16 +0100 |
| commit | 82adf6af7c72b852449346835f33184a841b4796 (patch) | |
| tree | 0dd1c4c6dcdd9760df65300e15bd3b53b5aad553 /src/core/execute.c | |
| parent | 0d3f7bb3a5bc6d5c0712f88a080fed388981bca3 (diff) | |
nspawn,man: use a common vocabulary when referring to selinux security contexts
Let's always call the security labels the same way:
SMACK: "Smack Label"
SELINUX: "SELinux Security Context"
And the low-level encapsulation is called "seclabel". Now let's hope we
stick to this vocabulary in future, too, and don't mix "label"s and
"security contexts" and so on wildly.
Diffstat (limited to 'src/core/execute.c')
| -rw-r--r-- | src/core/execute.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/src/core/execute.c b/src/core/execute.c index 437065465d..b941a024de 100644 --- a/src/core/execute.c +++ b/src/core/execute.c @@ -2123,7 +2123,6 @@ void exec_context_dump(ExecContext *c, FILE* f, const char *prefix) { fprintf(f, "%sSELinuxContext: %s\n", prefix, c->selinux_context); - } void exec_status_start(ExecStatus *s, pid_t pid) { |