From: Jarkko Sakkinen <jarkko@kernel.org>
To: "Mickaël Salaün" <mic@digikod.net>
Cc: Justin Suess <utilityemal77@gmail.com>, landlock@lists.linux.dev
Subject: Re: Landstrip
Date: Wed, 10 Jun 2026 12:46:44 +0300 [thread overview]
Message-ID: <aikyhKl829s_digC@kernel.org> (raw)
In-Reply-To: <aikxK37vyUmv1yLm@kernel.org>
On Wed, Jun 10, 2026 at 12:41:03PM +0300, Jarkko Sakkinen wrote:
I'm not sure if I fully understand this.
>
> I modified my client to temporarily use syscalls with the plan to return
> back using it as soon as it has all the features.
>
> It is only small portion of the implementation so it really is not a big
> deal. There's also Window and macOS.
>
> I.e. it is internal code for the client not a sloppy fork and I can
> do git revert + integration once there is the feature available.
>
> I have direct FFI also on macOS and Win32.
And I'm obviously returning back to your crate in future. No intention
to maintain syscall wrappers in long-term but right now just for
testing stuff it was useful temporal solution.
For the spec I'm mapping against see:
https://github.com/anthropic-experimental/sandbox-runtime
I saw the code and realized that it does not have anything for Windows
and Seatbelt and Bubblewrap do not pair too well so I decided to make
a fully parametrized version of it so that it could be swapped as
internals for ASR.
I don't have Claude Code installed on any of my machines but since that
policy has high spread it seemed like worth of focusing into as an app
sandboxing policy. I.e. probably could be used in most of coding agents.
So.. I don't think there's any problem here really.
BR, Jarkko
prev parent reply other threads:[~2026-06-10 9:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 1:42 Landstrip Jarkko Sakkinen
2026-06-05 19:19 ` Landstrip Justin Suess
2026-06-08 2:28 ` Landstrip Jarkko Sakkinen
2026-06-08 6:24 ` Landstrip Jarkko Sakkinen
2026-06-09 18:25 ` Landstrip Mickaël Salaün
2026-06-10 9:40 ` Landstrip Jarkko Sakkinen
2026-06-10 9:46 ` Jarkko Sakkinen [this message]
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=aikyhKl829s_digC@kernel.org \
--to=jarkko@kernel.org \
--cc=landlock@lists.linux.dev \
--cc=mic@digikod.net \
--cc=utilityemal77@gmail.com \
/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.