9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] cwfs footgun
Date: Sun, 18 Dec 2022 20:43:58 +0100	[thread overview]
Message-ID: <CAFSF3XMHRjod3YAQHDijMgR29itoa875W8i7He4VFSEXN5BVHw@mail.gmail.com> (raw)
In-Reply-To: <C8B1A836-6210-42AF-9C3C-AA2D3B003018@stanleylieber.com>

so i toggled twice here, and i got:
"none disabled" as the last line.

i guess that means that none access is disabled?
my cwfs config block (first block at beginning of my cwfs cache
partition) doesn't mention any "nonone".
does this mean after a reboot none will be enabled?

On 12/18/22, Stanley Lieber <sl@stanleylieber.com> wrote:
> On Dec 18, 2022, at 2:20 PM, hiro <23hiro@gmail.com> wrote:
>>
>> can somebody please elaborate on the risks stemming from "nonone" ?
>>
>> On 12/18/22, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
>>>> will existing installations who were setting nonone via /srv/cwfs.cmd
>>>> now
>>>> be exposed until
>>>> they set nonone permanently via the fsconfig console?
>>>
>>> yes.
>>>
>>> --
>>> cinap
>
> by default, when cwfs is listening on port 564, anyone can attach as user
> none. nonone disables it.
>
> sl
>
>
>

  reply	other threads:[~2022-12-18 19:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  0:37 hiro
2022-12-18 14:21 ` cinap_lenrek
2022-12-18 16:37   ` Stanley Lieber
2022-12-18 19:08     ` cinap_lenrek
2022-12-18 19:20       ` hiro
2022-12-18 19:20         ` hiro
2022-12-18 19:22         ` Stanley Lieber
2022-12-18 19:43           ` hiro [this message]
2022-12-18 20:26             ` cinap_lenrek
2022-12-18 20:29           ` cinap_lenrek
2023-01-06  0:59             ` hiro
2023-01-06  2:57               ` sl
2023-01-06  3:58                 ` Alex Musolino
2023-01-06  4:38                   ` sl
2023-01-06  5:20                     ` hiro
2023-01-06  5:43                       ` Stanley Lieber
2023-01-06 13:20                   ` cinap_lenrek

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=CAFSF3XMHRjod3YAQHDijMgR29itoa875W8i7He4VFSEXN5BVHw@mail.gmail.com \
    --to=23hiro@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).