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 to use full-disk encryption to ensure that a small set of sensitive files are safe. Encryption isn't without cost - I don't want to have a pointless encryption layer in place while I'm recording direct to HD. This is 2012, not 1992 - “all or nothing” solutions don't cut it. If swap is encrypted, then core dumps should be too. Otherwise what's the point?
Why have you made this bug public? Why is an easy fix the goal? Why do you expect WONTFIX? Are you saying that if a fix isn't easy, it isn't worth doing? Dumping sensitive data somewhere public IS A BUG. You can patronisingly point out as many “well known problems” as you like. It doesn't change the fact that this particular problem doesn't exist on Debian but does on Ubuntu, because they've decided to dump sensitive data in an unencrypted directory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1077074 Title: /var/crash is unencrypted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1077074/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
