From: Alex Musolino <alex@musolino.id.au>
To: 9front@9front.org
Subject: Re: [9front] cwfs footgun
Date: Fri, 06 Jan 2023 14:28:46 +1030 [thread overview]
Message-ID: <992175CE74233FDD14A74C7841551FAB@musolino.id.au> (raw)
In-Reply-To: <1C1048E2C391774EFECA92102DFB1F57@gaff.inri.net>
> http://fqa.9front.org/fqa7.html#7.3.3
Why do you have to type 'noauth' twice? To me the example makes it
look like authentication was already enabled, which would seem to make
the whole exercise pointless. Was the example generated on a machine
that already had authentication enabled perhaps? If not, what am I
missing?
Also, how does hjfs avoid this problem?
next prev parent reply other threads:[~2023-01-06 4:00 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
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 [this message]
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=992175CE74233FDD14A74C7841551FAB@musolino.id.au \
--to=alex@musolino.id.au \
--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).