Re: (ASCEND) Radius authenication question

[maxed_out_user@hotmail.com]

Regardless if you want to send the RADIUS request either as a proxy
RADIUS request or a normal RADIUS request, the user's password will be
hidden in a one way MD5 hash so this will relatively be a safe thing to
do.  However, the User-Name will not be encrypted, so a potential hacker
will have one less thing to figure out if using a sniffer.  I'm not sure
if that's really big deal though.

The only other concern of mine is the reliability of the Internet.
Provided links don't go down very often, you're service will be
reliable, but if links do go down frequently, then you're deep in the
water since users will not be able to authenticate.

That's just my opinion.


Hi,

This may be a little off topic but we use radius (AAC) to authenicate
our Ascend Maxes and we would like add a remote pop that would require
us to authenicate over the internet. Are the shared secrets good enough
for passing this information or should we be looking at some type of VPN
connection to carry the authenication?

I know a lot of people out source dialup and use radius proxy
authenication... so my guess is that the shared secrets work well
enough.

Any thoughts? Pitfalls?

Randy Smith

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>