- Freeradius-Devel - lists.freeradius.org

Automatic report from sources (radiusd) between 17.06.2005 - 18.06.2005 GMT
by Automatic cvs log generator 18 Jun '05

18 Jun '05

CVS log entries from 17.06.2005 (Fri) 16:59:20 - 18.06.2005 (Sat) 08:00:01 GMT ===================================================== Summary by authors ===================================================== Author: aland File: radiusd/src/lib/filters.c; Revisions: 1.40 ===================================================== Log entries ===================================================== Description: Make parser more forgiving. Patch from Wolfgang Hottgenroth, to close bug #228 Modified files: File: radiusd/src/lib/filters.c; Revision: 1.40; Date: 2005/06/18 01:24:11; Author: aland; Lines: (+41 -57) ===================================================== Summary of modified files ===================================================== File: radiusd/src/lib/filters.c Revisions: 1.40 Authors: aland (+41 -57) -- Automatic cron job from /web/pages/us.freeradius.org/bin/new_makelog.pl

1 0

Question on PEAP(EAP-GTC)
by Pon Chew Soon 17 Jun '05

17 Jun '05

Hi. Anyone ever did implementation successfully using the Cisco Aironet PEAP(EAP-GTC) to talk to FreeRadius? Can shared the configuration steps? thanks

1 0

rlm_python return tuple
by Schweizer Laurent 14 Jun '05

14 Jun '05

Hello, I try to use the rlm_phyton module and I have a little error with the return. When I authorise a request I do (from the prepaid.py example with a little modification): return (radiusd.RLM_MODULE_UPDATED,(('h323-credit-amount','h323-credit-amount='+ time+''),),(('Auth-Type', 'python'),)) and I have a FAILED error. authorize: h323-credit-amount = h323-credit-amount=60 authorize: s1, s2 OK authorize: Auth-Type = python authorize: s1, s2 FAILED rad_recv: Access-Request packet from host 193.x.x.x:1645, id=68, length=410 Sending Access-Reject of id 68 to 193.x.x.x:1645 h323-credit-amount = "h323-credit-amount=60\n" I have tried to remove the second tuple but in this case I have this error: tuple must be (return, replyTuple, configTuple) what is the configTuple ? Thanks for help Laurent

1 0

Manpage submission
by Shawn K. O'Shea 13 Jun '05

13 Jun '05

I've been working a lot on eap stuff lately and had considered writing manpages for the various rlm_eap submodules. Since I've never written a manpage before, I decided to tackle something "smaller" first. I wrote the following man page for clients.conf(5) Please let me know if this kind of submission is welcome, and make any corrections as deemed necessary. Manpage source: http://go.airpathwireless.com/man/clients.conf.5 Man2htmlized version: http://go.airpathwireless.com/man/clients.conf.5.html Inline man source ----------------- .TH clients.conf 5 "13 June 2005" "" "FreeRADIUS client configuration" .SH NAME clients.conf \- FreeRADIUS client configuration .SH DESCRIPTION The .I clients.conf file contains definitions of RADIUS clients. .PP The information in this file overrides any information provided in the deprecated .BR clients (5) and .BR naslist (5) files. .PP The file format is the same as that used for .I radiusd.conf. See .BR radiusd.conf (5) for more details. .PP Each RADIUS client entry has the following basic form: .IP .nf client <hostname|ip-address|ip-block> { <attribute> = <value> } .fi .LP ip-block is used to specify a network of clients. Networks are specified in CIDR notation. The best match (smallest possible network) will be chosen. .SH ATTRIBUTES The attributes that can appear in a .B client section are listed below. Required attributes are labelled as such. All other attributes are optional. .PP .TP 0.5i .B secret [Required] The RADIUS shared secret used for communication between the client/NAS and the RADIUS server. .TP 0.5i .B shortname [Required] A short alias that can be used in place of the IP address or fully qualified hostname provided in the first line of the section. .TP 0.5i .B nastype The nastype attribute is used to tell the .BR checkrad.pl script which NAS-specific method it should use when checking simultaneous use. The following values are currently recognized: .nf cisco computone livingston max40xx multitech netserver pathras patton portslave tc usrhiper other .fi .TP 0.5i .B login Reserved for future use. .TP 0.5i .B password Reserved for future use. .SH EXAMPLES .IP .nf client 127.0.0.1 { secret = testing123 shortname = localhost nastype = other } .fi .LP This adds a client for the loopback address. This is useful in testing the server locally, for example with .BR radclient (1). .IP .nf client 192.168.0.0/24 { secret = testing123-1 shortname = private-network-1 } .fi .LP This entry represents any client from the 192.168.0.0/24 network. .SH FILES .I /etc/raddb/clients.conf .I /etc/raddb/radiusd.conf .SH "SEE ALSO" .BR radiusd (8), .BR radiusd.conf (5), .BR clients (5), .BR naslist (5) .SH AUTHOR This manual page was authored by Shawn K. O'Shea <shawn(a)eth0.net>. FreeRADIUS is authored by the FreeRADIUS team. http://freeradius.org/ -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.

2 1

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