linux-kernel - Re: [PATCH 1/5] WIP: Add syscall unlinkat

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 04 Feb 2015 13:22:26 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	Lukáš Czerner <lczerner@...hat.com>
CC:	Al Viro <viro@...IV.linux.org.uk>, Theodore Ts'o <tytso@....edu>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/5] WIP: Add syscall unlinkat_s (currently x86* only)

Am 04.02.2015 um 13:07 schrieb Lukáš Czerner:

> The fact is that the current patches are useless for anything other
> than proof-of-concept. Now you know more that needs to be done or

That's wrong. The patches already work. If you delete a file which isn't 
in use by something else, the current contents will be wiped on 
traditional harddrives. I assume that already fulfills more than 50% of 
use cases of ordinary people.

> thought about, but if you're not willing to do the work, then please
> stop complaining about "high towers". I am not a maintainer and I
> thinks that the feedback you've got is entirely reasonable. Take it
> as you will.
>
> One more thing, can I ask you what were your expectations when
> posting those patches ?

I've posted them for other users which are happy with what I've 
explained above. Besides requesting an API which makes such a simple 
solution, in contrast to the the 's' bit, possible.

Alexander Holler

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/