From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] private /srv attach option
Date: Sun, 10 Jul 2022 17:47:27 -0400 [thread overview]
Message-ID: <A17897B86C532B7A28743DBC933E3464@eigenstate.org> (raw)
In-Reply-To: <6bb0ee7b-0916-a6df-913e-3f41256ce1eb@posixcafe.org>
Quoth Jacob Moody <moody@mail.posixcafe.org>:
> This patch add a 'p' attach option to srv to get a private session.
> The sessions work similarly to #| sessions.
>
> Attaching a private /srv does not effect future
> attaches to '#s' without the private option.
> I figure the global /srv can be explicitly
> given up through chdev if desired.
>
>
For those following along, https://shithub.us is now running
an updated version of this code, along with the patch to grow
the size of args, and a slightly tweaked version of auth/box.
sandboxing is now done with:
#!/bin/auth/box -r/mnt -r/usr/git -r/sys/lib/tcp80 -r/usr/web -r/sys/lib/shithub -r/n -r/dev -eM -s
<[3]/srv/clone{
d=`{<[0=3]read}
bind /srv/$d /srv
# ugly, but we don't want to leak the clone fd into
# procs that may stick around.
<[3=0]{
rfork n
bind /usr/web /mnt/static
execfs -m /usr/web /sys/lib/tcp80/gitrules
bind /mnt/static /usr/web/static
rfork n
cd /
exec /bin/tcp80
}
}
using auth/box as a #! line is quite nice, though even
with the `-s` option, the lines tend to get a bit long.
prev parent reply other threads:[~2022-07-10 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 11:50 Jacob Moody
2022-05-30 14:44 ` ori
2022-05-30 17:26 ` Jacob Moody
2022-05-30 20:04 ` ori
2022-05-31 7:03 ` hiro
2022-05-31 15:09 ` Jacob Moody
2022-05-31 16:04 ` Jacob Moody
2022-06-08 14:48 ` Jacob Moody
2022-06-22 15:22 ` cinap_lenrek
2022-05-30 14:56 ` ori
2022-07-10 21:47 ` ori [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=A17897B86C532B7A28743DBC933E3464@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).