Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
On Wed, Jan 11, 2006 at 06:38:14AM -0500, Michael Stone wrote: It looks like someone needs to replace the RSA md5 implementation with one of the GPL-compatible ones, correct? I'm inclined to just dump the current code and go with freebsd's implementation of libpam-opie, just haven't had time. Any progress on this? Reimplementing the offending code would probably just be a few hours (including also fixing the code to write to the wtmp, although perhaps the advertising clause could be removed since Berkeley announced it could be removed for their software a few years ago?), but there's no point if you're replacing the code anyhow. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
On Sat, Jul 15, 2006 at 06:53:09PM -0400, Michael Stone wrote: including also fixing the code to write to the wtmp ? An authentication module shouldn't be writing to wtmp. Don't ask me why, but it does. Anyhow, the code is completely useless -- the two calls to opielogwtmp() can be replaced by a single one to logwtmp() AFAICS, and then the wtmp code can just go away. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
On Sun, Jul 16, 2006 at 12:46:38AM +0200, Steinar H. Gunderson wrote: Any progress on this? Nope. including also fixing the code to write to the wtmp ? An authentication module shouldn't be writing to wtmp. -- Michael Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
reassign 328923 opie thanks On Sun, Jul 16, 2006 at 12:53:46AM +0200, Steinar H. Gunderson wrote: ? An authentication module shouldn't be writing to wtmp. Don't ask me why, but it does. Anyhow, the code is completely useless -- the two calls to opielogwtmp() can be replaced by a single one to logwtmp() AFAICS, and then the wtmp code can just go away. So, I figured out: It's part of libopie. libpam-opie doesn't use the included libopie, though; in fact, the clean target does an rm -rf on it. (Not a very friendly thing to do; I had just spent some time replacing all the offending code in there!) Anyhow, the offending code is in the opie source package, so I'm reassigning. I've found appropriate replacement code, and it looks easy enough to slot in; expect a patch soon. /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
Hi Michael, Is anything being done about this bug? It looks like someone needs to replace the RSA md5 implementation with one of the GPL-compatible ones, correct? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
On Wed, Jan 11, 2006 at 03:25:17AM -0800, you wrote: Is anything being done about this bug? Not really. It looks like someone needs to replace the RSA md5 implementation with one of the GPL-compatible ones, correct? I'm inclined to just dump the current code and go with freebsd's implementation of libpam-opie, just haven't had time. Mike Stone -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328923: libpam-opie: GPL/4-clause BSD/RSA license conflict
Package: libpam-opie Severity: serious Justification: Policy 2.2.1 The package links code licensed under the GPL to code which is covered by licenses with advertising clauses, for example: | License to copy and use this software is granted provided that it | is identified as the RSA Data Security, Inc. MD5 Message-Digest | Algorithm in all material mentioning or referencing this software | or this function. | | License is also granted to make and use derivative works provided | that such works are identified as derived from the RSA Data | Security, Inc. MD5 Message-Digest Algorithm in all material | mentioning or referencing the derived work. | | RSA Data Security, Inc. makes no representations concerning either | the merchantability of this software or the suitability of this | software for any particular purpose. It is provided as is | without express or implied warranty of any kind. | | These notices must be retained in any copies of any part of this | documentation and/or software. Or: | 1. All terms of the UC Berkeley copyright and license must be followed. | 2. Redistributions of source code must retain the above copyright |notice, this list of conditions and the following disclaimer. | 3. Redistributions in binary form must reproduce the above copyright |notice, this list of conditions and the following disclaimer in the |documentation and/or other materials provided with the distribution. | 4. All advertising materials mentioning features or use of this software |must display the following acknowledgements: | | This product includes software developed by the University of | California, Berkeley and its contributors. | | This product includes software developed at the Information | Technology Division, US Naval Research Laboratory. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
