9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "steve@quintile.net" <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] replace p9sk1 with something better(9front)
Date: Thu,  2 Jul 2015 13:12:08 +0100	[thread overview]
Message-ID: <9F4D8B7E-6AAF-4A9F-BB38-5D1B24EF4FDA@quintile.net> (raw)
In-Reply-To: <5595227C.4090504@tfwno.gf>

I think just replacing des keys with AES is not worth it. there is so little data that des is quite secure (imho).

replacing p9sk1 with pki is much more useful. rus posted to 9fans about wanting to do this so a terminal could cache tickets to speed auth when the auth server is remote - I cannot remember the details, sorry.

also pki would allow the old 9grid ideas to resurface, if there are enough plan9 machines left :-)

-Steve


ps. inferno already uses pki, it would be best to be compatible unless there is a very good reason not to be.



> On 2 Jul 2015, at 12:37, 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)



  reply	other threads:[~2015-07-02 12:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 11:37 gracc
2015-07-02 12:12 ` steve [this message]
2015-07-02 12:30 ` Anthony Sorace
2015-07-02 12:57   ` Charles Forsyth
2015-07-02 13:14     ` Charles Forsyth
2015-07-02 15:48       ` lucio
2015-07-02 16:44       ` Skip Tavakkolian
2015-07-02 17:38         ` Charles Forsyth
2015-07-02 20:15       ` 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=9F4D8B7E-6AAF-4A9F-BB38-5D1B24EF4FDA@quintile.net \
    --to=steve@quintile.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).