[RADIATOR] [Radiator] Problem with SHA hash

Hello, I'm storing in a SQL database the user's password in plain text format. I've tried to switch to hashed password, which is of course a more secure approach. I' ve some trouble with the SHA hash computation, because the one that Radiator computes is different from the mine. In the user's manua

Re: [RADIATOR] [Radiator] Problem with SHA hash

Thanks very much for your help! Alberto 2011/12/21 Heikki Vatiainen > On 12/21/2011 09:25 PM, Dick Visser wrote: > > On 21 December 2011 15:16, Alby wrote: > > >> I'm storing in a SQL database the user's password in plain text format. > I've > >>

[RADIATOR] Limit users' request rate

Hi all, does anyone know if Radiator has an easy way to limit the users' request rate? I would like to make users that fail the authentication for more than 10 times consequently to wait for some minutes before being able to authenticate again in the system. This could be useful to keep away people

Re: [RADIATOR] Limit users' request rate

gt; regards > > Hugh > > > On 14 Feb 2012, at 20:24, Alby wrote: > > > Hi all, > > does anyone know if Radiator has an easy way to limit the users' request > rate? I would like to make users that fail the authentication for more than > 10 times consequently to

[RADIATOR] Radiator's database handle

Hi all, I'm using radiator with a SQL database that stores the users' data. I've also a PostAuthHook that writes some data on the SQL database. Up to now my Hook connects to the database, writes the data and then disconnects. I suspect that connecting and disconnecting each time I write to the data

Re: [RADIATOR] Radiator's database handle

ant to write something to a table for example ever time a user > authenticates, use an , a SuccessQuery, and "LogSuccess > 1". > if you want to write something when stop packets come in, use SQL>, with "HandleAcctStatusTypes Stop", and a AcctSQLStatement. > &g

Re: [RADIATOR] Radiator's database handle

you may be trying to do something that is pretty complex. >> maybe you should be thinking about creating your own custom Auth Clause. >> section 17.0 in the Radiator manual. For example, i've created my own Auth >> Clause (AuthUNIX_UID) to support the UID value from unix password

[RADIATOR] Custom Reply-Message for each AuthSQL inside REALM

Hello everyone, I am using Radiator in a Telecommunication group. I have only one REALM, with 3 AuthSQL statements inside (the policy used is ContinueWhileIgnore). The first one checks that the user is allowed to occupy another port in the system. If the check goes OK, then the next AuthSQL stateme

Re: [RADIATOR] Custom Reply-Message for each AuthSQL inside REALM

... Thanks again, Alberto 2012/7/4 Heikki Vatiainen > On 07/04/2012 04:32 PM, Alby wrote: > > Hello Alberto, > > > I am using Radiator in a Telecommunication group. I have only one REALM, > > with 3 AuthSQL statements inside (the policy used is > > ContinueWhileIgno

[RADIATOR] AM or PM strings into accounting file name

Dear all, My need is to add the strings "AM" or "PM" to the Radiator's accounting file name because I need to generate two accounting files at day, one that contains the accounting entry from 00:00 to 12:00 and one from 12:00 to 00:00. In my opinion the best way to do this is to include the string

Re: [RADIATOR] AM or PM strings into accounting file name

Ciao Hugh! :) Thanks for your prompt response! I will try your solution asap! Grazie! Alberto Albesiano 2013/2/12 Hugh Irvine > > Ciao Alby - > > You can either use the %{SQL:….} special character if you are using an SQL > database, or write a little hook to generate a pseudo-a