9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Using Inferno factotum with Plan 9
Date: Thu, 16 Oct 2008 14:34:37 +0100	[thread overview]
Message-ID: <e11d1aade81eb1b79b3b2b66d696db9b@vitanuova.com> (raw)
In-Reply-To: <20081016115517.GA26994@unknown>

>Any chance of Plan 9's factotum learning how to speak infauth?

that was done as a GSoC project, but i then made the mistake
of trying to include it as part of a much larger change on
the Inferno side. it wasn't a silly mistake: factotum doesn't
support the key structure required for public keys and signatures,
so something more was needed. i also wanted to extend Inferno's
authentication scheme.  that in turn is requiring a big (ie, visible)
change in a few old Inferno modules and commands.

still, for your purposes the temporary hack of stashing the
existing certificate data in hex would be fine.
i'll send you some changes for you to try.



  reply	other threads:[~2008-10-16 13:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 11:55 Venkatesh Srinivas
2008-10-16 13:34 ` C H Forsyth [this message]
2008-10-16 14:08   ` hiro

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=e11d1aade81eb1b79b3b2b66d696db9b@vitanuova.com \
    --to=forsyth@vitanuova.com \
    --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).