[LSM/Landlock] Adding ability to sandbox TTYs

COHEN-SCALI Remi (AMPERE) remi.cohen-scali at renault.com
Sun Jun 16 18:02:03 UTC 2024


Hi

A feature request on landlock is about sandboxing ttys management. I'd like to propose an api for this feature but before I'd like to hear from you about what could be proposed to developers.
Of course the standard approach can be provided for "locking" access to some syscalls. It will allow a dev to setup a ttys mngt for his app and then lock it. However I think this will not be enough for most of the use case for applications making an intensive usage of tty framework.
So I will go first by proposing a standard approach. But in a second step, and for also allowing apps having an intensive ttys framework usage to use landlock, I think it could be interesting to propose another approach: 
something as... providing the app a way to define several configurations and allow it to switch from one to another
or ...

Have you got ideas for this ... I can't wait hearing from you if you have ideas about ...

Thanks

PS: I saw @gnoack proposals about this tty handling in landlock and  they seems to be, at least, a good starting point. I'm also looking at several apps using teletypewriter management (gtkterm, minicom,  vterm, shells and one I specifically love and use, emacs).

Rc5kali

Confidential C
-- Disclaimer ------------------------------------ 
Ce message ainsi que les eventuelles pieces jointes constituent une correspondance privee et confidentielle a l'attention exclusive du destinataire designe ci-dessus. Si vous n'etes pas le destinataire du present message ou une personne susceptible de pouvoir le lui delivrer, il vous est signifie que toute divulgation, distribution ou copie de cette transmission est strictement interdite. Si vous avez recu ce message par erreur, nous vous remercions d'en informer l'expediteur par telephone ou de lui retourner le present message, puis d'effacer immediatement ce message de votre systeme.

*** This e-mail and any attachments is a confidential correspondence intended only for use of the individual or entity named above. If you are not the intended recipient or the agent responsible for delivering the message to the intended recipient, you are hereby notified that any disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender by phone or by replying this message, and then delete this message from your system.




More information about the Linux-security-module-archive mailing list