From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 92271] Provide a way to really delete files, please
Date: Tue, 03 Feb 2015 17:47:27 +0000 [thread overview]
Message-ID: <bug-92271-13602-QpB8HjDX0i@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-92271-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=92271
--- Comment #24 from Alexander Holler <holler@ahsoftware.de> ---
Sorry, but that doesn't make any sense (comment #22).
As all these companies already fail with 'rm', still offer 'shred', there is
nothing more to loose. It can't become worse, just better.
And that is would this approach is or was about (as written on LKML, I've
already given up).
And if people do answer with complications like snapshots and whatever (as bug
#92261), I really have to wonder. Where does the documentation for 'rm' or even
'shred' mention that it is unable to delete files from backups, snapshots or
the like?
Nobody has to advertise this scheme in way it doesn't work.
Maybe it was a fault to mention the word secure, and I should have used
unlinkat_w() (for wipe), because everyone seems to end up in panic nowadays
when they get in contact with the word secure.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-02-03 17:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 11:47 [Bug 92271] New: Provide a way to really delete files, please bugzilla-daemon
2015-01-29 19:13 ` [Bug 92271] " bugzilla-daemon
2015-01-29 19:30 ` bugzilla-daemon
2015-01-29 19:49 ` bugzilla-daemon
2015-01-29 20:59 ` bugzilla-daemon
2015-01-29 21:01 ` bugzilla-daemon
2015-01-29 21:20 ` bugzilla-daemon
2015-01-29 21:55 ` bugzilla-daemon
2015-01-29 22:02 ` bugzilla-daemon
2015-01-29 22:11 ` bugzilla-daemon
2015-01-31 17:21 ` bugzilla-daemon
2015-01-31 18:36 ` bugzilla-daemon
2015-01-31 20:56 ` bugzilla-daemon
2015-02-01 1:51 ` bugzilla-daemon
2015-02-01 1:58 ` bugzilla-daemon
2015-02-01 10:14 ` bugzilla-daemon
2015-02-01 10:35 ` bugzilla-daemon
2015-02-01 11:04 ` bugzilla-daemon
2015-02-01 16:33 ` bugzilla-daemon
2015-02-01 17:18 ` bugzilla-daemon
2015-02-02 8:32 ` bugzilla-daemon
2015-02-02 11:13 ` bugzilla-daemon
2015-02-02 17:12 ` bugzilla-daemon
2015-02-03 17:29 ` bugzilla-daemon
2015-02-03 17:44 ` bugzilla-daemon
2015-02-03 17:47 ` bugzilla-daemon [this message]
2015-02-03 18:20 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-92271-13602-QpB8HjDX0i@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).