linux-kernel - Re: Variant symlink filesystem

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:	Fri, 11 Mar 2016 21:04:29 +0100
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Cole <cole@...eqint.net>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Variant symlink filesystem

On Fri, Mar 11, 2016 at 5:20 PM, Cole <cole@...eqint.net> wrote:
> Hi,
>
> I have written a Variant Symlink Filesystem for linux, currently
> implemented as a kernel module:
> https://github.com/onslauth/varsymfs
> The code was written for the 3.x kernel.
>
> I would like to try to get this included into the linux kernel, and am
> willing to hand over all copyright and change the license as needed.
> As such, I would like to know what I can do to try to make this
> happen.
>
> If the code quality or standards are not up to par with those of the
> linux kernel, or code needs to change due to newer changes introduced
> into the kernel, please let me know and I will endeavour to make the
> necessary changes.
>
> Please can you also cc me in any replies, as I am not currently
> subscribed to the list.

Why does this need to be a kernel filesystem and not a filesystem in
userspace (FUSE)?
Especially as you are dealing with environment variables which are
owned and controlled
by userspace.

-- 
Thanks,
//richard