On 03/25/2011 12:12 AM, David Zych wrote: > I noticed today when using AuthBy RADIUS with Synchronous and Fork > that if the secrets don't match (resulting in "Bad authenticator > received in reply to ID 1. Reply is ignored"), this creates forked > processes that never terminate and have to be manually force-killed. > > From what I can tell, it appears that AuthRADIUS::handleReply removes > the timeout but does not set RadiusResult to tell Synchronous mode > that it's finished. Presumably it needs to do both of these things > or neither.
David, thanks for investigating and reporting this. The patch for this was commited recently and is available in the patch set for 4.7. Thanks! -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator