diff options
| author | David Kalnischkies <david@kalnischkies.de> | 2016-11-25 15:15:01 +0100 |
|---|---|---|
| committer | David Kalnischkies <david@kalnischkies.de> | 2016-12-16 13:50:00 +0100 |
| commit | 78db35195eddcd156130fff9ea3e895b30cbf9c3 (patch) | |
| tree | 93827ea711fae53ed1923ad157cdacaa90c2b45f /test/integration/test-apt-get-changelog | |
| parent | f47f4b195b4a4f8e72a6a120ed47a3d0120cd033 (diff) | |
reword "Can't drop priv" warning message
Note: This is a warning about disabling a security feature. It is
supposed to be scary as we are disabling a security feature and we
can't just be silent about it! Downloads really shouldn't happen
any longer as root to decrease the attack surface – but if a warning
causes that much uproar, consider what an error would do…
The old WARNING message:
| W: Can't drop privileges for downloading as file 'foobar' couldn't be
| accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
is frequently (incorrectly) considered to be an error message indicating
that the download didn't happen which isn't the case, it was performed,
but without all the security features enabled we could have used if run
from some other place…
The word "unsandboxed" is chosen as the term 'sandbox(ed)' is a common
encounter in feature lists/changelogs and more people are hopefully able
to make the connection to 'security' than it is the case for 'privilege
dropping' which is more correct, but far less known.
Closes: #813786
LP: #1522675
Diffstat (limited to 'test/integration/test-apt-get-changelog')
0 files changed, 0 insertions, 0 deletions