[Expired for apport (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apport (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1077074
This release of Ubuntu is no longer receiving maintenance updates. If
this is still an issue on a maintained version of Ubuntu please let us
know.
** Changed in: apport (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The problem with /var/crash is that it violates the principle of least
surprise. Mounting /tmp and /var/tmp on tmpfs is a pretty obvious step
to take for anyone who is familiar with any modern GNU/Linux flavour. As
apport is Ubuntu specific it's considerably less obvious, and as this
has a security
Using ecryptfs instead of full disk encryption is a trade-off. There are
countless other directories where private information may get stored,
and which isn't encrypted by default, such as /tmp, /var/tmp, etc.
You can turn off apport's core dump handling by modifying the
/etc/default/apport file.
I haven't asked apport to write core dumps outside of $HOME. It just
does is BY DEFAULT. As someone who has used GNU/Linux since the mid-90s
and had countless core dumps land somewhere in my home directory I
shouldn't have to suddenly worry about them ending up somewhere else. I
also shouldn't have
Hi Julian - thanks for the bug report!
As the upstream maintainer of eCryptfs, I'd like to point out that this
is a well known problem with partial disk encryption technologies such
as eCryptfs. Information leaks are bound to happen when applications can
write to locations outside of the encrypted
