From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] Foundation new releases question
Date: Thu, 08 Apr 2021 16:39:18 +0200 [thread overview]
Message-ID: <5E822557334CF8E10AD34450F8015D4A@felloff.net> (raw)
In-Reply-To: <c2cd6248-21c8-4088-9aa5-6daa099430ac@www.fastmail.com>
> Yep. I might be able to understand that change, but less so the later breaking change to 9p auth.
What 9p change for auth are you talking about?
The dp9ik implementation in 9front just uses p9any to negotiate
it and p9sk1 is still supported; tho by default we have p9sk1
disabled at the authentication server now to prevent the offline
dictionary attack on the DES encrypted tickets that p9sk1 uses
(tho it can be enabled by a flag in the authservers startup script).
The code changes to have both auth protocols work concurrently
was actually the thing that took the most work and it took
over a year of transition period until we could disable
p9sk1 by default.
I'm not aware of anyone changing 9p.
--
cinap
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tc472e4a0c0b6f084-M611da16b4751d70c9cefd61d
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-04-08 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 16:31 leimy2k via 9fans
2021-04-01 17:03 ` sirjofri
2021-04-02 4:20 ` Lucio De Re
2021-04-02 5:25 ` Devon H. O'Dell
2021-04-02 8:34 ` vic.thacker
2021-04-02 15:06 ` Devon H. O'Dell
2021-04-02 16:53 ` hiro
2021-04-03 15:27 ` Ethan Gardener
2021-04-03 15:37 ` hiro
2021-04-03 15:39 ` hiro
2021-04-03 15:47 ` Keith Gibbs
2021-04-03 18:17 ` hiro
2021-04-05 11:43 ` Ethan Gardener
2021-04-06 2:05 ` Anthony Martin
2021-04-08 14:39 ` cinap_lenrek [this message]
2021-04-09 12:57 ` Ethan Gardener
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=5E822557334CF8E10AD34450F8015D4A@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9fans@9fans.net \
/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).