From: Darren Bane <darren.bane@gmail.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Re: secstore and PAKserver
Date: Tue, 28 Aug 2007 11:32:19 +0100 [thread overview]
Message-ID: <fb0tjj$fcu$1@majestic.ukshells.co.uk> (raw)
In-Reply-To: <315ad2d6239bdd92272f868c3cdae53f@proxima.alt.za>
lucio@proxima.alt.za wrote:
> 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
Are US patents applicable outside the US? I know copyright is, under the
Berne convention, but I thought the patent systems were still strictly
national.
--
Darren Bane
next prev parent reply other threads:[~2007-08-28 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 9:39 [9fans] " lucio
2007-08-28 10:32 ` Darren Bane [this message]
2007-08-28 12:52 ` [9fans] " Anthony Sorace
2007-08-28 13:34 ` Gorka Guardiola
2007-08-28 23:49 ` Andrés Domínguez
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='fb0tjj$fcu$1@majestic.ukshells.co.uk' \
--to=darren.bane@gmail.com \
--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).