Hi Alan,
Quoting Alan DeKok [EMAIL PROTECTED]:
Why? What would it gain us?
it would help people keeping track of the development without having the hassle
of doing a cvs co everytime.
Furthermore, if something is being discussed on this list that refers to a
funtion or file that has not yet
David,
read the error messages. look likes u are missing some of the
files..eg. newcert..pem, tranda1.p12...
where do your find Raymond Mckay's file?
There is another EAP/TLS howto, http://www.freeradius.org/doc/EAPTLS.pdf
Augustine
David Tran wrote:
To All,
I've followed Raymond Mckay
Hi!
Accordingly to 'doc/Simultaneous-Use' this feature works in this way:
if someone tries to ask for authentication, radiusd first search
radutmp file (or 'sql') and (only) if there is an open session for that
user server uses checkrad script to query NAS. Record in radutmp
appears only after
Hello
I am setting up a FreeRadius server (currently installed snapshot from
October 30, 2002). I would be grateful if someone could assist with a means
to do the following (sorry for the long-ish post):
The Radius server would be used to authenticate administrators (of the
Radius server itself
Paul Hampson [EMAIL PROTECTED] wrote:
Why? What would it gain us?
The ability to go back and see when a markedly broken problem
(such as that kill(-1) thing from last week) was introduced
and what the _intention_ was.
http://www.freeradius.org/cvs-log/
Alan DeKok.
-
List
[EMAIL PROTECTED] wrote:
Why? What would it gain us?
it would help people keeping track of the development without having the hassle
of doing a cvs co everytime.
http://www.freeradius.org/cvs-log/
The daily changes to CVS are mailed to the freeradius-devel list,
and are archived on
[EMAIL PROTECTED] wrote:
The 'callback' phase takes some time and at this point there is no
radutmp record yet (in contrast at NAS there is such record). Imagine
that during 'callback' someone another tries to login with the same
account. So radiusd will not check NAS for twice login and will
Tarun Bhushan [EMAIL PROTECTED] wrote:
The question is - how do I prevent a successful user login from being
misused to make attempts to access the firewall administration interface?
The answer is you either distinguish users by IP address of the
RADIUS client, or by something in the RADIUS
Yes... this is what section 5 of the Simultaneous-Use document
says. I don't understand why you're telling us what we already know.
It would have been sufficient to simply reference the document.
Yes...my post was _only_ (another) real-world example about what
section 5 says. Do you think
Hi Artur
Artur Hecker wrote:
hi
Yes, the EAP document with the FreeRADIUS 0.7 tar ball indicates that
OpenSSL 0.9.6b or later (for example, 0.9.6c - 0.9.6g) should work.
Others were having problems with that release, so I tried it, verified
that it didn't work, tried to find out why it
[EMAIL PROTECTED] wrote:
Yes...my post was _only_ (another) real-world example about what
section 5 says. Do you think that if it is not interesting to 'us'
it is not interesting at all?
I'm not sure what you mean.
For one, development questions should be discussed on the
freeradius-devel
11 matches
Mail list logo
