9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] notes on user none
Date: Sat, 23 Jan 2021 15:02:34 +0100	[thread overview]
Message-ID: <CAFSF3XOGc1rMG+pOcKp10hW8pZfLmTi3B0eWNS72JnMP1hzpVA@mail.gmail.com> (raw)
In-Reply-To: <d75bacdb-a9d0-4932-b0ca-bf3cc52f5e02@sirjofri.de>

yeah, if making nonone the default makes it all more consistent with
how it was in the labs that's what we should do, i agree.

very nice writeup, anthony.

On 1/23/21, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
> Hello,
>
> imo this is valuable research that should be documented if possible.
>
> This also makes clear the none differences between fossil and cwfs, and
> it's a nice template to look how hjfs works. Sadly I have no hjfs running
> anywhere, only cwfs[1].
>
> This also conforms to sl's suggestion to add nonone to cpurc or
> something, so that cwfs works more like fossil, which also makes the
> system more secure. I'd personally even think about making it the default
> and allow users to explicitly enable none authentication, but I don't
> think my vote counts that much. I'm sure ori, sl, cinap as well as many
> others have more experience to decide this.
>
> just my 2 cents.
>
> sirjofri
>
> [1] the "experimental" note always tells me not to use it. Also I'm happy
> with cwfs and have no reason to switch to hjfs, although users report
> that hjfs is pretty stable.
>

  reply	other threads:[~2021-01-23 14:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 23:44 Anthony Martin
2021-01-23  9:45 ` sirjofri
2021-01-23 14:02   ` hiro [this message]
2021-01-23 14:13 ` cinap_lenrek
2021-01-23 21:31 ` ori
2021-01-24  6:33   ` magma698hfsp273p9f
2021-01-25 19:44     ` ori
2021-01-31 21:42       ` magma698hfsp273p9f
2021-02-01 22:06         ` sirjofri

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=CAFSF3XOGc1rMG+pOcKp10hW8pZfLmTi3B0eWNS72JnMP1hzpVA@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).