From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] State of the 9front mailing list archives
Date: Fri, 3 Jun 2016 22:27:04 +0200 [thread overview]
Message-ID: <5e7518a93a2829c3e294b089c3abb788@felloff.net> (raw)
In-Reply-To: <D6AA6E32-A60B-406F-90C6-0540DC844FC7@stanleylieber.com>
it was indeed in the changelog of "the muscott icon of it! Why devil?" release:
"tcp567: run authserver with p9sk1 tickets disabled preventing offline password brute-force"
but i should have written a longger email announcing the change.
i know this is painfull. we'v almost spend a year on the whole topic,
implementing it so it could have a transition period.
regressions can happen at every release, no matter what. we do have
a procedure to update your stuff and be protected. we do not have
a procedure when your system got hacked.
for the lack of communicating this more loudly i'm sorry.
--
cinap
next prev parent reply other threads:[~2016-06-03 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 18:23 stanley lieber
2016-06-03 18:29 ` [9front] " cinap_lenrek
2016-06-03 18:45 ` stanley lieber
2016-06-03 20:27 ` cinap_lenrek [this message]
2016-06-04 6:31 ` BurnZeZ
2016-06-04 14:54 ` Benjamin Purcell
2016-06-04 21:35 ` arisawa
2016-06-03 18:51 ` Kurt H Maier
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=5e7518a93a2829c3e294b089c3abb788@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).