9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] secstore and PAKserver
Date: Mon, 27 Aug 2007 11:39:19 +0200	[thread overview]
Message-ID: <315ad2d6239bdd92272f868c3cdae53f@proxima.alt.za> (raw)

I note in /sys/src/cmd/auth/secstore/pak.c:

	// PAK is an encrypted key exchange protocol designed by Philip MacKenzie et al.
	// It is patented and use outside Plan 9 requires you get a license.
	// (All other EKE protocols are patented as well, by Lucent or others.)

I want to leverage the functionality of the secstore for a different
application (I'm not yet ready to publicize the details, but I will to
anyone who shows some interest), but this seems to put a bit of a
spanner in the works.  Naturally, I can prototype with it, but in the
long term I have either to licence the PAK stuff (who do I contact?)
or to replace the code with an analogous facility.

Has the licence been waved for p9p?  What are the terms of the
licence?  Does anyone know of licence free options to perform a
similar function?  I suppose I ought to ask what is so special about
PAK, too or, more to the point, what does it do that made Bell Labs
choose it for the secstore?  Maybe if I understood PAK better I'd be
able to decide whether it is as important in my application as it was
for the secstore.

++L



             reply	other threads:[~2007-08-27  9:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27  9:39 lucio [this message]
2007-08-28 10:32 ` [9fans] " Darren Bane
2007-08-28 12:52   ` Anthony Sorace
2007-08-28 13:34     ` Gorka Guardiola
2007-08-28 23:49       ` Andrés Domínguez
  -- strict thread matches above, loose matches on Subject: below --
2007-08-27  9:32 [9fans] " lucio
2007-08-28 22:19 ` Russ Cox
2007-09-06  2:42   ` William Josephson

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=315ad2d6239bdd92272f868c3cdae53f@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /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).