Re: CallsOnline fix

Phil Heller ( (no email) )
Wed, 9 Apr 1997 16:31:32 -0400

Or maybe implement a severe authentication delay after x authentications.
You could also use some wacked out registry keys to prevent 'at' from
executing radius.exe.

Just some thoughts. Maybe you could make the unregistered version only
capable of attaching to MS Access ODBC sources. Then the severe delays
will be inherent.

-Phil

---------------------------------------------------------------------------
Phillip A. Heller pheller@csonline.net
Internet Engineer http://www.csonline.net
CSOnline Internet Services (814) 898-6524
---------------------------------------------------------------------------
...I think what I write, but my employer might not...

----------
> From: Dale E. Reed Jr. <daler@iea.com>
> To: RadiusNT@emerald.iea.com
> Subject: Re: CallsOnline fix
> Date: Wednesday, April 09, 1997 4:01 PM
>
> Phil Heller wrote:
> >
> > How about have it run for X authentications?
>
> X authentications might not be that bad. I don't really like X time,
> though.
> When I was first testing a DNS server (I think metainfo's), where it
> runs
> for 24 hours, I created an AT that would stop the service at 12:00 and
> restart
> it at 12:05. The time frame was perfect and it ran without a hitch for
> several
> months before we dumped it.
>
> Processes that run as a service for a set amount of time are easy to get
> around using this tact. :(
>
> --
> Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>