Re: ver 2.5 RE: blank user

iml@interconnect.net
Mon, 13 Apr 1998 17:16:28 -0500

Hmmm it won't be charged for if you are paying a yearly update cost as
listed on their webpage. At least I hope not or I will stop paying
that..heheh.

On Thu, 09 Apr 1998 15:34:41 -0500, John Lange wrote:

>HI
>
>I have seen Dale respond several times to this question. When =
available,
>2.5 will be a free upgrade.
>
>Should there be a version 3, It will be charged for.
>
>JOhn :}
>
>At 02:15 PM 4/9/98 -0600, you wrote:
>>My question is, will I have to pay for 2.5? The 2.5 that corrects this
>>problem and most likely a lot of others?
>>I am a registered user for 2.x but will I have to pay again to get a =
good
>>working version ?
>>
>>----------
>>Franco Nogarin
>>Webmaster - The Aurora Network
>>webmaster@auroranet.nt.ca
>>tel: (867) 872-5123
>>
>>> -----Original Message-----
>>> From: Dale E. Reed Jr. [mailto:daler@iea-software.com]
>>> Sent: Wednesday, April 08, 1998 1:22 AM
>>> To: emerald@emerald.iea.com
>>> Subject: Re: blank user
>>>
>>>
>>> Robert H. Clugston wrote:
>>> >
>>> > I keep getting a blank user in Emerald. It is basically
>>> a user without a
>>> > username. I also see this on my PM3 with the show sessions.
>>> Yesterday this
>>> > happened twice. Any ideas?
>>>
>>> There is an issue with Emerald 2.2 and lower that RadiusNT 2.5 and
>>> higher patches. When SQL Server stores a varchar of "" (blank zero
>>> length string, which is NOT the same thing as a NULL) it changes
>>> it to a " " (string of length one containing a single space). =
Emerald
>>> 2.2 and lower store a blank login, shell, or Email as "" which gets
>>> changed to a single space.
>>>
>>> Now, since RadiusNT allows multiple users to have the same login,
>>> shell, or email (note Emerald doesn't allow this at the application
>>> level, but its possible at the database level) it will go through
>>> each record with a match until it finds a matching password. This
>>> is were the infamous scrolling userlist comes into affect.
>>>
>>> There are two things to do to correct this problem. First, is
>>> to run a script to change all the " " login, shell, and email
>>> fields to NULL. This is part of the rad25_up.sql script. The
>>> second is to use RadiusNT 2.5 with the trimname option, which
>>> will trim spaces and other things out, preventing this issue before
>>> it gets to the database. Emerald 2.5 and higher will stores these
>>> fields as NULL rather than "" to prevent this problem in the
>>> future. (I know, don't shoot me or complain because I mentioned
>>> it).
>>>
>>> --
>>> Dale E. Reed Jr. (daler@iea-software.com)
>>> _________________________________________________________________
>>> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
>>> Internet Solutions for Today | http://www.iea-software.com
>>>
>>> ----------------------------------------------------------
>>> Emerald Mailing List listserver@emerald.iea.com
>>>
>>
>>
>> ----------------------------------------------------------
>> Emerald Mailing List listserver@emerald.iea.com
>>
>>
>>
>
>John C. Lange, Sr. PALACE dot NET, INC.
>microjl@palacenet.net MICRO-TECH Computers, Inc.
>608.742.1601 & 6980 2800 New Pinery Road
>http://www.palacenet.net/ Portage, WI 53901
>Visit our online store @ http://www.microt.com/
>Authorized iPSwitch WebVar @ http://www.microt.com/iPSwitch/index.html
>
> --- __o
> --- _-\<,_ Fastest Service in Town
> --- (_)/ (_)
>
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com