From: adventures in9 <adventuresin9@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] patch your shit
Date: Sat, 24 Aug 2024 14:25:21 -0700 [thread overview]
Message-ID: <CAPfmpJBwe9TkHGFj9ZWkF1B6xRmAVBv=nSmhWBiFmyNMiJjKFg@mail.gmail.com> (raw)
In-Reply-To: <83dbbe63-a139-4dc6-af13-3abcafb9be6d@posixcafe.org>
hjfs does have the "experimental" warning XD
On Sat, Aug 24, 2024 at 2:23 PM Jacob Moody <moody@posixcafe.org> wrote:
>
> hjfs is not the default install, our number of holes is fine.
>
> On 8/24/24 15:15, Willow Liquorice wrote:
> > e https://9front.org/
> > /Only three remote holes in the default install, in a heck of a long time!/
> > s/three/four
> > w https://9front.org/
> >
> > - Willow
> >
> > On 24/08/2024 20:08, hiro wrote:
> >> some people did something that increases security apparently. so patch
> >> your shit.
> >>
> >> ref: 07aa9bfeef55ca987d411115adcfbbd4390ecf34
> >> parent: b05c74e7cb160f152e2f2cc2f6e0677763f8d57e
> >> author: Jacob Moody <moody@posixcafe.org>
> >> date: Sat Aug 24 12:58:31 EDT 2024
> >>
> >> lib9p: verify uname against returned AuthInfo from factotum (thanks humm)
> >>
> >> Before this it was possible to Tauth and Tattach with one
> >> user name and then authenticate with factotum using a different
> >> user name. To fix this we now ensure that the uname matches the returned
> >> cuid from AuthInfo.
> >>
> >> This security bug is still pending a cute mascot and theme song.
> >>
> >>
> >> mein name ist hase. bye.
>
next prev parent reply other threads:[~2024-08-24 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-24 19:08 hiro
2024-08-24 20:15 ` Willow Liquorice
2024-08-24 21:21 ` Jacob Moody
2024-08-24 21:25 ` adventures in9 [this message]
2024-08-24 21:37 ` sl
2024-08-24 21:40 ` Willow Liquorice
2024-08-24 21:55 ` Eli Cohen
2024-08-24 22:18 ` Jacob Moody
2024-08-25 0:55 ` Jacob Moody
2024-08-25 10:27 ` rgl
2024-08-25 6:56 ` Kristo
2024-08-26 14:32 ` hiro
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='CAPfmpJBwe9TkHGFj9ZWkF1B6xRmAVBv=nSmhWBiFmyNMiJjKFg@mail.gmail.com' \
--to=adventuresin9@gmail.com \
--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).