Now that our dot1x and WLAN Radiator needs to check three different crls I've looked into a better solution for refreshing them. While reading Radius::TLS I've stumbled over the method reloadCrls which claims to reload the crl if the timestamp changes. Has this ever worked? In the contextInit method you've put a note # REVISIT: what if a CRL changes while we are running?
I'm trying to restart Radiator as rarely as possible to not terminate an ongoing EAP communication but the crls all have different expiration dates (two have a lifetime of a day, the third of a week which will probabliy also changed to a day or less). Best regards, Alex *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien Handelsgericht Wien, FN 79340b *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* Notice: This e-mail contains information that is confidential and may be privileged. If you are not the intended recipient, please notify the sender and then delete this e-mail immediately. *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"* _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator