linux-kernel - Re: Suggested new user link command

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 for Android: free password hash cracker in your pocket

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

Message-ID: <CAFLxGvxpe78WhrEKcKRt5XRBMtT-mZUe9Bm=sQsn8-f1TnX0eQ@mail.gmail.com>
Date:   Tue, 1 May 2018 13:04:36 +0200
From:   Richard Weinberger <richard.weinberger@...il.com>
To:     Tony Wallace <tony@...y.gen.nz>
Cc:     Bernd Petrovitsch <bernd@...rovitsch.priv.at>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: Suggested new user link command

On Tue, May 1, 2018 at 12:58 PM, Tony Wallace <tony@...y.gen.nz> wrote:
> Good point.  But there are gid and uid fields in inode disc record.
>
> https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Inode_Table
>
> I assume these can be use to ensure that the directory in which it is to
> be placed has permissions to accept the inode.  If that is not the case
> then it would have to be a root only syscall.

Before we dig into details, please come up with a very good use case. :-)
But I'm with Bernd, I don't think it is worth the permissions hassle.

-- 
Thanks,
//richard