All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yves Rutschle <landlock@rutschle.net>
To: landlock@lists.linux.dev
Subject: Landlock setup
Date: Mon, 7 Nov 2022 17:22:16 +0000	[thread overview]
Message-ID: <20221107172216.GA10688@rutschle.net> (raw)

Hello everyone,

Following Mickael's presentation of Landlock at
Pass-the-Salt 2022, I intend to add support for it to sslh.

I'm starting from the beginning: compiling and running the
example, which so far complains the LSM is not loaded, when
the kernel tells me it is...

I'm running a stock Debian where I manually add landlock to
the command line:

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.18.0-3-amd64 root=UUID=79c3bdf6-4be2-46d6-b006-bb17170247b1 ro quiet lsm=landlock

the kernel indicates the LSM is started:

[    0.076550] LSM: Security Framework initializing
[    0.076559] landlock: Up and running.


Yet running the example fails:

# LL_FS_RO="/bin:/lib:/usr:/proc:/etc:/dev/urandom" LL_FS_RW="/dev/null:/dev/full:/dev/zero:/dev/pts:/tmp" ./lock bash -i
Failed to check Landlock compatibility: Function not implemented
Hint: Landlock is not supported by the current kernel. To support it, build the kernel with CONFIG_SECURITY_LANDLOCK=y and prepend "landlock," to the content of CONFIG_LSM.



What would I be doing wrong?

Cheers,
Y.




             reply	other threads:[~2022-11-07 17:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 17:22 Yves Rutschle [this message]
2022-11-07 18:02 ` Landlock setup Mickaël Salaün
2022-11-08 11:27   ` Yves Rutschle
2022-11-08 14:13     ` Mickaël Salaün
2022-11-08 17:15       ` Yves Rutschle
2022-12-16  9:44         ` Mickaël Salaün
2022-12-16  9:53           ` Yves Rutschle
2022-12-16 10:34             ` Mickaël Salaün
2023-01-08 15:29               ` Yves Rutschle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221107172216.GA10688@rutschle.net \
    --to=landlock@rutschle.net \
    --cc=landlock@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.