<html><div style='background-color:'><DIV class=RTE>
<P>But, this version does not still support that the existed realms in 'proxy.conf' file was in a DB.</P>
<P>It is useful for me, because I have a lot of roaming partners.<BR></P></DIV>
<DIV></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif">
<HR color=#a0c6e5 SIZE=1>
<DIV></DIV>From: <I>Alan DeKok <aland@deployingradius.com></I><BR>Reply-To: <I>FreeRadius users mailing list <freeradius-users@lists.freeradius.org></I><BR>To: <I>FreeRadius users mailing list <freeradius-users@lists.freeradius.org></I><BR>Subject: <I>FreeRADIUS 1.1.4 has been released</I><BR>Date: <I>Thu, 04 Jan 2007 16:39:39 -0800</I><BR>> Version 1.1.4 has been released, with a few notable improvements.<BR>><BR>> The server has been updated to be compatible with Microsoft Vista<BR>>clients for 802.1x. This feature should prove to be of significant<BR>>interest in many deployments.<BR>><BR>> The "rlm_pap" module has been updated, which should make many<BR>>configurations much simpler. A new attribute has been added,
called<BR>>Cleartext-Password. This attribute should be used to hold the "known<BR>>good" password, where configurations previously had used the<BR>>"User-Password" attribute. Historically, User-Password has been used<BR>>both as the users password in the Access-Request packet, and also for<BR>>the "known good" password in the servers configuration ("users" file or<BR>>SQL database). Having two meanings for one attribute is problematic, so<BR>>we have modified the server to separate the meanings of the two attributes.<BR>><BR>> Existing configurations will not be affected by this change. However,<BR>>we recommend that everyone reads the "README" and "man rlm_pap"<BR>>documentation once the server is installed.<BR>><BR>> The ChangeLog is included below:<BR>><BR>>Feature
improvements<BR>> * Major enhancements to rlm_pap, that make "encryption_scheme"<BR>> a think of the past. See "man rlm_pap" for details.<BR>> * Added SSL_OP_DONT_INSERT_EMPTY_FRAGMENTS flag to use<BR>> work-arounds that enable Windows Vista clients to work.<BR>> * Added preliminary code to support Firebird. (closes: #378)<BR>> Use at your own risk!<BR>> * Send MS-CHAP2-Success, which makes EAP-TTLS/MSCHAP work on more<BR>> platforms. (closes: #402)<BR>> * Add a new "reply-name" directive in rlm_sqlcounter to define the<BR>> name of the reply attribute. (closes: #403)<BR>> * Added more dictionaries and attributes (closes: #408, among
others)<BR>> * Print ntlm_auth failure reason in Module-Failure-Message<BR>> (closes: #398)<BR>> * radsqlrelay is able to get the DB password from a file instead<BR>> of command line. (closes: #395)<BR>><BR>>Bug fixes<BR>> * Fix a parse error in the digest module, where malformed<BR>> digest requests would result in the user being accepted. Oops...<BR>> * VALUEs can only be defined for 'integer', to catch mistakes<BR>> with setting VALUEs for type 'string'.<BR>> * Better parsing of VALUE names, so that values starting with<BR>> a digit work correctly.<BR>> * Check return from malloc (closes: #407)<BR>> * Fix a double free() in
rlm_eap_tls.c (closes: #404)<BR>> * Check return code of malloc() during initialization. (closes: #407)<BR>> * Fix a corner case where the proxy port isn't set either in<BR>> radiusd.conf or in proxy.conf.<BR>><BR>><BR>>NOT in this release<BR>> * Threading issues with SSL and EAP on some systems.<BR>> * MS-CHAP UTF-8 fixes.<BR>><BR>> We expect both those fixes to be in a future release.<BR>><BR>> Alan DeKok.<BR>> FreeRADIUS Project Leader<BR>><BR>><BR>>--<BR>> Alan DeKok.<BR>>--<BR>> http://deployingradius.com - The web site of the book<BR>> http://deployingradius.com/blog/ - The blog<BR>>-<BR>>List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html<BR></FONT></BLOCKQUOTE></div><br clear=all><hr>Excursiones y escapadas a sitios mágicos. <a href="http://g.msn.com/8HMAESES/2734??PS=47575" target="_top">No te lo pierdas en MSN Entretenimiento</a> </html>