Hello Felipe -
On Sat, 01 Jul 2000, Felipe Salum wrote:
> Hi.
>
> I am authenticating my dial-up users in a Oracle Database. The users
> have encrypted passwords. So I use the line:
> AuthColumnDef 0, Encrypted-Password, check
>
> and not
>
> AuthColumnDef 0, User-Password, check.
>
> The pr
Hi.
I am authenticating my dial-up users in a Oracle Database. The users
have encrypted passwords. So I use the line:
AuthColumnDef 0, Encrypted-Password, check
and not
AuthColumnDef 0, User-Password, check.
The problem is that I need to use CHAP and I read in the Radiator
Reference Manual th
Hello Ray -
On Fri, 30 Jun 2000, Raymond Brighenti wrote:
> Hi,
>
> Just got Radiator running with MySQL, all seemed to be going alright until
> I notice that it was accepting any password given as long as a valid
> username was used.
>
> I've dropped it back to using the passwd file but I'm
Hello Dan -
We have discovered a problem with AuthAttrDef - thanks go to
Eric Kilfoil <[EMAIL PROTECTED]> for pointing it out and sending a patch.
Here is an extract from the patches area:
http://www.open.com.au/radiator/downloads/patches-2.16.1/patches.README
30/6/00 Fixed a problem with Au
I've checked Oracle PLSQL reference, DBD-Oracle manual.
The correct syntax to call Oracle stored procedure/function from a perl script is
to wrap it in BEGIN END; block then call prepare(), bind_param[_inout]() for IN and OUT
parameters if any, than execute().
To pass returned results (it can be O
Hi,
Just got Radiator running with MySQL, all seemed to be going alright until
I notice that it was accepting any password given as long as a valid
username was used.
I've dropped it back to using the passwd file but I'm bluffed as to what is
happening. Also I've noticed that nothing is getti
