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-next>] [day] [month] [year] [list]
Message-ID: <0597ffe1-f80e-d5dd-e20d-da68bd8a189a@gmx.de>
Date:   Wed, 7 Feb 2018 13:38:49 +0100
From:   "Enrico Weigelt, metux IT consult" <metux@....de>
To:     linux-kernel@...r.kernel.org
Cc:     aganti@...gle.com
Subject: adding plan9-like usernames to the kernel

Hi folks,


as part as a little research project for bringing Plan9 semantics
to Linux, I'd like to add textual usernames. In contrast to *nix,
Plan9 doesn't use numerical IDs, but names.

Obviously that needs some internal mapping between names and ids.

Should this go into struct user_namespace (where per-namespace
uid mapping lives) or to struct cred / struct user_struct ?

The primary consumer of this username will be the /dev/caphash
and /dev/capuse devices for switching the UID.
(an interesting question of course is, how to allocate the
numerical UIDs for given usernames)


--mtx

-- 
Enrico Weigelt, metux IT consult
Free software and Linux embedded engineering
info@...ux.net -- +49-151-27565287

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ