June 2005 - Freeradius-Devel - lists.freeradius.org

ZyXEL
by Shawn K. O'Shea 13 Jun '05

13 Jun '05

I just joined the devel list and was looking at the recent archives. My company uses a lot of ZyXEL equipment and we work with them pretty closely (some of their sales folks were just out here a few weeks ago and I have one of their APs sitting on my desk right now for 802.1X testing). If you are having trouble getting in touch with anyone, feel free to get in contact with me and I'll see what I can do. -Shawn ~~~~~~~~~~~~~~~~~~~~~~~~~ Shawn O'Shea Network Engineer Airpath Wireless, Inc. "Clearing the Way" 781-250-3500-office 781-250-3535-direct 781-250-3503-fax shawno(a)airpath.com http://www.airpath.com ~~~~~~~~~~~~~~~~~~~~~~~~~ CONFIDENTIALITY STATEMENT This electronic message contains information from Airpath Wireless, Inc., and may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this message is prohibited. If you have received this electronic message in error, please notify the sender immediately by reply e-mail shawno(a)airpath.com or telephone at (781) 250-3500.

1 0

Copyright infringement and GPL violation in tinypeap
by Alan DeKok 10 Jun '05

10 Jun '05

-----BEGIN PGP SIGNED MESSAGE----- Your web site http:/www.tinypeap.com (hosted at the Georgia Institute of Techology, machine "rhampora.cc.gatech.edu") is distributing programs built at least in part from code that is derived from the FreeRADIUS server project (http://www.freeradius.org) I refer you to the following URL's: http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=5649 This message contains text with error messages "rlm_eap_tls: SSL_read failed inside of TLS ". The "rlm_eap_tls" module is part of FreeRADIUS, is copyright by me personally, and is licensed under the terms of the GPL. However, in the forum post at: http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=4533 You claim that tinyPEAP is "closed source". You further do not acknowledge my copyright on code that you distribute. http://www.tinypeap.com/bin/peapd-beta1.zip This URL points to a file which contains "peapd.exe". That file contains at least the following text strings, which are either identical to strings included with FreeRADIUS, or substantially similar: - -- rlm_eap_tls: FATAL SSL error ..... %d rlm_eap_tls: %s failed inside of TLS (%d), TLS session fails. rlm_eap_tls: %s failed in a system call (%d), TLS session fails. handshake_send rlm_eap_tls: Application Data In SSL Connect mode In SSL Accept mode Before SSL Handshake Phase In SSL Handshake Phase SSL Connection Established SSL_read rlm_eap_tls: Requiring client certificate rlm_eap_tls: Error creating new SSL - -- This code is part of the FreeRADIUS project, and you are infringing on our copyright, and violating the GPL by copying it without following the terms of our license. Nothing under copyright law gives you permission to use our copyrighted code without our permission. The only license terms available for the code in question is the GNU GPL, which is distributed with the FreeRADIUS server source. The terms of that license require you to make the source code for derived works available under the same terms as the the original code. I refer you to section 2 (b): - --- b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. - --- We have tried contacting the public email address for tinypeap: "tinypeap(a)yahoo.com". We have yet to receive a response. We are sending this message to the contact address listed in "whois", and to the Georgia Institute of Technology Office of Legal Affairs, as you are distributing the infringing material from a machine hosted at that institute. You have 24 hours to remove all infringing binaries (tinypeap.exe, and any Linksys firmware containing the infringing code) from your website, or to comply with the terms of the GPL by releasing the source code to tinypeap under the GPL. If you do not choose to release the source under the GPL, you must remove the infringing code from any version of tinypeap that is released in the future. This removal may be done by re-writing the code in question. A simple edit of the text strings will not suffice, as our copyright applies to the binaries produced from the C source code, in addition to the text strings. If you do not comply within 24 hours, we will send a DMCA "take-down" notice to you personally, and to the office of the legal affairs. We hope you take our concerns seriously. Alan DeKok. The FreeRADIUS Server Project http://www.freeradius.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iQCVAwUBQqdpEakul4vkAkl9AQF02wP7BBA3R4Kfc79NNvBGX7R7h2xh2uxto816 CuYAuI51ArqqhjzKmB189Lz9xgMXN4ic0OL1CWuO2iAw5qY8occ2g7LVGwGUYbKM 9BxNSTPola0zzjFAwYK0aEgBU3wJnES3PBzwCOFQo9f16ks1oXHhrx8v2FFV//Ix eIOlG/+hitY= =OsyM -----END PGP SIGNATURE----- Alan DeKok.

4 4

tinyPEAP has said they will comply
by Alan DeKok 09 Jun '05

09 Jun '05

>From http://www.tinypeap.com ... 6/9/2005 tinyPEAP has stopped distributing the binaries due to the copyright infringement against FreeRADIUS Project. ... The author also says in private email that he apologizes, takes our concerns seriously, will re-write the relevant code. Thanks to everyone for their support & patience in this matter. Alan DeKok.

3 2

tinypeap update
by Alan DeKok 09 Jun '05

09 Jun '05

I called the Office of Legal Affairs listed on: http://www.gatech.edu/legal.php, Randy Nordin (404-894-4812). He was busy, and would be out the rest of the day. But I did leave a message re: copyright infringement, and asked him to respond to my previous email. I also contacted softwarefreedom.org, and asked for assistance. We'll see what comes up. Alan DeKok.

1 0

More GPL issues: anyone have a Zyzel box?
by Alan DeKok 09 Jun '05

09 Jun '05

http://www.nowthor.com/shopping/productdocs/ZyXEL-Vantage-Radius-50-v1.0-Us… Page 4-10, Figure 4-6. "Info: Listening on IP address *"... They're running FreeRADIUS, too. If they're following the GPL, we can list them on the web page as a "success", so people know the software works in commercial environments. If they're not following the GPL, we should send a nice letter to them, too. Alan DeKok.

4 4

RE: TinyPEAP
by Mitchell, Michael J 08 Jun '05

08 Jun '05

I'm not sure that "infected" is a good way to describe freeRADIUS code ;-) Its not my project, but I think it would be nice to give them a little more than a day to respond... > -----Original Message----- > From: freeradius-devel-bounces(a)lists.freeradius.org > [mailto:freeradius-devel-bounces@lists.freeradius.org] > Sent: Tuesday, 7 June 2005 12:37 PM > To: freeradius-devel > Subject: TinyPEAP > > I was going to post the following on the linksys tinypeap > forum. Comments? > And/or we could submit a slashdot story. > > ==== > Please don't use TinyPEAP. The authors have stolen code from > the FreeRADIUS project (not the legal definition of "steal" > since code isn't physical property, but theft all the same). > > TinyPEAP uses TLS (and possibly other) code from FreeRADIUS. > FreeRADIUS is licensed under the GPL. That means if you take > FreeRADIUS code and redistribute it, you must also distribute > your modifications to the code. Or if you incorporate > FreeRADIUS code into your own, you've "infected" your own > code and must distribute the source. > > Many FreeRADIUS developers have worked hard to create the EAP > functionality. Please don't step on their rights by using TinyPEAP. > > The TinyPEAP developers were contacted but did not respond. > Next will be legal action. > > Frank Cusack > FreeRADIUS developer > ==== > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/devel.html >

4 5

TinyPEAP
by Frank Cusack 07 Jun '05

07 Jun '05

I was going to post the following on the linksys tinypeap forum. Comments? And/or we could submit a slashdot story. ==== Please don't use TinyPEAP. The authors have stolen code from the FreeRADIUS project (not the legal definition of "steal" since code isn't physical property, but theft all the same). TinyPEAP uses TLS (and possibly other) code from FreeRADIUS. FreeRADIUS is licensed under the GPL. That means if you take FreeRADIUS code and redistribute it, you must also distribute your modifications to the code. Or if you incorporate FreeRADIUS code into your own, you've "infected" your own code and must distribute the source. Many FreeRADIUS developers have worked hard to create the EAP functionality. Please don't step on their rights by using TinyPEAP. The TinyPEAP developers were contacted but did not respond. Next will be legal action. Frank Cusack FreeRADIUS developer ====

3 2

RE: PAP failure
by Batta, Anurag 07 Jun '05

07 Jun '05

I have been running it in debug mode. I don't think it's the module itself. Here is what I see: Ready to process requests. rad_recv: Access-Request packet from host X.Y.73.124:32769, id=77, length=56 User-Name = "test" User-Password = "test" NAS-IP-Address = 255.255.255.255 NAS-Port = 1812 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall: group authorize returns noop for request 0 auth: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user auth: Failed to validate the user. Delaying request 0 for 1 seconds Finished request 0 -----Original Message----- From: freeradius-devel-bounces(a)lists.freeradius.org [mailto:freeradius-devel-bounces@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, June 07, 2005 12:55 PM To: FreeRadius developers mailing list Subject: Re: PAP failure "Batta, Anurag" <Anurag_Batta(a)usr.com> wrote: > Did anyone experience this while testing? I loaded PAP module and put > a user and pwd in config file. I get access reject in reply to radtest. Run the server in debugging mode to see why. If it's a problem in the PAP module, instrument the code to see what it's doing, and why. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. U. S. Robotics

2 1

crash of freeradius 1.0.2
by Schweizer Laurent 07 Jun '05

07 Jun '05

Hello, i use freeradius 1.0.2 with the jradius module and i have many crashes. Loaded symbols for /usr/local/lib/rlm_eap_mschapv2-1.0.2.so #0 0x40242ef1 in kill () from /lib/libc.so.6 (gdb) bt #0 0x40242ef1 in kill () from /lib/libc.so.6 #1 0x40081bb1 in pthread_kill () from /lib/libpthread.so.0 #2 0x40081f2b in raise () from /lib/libpthread.so.0 #3 0x40242b24 in raise () from /lib/libc.so.6 #4 0x402443fd in abort () from /lib/libc.so.6 #5 0x0804f5d2 in rad_assert_fail (file=0x806105f "request_list.c", line=470) at util.c:331 #6 0x08059c4f in rl_delete (request=0x815c3b8) at request_list.c:491 #7 0x0805a502 in refresh_request (request=0x815c3b8, data=0xbfffec40) at request_list.c:1048 #8 0x0805aaff in rl_clean_list (now=0) at request_list.c:1398 #9 0x0804d141 in main (argc=1, argv=0x0) at radiusd.c:1492 #0 0x40242ef1 in kill () from /lib/libc.so.6 (gdb) bt #0 0x40242ef1 in kill () from /lib/libc.so.6 #1 0x40081bb1 in pthread_kill () from /lib/libpthread.so.0 #2 0x40081f2b in raise () from /lib/libpthread.so.0 #3 0x40242b24 in raise () from /lib/libc.so.6 #4 0x402443fd in abort () from /lib/libc.so.6 #5 0x0804f5d2 in rad_assert_fail (file=0x806105f "request_list.c", line=1000) at util.c:331 #6 0x0805a489 in refresh_request (request=0x815b8a0, data=0xbfffec40) at request_list.c:1000 #7 0x0805a33e in rl_walk (walker=0x805a460 <refresh_request>, data=0xbfffec40) at request_list.c:895 #8 0x0805a96c in rl_clean_list (now=0) at request_list.c:1425 #9 0x0804d141 in main (argc=1, argv=0x0) at radiusd.c:1492 #0 0x40242ef1 in kill () from /lib/libc.so.6 (gdb) bt #0 0x40242ef1 in kill () from /lib/libc.so.6 #1 0x40081bb1 in pthread_kill () from /lib/libpthread.so.0 #2 0x40081f2b in raise () from /lib/libpthread.so.0 #3 0x40242b24 in raise () from /lib/libc.so.6 #4 0x402443fd in abort () from /lib/libc.so.6 #5 0x0804f5d2 in rad_assert_fail (file=0x806105f "request_list.c", line=1000) at util.c:331 #6 0x0805a489 in refresh_request (request=0x815a678, data=0xbfffec40) at request_list.c:1000 #7 0x0805a33e in rl_walk (walker=0x805a460 <refresh_request>, data=0xbfffec40) at request_list.c:895 #8 0x0805a96c in rl_clean_list (now=0) at request_list.c:1425 #9 0x0804d141 in main (argc=1, argv=0x0) at radiusd.c:1492 #0 0x40242ef1 in kill () from /lib/libc.so.6 #1 0x40081bb1 in pthread_kill () from /lib/libpthread.so.0 #2 0x40081f2b in raise () from /lib/libpthread.so.0 #3 0x40242b24 in raise () from /lib/libc.so.6 #4 0x402443fd in abort () from /lib/libc.so.6 #5 0x0804f5d2 in rad_assert_fail (file=0x806105f "request_list.c", line=1000) at util.c:331 #6 0x0805a489 in refresh_request (request=0x815b570, data=0xbfffec40) at request_list.c:1000 #7 0x0805a33e in rl_walk (walker=0x805a460 <refresh_request>, data=0xbfffec40) at request_list.c:895 #8 0x0805a96c in rl_clean_list (now=0) at request_list.c:1425 #9 0x0804d141 in main (argc=1, argv=0x0) at radiusd.c:1492 (gdb) #5 0x0804f5d2 in rad_assert_fail (file=0x806105f "request_list.c", line=470) at util.c:331 #6 0x08059c4f in rl_delete (request=0x815c3b8) at request_list.c:491 #7 0x0805a502 in refresh_request (request=0x815c3b8, data=0xbfffec40) at request_list.c:1048 #8 0x0805aaff in rl_clean_list (now=0) at request_list.c:1398 #9 0x0804d141 in main (argc=1, argv=0x0) at radiusd.c:1492

2 3

PAP failure
by Batta, Anurag 07 Jun '05

07 Jun '05

Did anyone experience this while testing? I loaded PAP module and put a user and pwd in config file. I get access reject in reply to radtest. Could not find any thread that explains it. Thanks, Anurag. This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. U. S. Robotics

2 1