From: Stanley Lieber <sl@9front.org>
To: 9front@9front.org
Subject: Fwd: [9fans] replace p9sk1 with something better(9front)
Date: Thu, 02 Jul 2015 10:44:51 -0400 [thread overview]
Message-ID: <b301f7ec-cc9b-4862-8136-abbc48d22039@typeapp.com> (raw)
In-Reply-To: <5595227C.4090504@tfwno.gf>
[-- Attachment #1: Type: text/plain, Size: 664 bytes --]
test.
On Jul 2, 2015, 7:45 AM, at 7:45 AM, gracc <oniichan@tfwno.gf> wrote:
>as per http://wiki.9front.org/bounties
>>>replace p9sk1 with something better
>
>I'm looking to start on this, does anyone have thoughts on
>improvements?
>At the moment I am intending to just replace the DES keys with AES but
>is there any call for more structural changes?
>
>I was thinking that an overhaul using public keys might be appropriate
>so that the auth server would still be a trusted key holder but without
>secret keys having to leave the user's machine.
>
>(9front mailing list was down so im sending to 9fans instead, sorry if
>that's a bother)
[-- Attachment #2: Type: text/html, Size: 1339 bytes --]
parent reply other threads:[~2015-07-02 14:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5595227C.4090504@tfwno.gf>]
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=b301f7ec-cc9b-4862-8136-abbc48d22039@typeapp.com \
--to=sl@9front.org \
--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).