From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] secstore and PAKserver
Date: Tue, 28 Aug 2007 18:19:24 -0400 [thread overview]
Message-ID: <20070828221926.4D1BA1E8C35@holo.morphisms.net> (raw)
In-Reply-To: <96cb5a995b85bf656a8ddf7ef4356336@proxima.alt.za>
> 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.
I am not a lawyer; this is not legal advice.
The Lucent Public License permits redistribution of the programs
contained in the Plan 9 distribution, secstore included, in source
or binary forms, and includes appropriate copyright and patent
licenses. I believe that is the only license needed for me to
distribute the p9p programs. I have no special arrangement
with Lucent.
The details are in /LICENSE.
Of course, in such licensing situations, I have never understood
where the line is between redistributing the entire Plan 9 software
(obviously permitted, with copyright and patent licenses granted)
and redistributing just a few snippets of Plan 9 code that make up
an insignificant part of a larger program that happens to use
techniques from those same patents. I'm fairly certain p9p is on
the first side of that line, but I still don't know where the line is.
If this really matters to you, you should talk to a lawyer.
If you're not using Plan 9 code, you might look at SRP.
I don't think the licensing issues are any less murky than PAK,
but they are at least more widely studied.
Russ
next prev parent reply other threads:[~2007-08-28 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 9:32 lucio
2007-08-28 22:19 ` Russ Cox [this message]
2007-09-06 2:42 ` William Josephson
2007-08-27 9:39 lucio
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=20070828221926.4D1BA1E8C35@holo.morphisms.net \
--to=rsc@swtch.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).