Hi all,
I am running freeradius2.1.12, having recently upgraded from freeradius
1, where this worked perfectly.
I use LDAP authentication from my radius server for ADSL, 3g and wifi
users, each with their own realm set up. Now for support staff we have
another separate apn using a single user
Cooper, Tom wrote:
I am running freeradius2.1.12, having recently upgraded from freeradius
1, where this worked perfectly.
The server *did* change from version 1 to version 2. Did you copy the
version 1 configuration, or did you build a new one for version 2?
I use LDAP authentication
Nick Kalen wrote:
looking at the docs, it looks like it's not possible to try to
authenticate against a local LDAP server and in case it failes send it
to another radius server?
That won't work.
Maybe in 3.0.
Alan DeKok.
-
List info/subscribe/unsubscribe? See
Hello,
looking at the docs, it looks like it's not possible to try to
authenticate against a local LDAP server and in case it failes send it
to another radius server?
Can someone please prove me wrong?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Thomas A. Fine wrote:
One of the things I love on the Internet (and by love I mean hate) is
when someone asks a technical question, and they end up with a
condescending policy answer.
The answer I read includes a *technical* portion describing exactly
how to do what you want.
Another
Christ Schlacta li...@aarcane.org wrote:
Individual SSH keys are so 2010, you legacy SSHers need to get an SSH
CA setup so you can just sign all your keys and deploy a single master
certificate like the rest of us.
You can do that?
/me goes to investigate
Cheers
--
Alexander Clouter
Thomas A. Fine f...@head.cfa.harvard.edu wrote:
One of the things I love on the Internet (and by love I mean hate) is
when someone asks a technical question, and they end up with a
condescending policy answer.
Welcome to the Internet, the place where tongue-in-cheek evaporates...
The
Hi,
I thought this would be easy but now I'm wondering if it will be
possible at all. We are transitioning to a DMZ for all ssh logins.
During phase one, people will use a standard (but different than
internal) password which will be obtained either through LDAP or
the passwd module (we just
Hi,
I thought this would be easy but now I'm wondering if it will be
possible at all. We are transitioning to a DMZ for all ssh logins.
During phase one, people will use a standard (but different than
internal) password which will be obtained either through LDAP or
the passwd module (we just
On 2/16/11 5:36 PM, Gary Gatten wrote:
I don't understand the question 100%. If you want different users to test different methods (LDAP, OTP,
etc.) - that's fairly easy. If you want a given user Bob to test different methods concurrently,
that sounds tricky - and I'm not sure what you wish
Thomas A. Fine f...@head.cfa.harvard.edu wrote:
I thought this would be easy but now I'm wondering if it will be
possible at all. We are transitioning to a DMZ for all ssh logins.
During phase one, people will use a standard (but different than
internal) password which will be obtained
One of the things I love on the Internet (and by love I mean hate) is
when someone asks a technical question, and they end up with a
condescending policy answer.
The first thing anyone should know (but many don't) about security is
that everybody has different security needs, and their policy
On 2/16/2011 15:02, Alexander Clouter wrote:
Thomas A. Finef...@head.cfa.harvard.edu wrote:
I thought this would be easy but now I'm wondering if it will be
possible at all. We are transitioning to a DMZ for all ssh logins.
During phase one, people will use a standard (but different than
13 matches
Mail list logo
