From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] patch your shit
Date: Sat, 24 Aug 2024 17:18:15 -0500 [thread overview]
Message-ID: <affd4e50-5488-49a2-a0af-d94718f9cfa2@posixcafe.org> (raw)
In-Reply-To: <CAFSF3XO6BLKzBX1RgPYaxPSXF9NgNmTCm3XDWLiF1+KEi__=nQ@mail.gmail.com>
!WARNING!
As of the time of this writing (Sat Aug 24 22:17:26 GMT 2024) there is an issue
with this patch which causes hjfs to not permit none attaches. This is currently
being worked on and I suspect we'll have a solution within the next couple hours
but those running a hjfs CPU server may want to avoid updating immediately.
I will respond promptly to this thread once this bug has been patched, and I feel
it is safe to update these systems. I will provide a further write up once there is
a fix for the fix added.
- moody
On 8/24/24 14: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 22:20 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
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 [this message]
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=affd4e50-5488-49a2-a0af-d94718f9cfa2@posixcafe.org \
--to=moody@posixcafe.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).