From: Cory Visi <merlin@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Patches for MPPE/MPPC
Date: Wed, 25 Aug 2004 17:24:50 +0000 [thread overview]
Message-ID: <20040825172450.GB20213@toucan.gentoo.org> (raw)
Hi all. I am working on some ppp bugs and I noticed there is an excellent
kernel patch for MPPE/MPPC available for both 2.4 and 2.6 kernel versions:
http://www.polbox.com/h/hs001/
There have been existing patches similar to this one available for a long
time. However, the author of this patch effectively differentiates his
patches here:
"Some day, digging in the Net, I found MPPE implementation at
http://mirror.binarix.com/ppp-mppe/. I thought that it would be good to
complete that code with MPPC and make it freely available. So I wrote MPPC
part and added support for 56 bit keys in MPPE."
There may be some copyright issues with this patch. Here is another
relavent quote from the above website:
"Although the module's source code is completely free, MPPC itself is
patented algorithm. Patent for *Microsoft* PPC is holded by the Hifn Inc.
This is obvious ;-). Furthermore, MPPE uses RC4 encryption algorithm
which itself isn't patented, but RC4 is trademark of RSA Data Security
Inc. To avoid legal problems, US citizens shouldn't use this module."
I have two questions for everyone:
1. Can I include the ppp patch in the ppp ebuild? How do I do it legally?
2. Can we include the kernel patch in the gentoo-sources base patch set?
How do we do it legally?
Thanks,
Cory
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2004-08-25 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 17:24 Cory Visi [this message]
2004-08-25 17:40 ` [gentoo-dev] Patches for MPPE/MPPC Mike Frysinger
2004-08-29 8:25 ` John Huttley
2004-08-29 11:43 ` Jan Dubiec
2004-08-29 11:02 ` Jan Dubiec
2004-08-30 4:09 ` Cory Visi
2004-08-30 17:27 ` Jan Dubiec
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=20040825172450.GB20213@toucan.gentoo.org \
--to=merlin@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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