Jeffrey Sewell wrote:
Thank you for your reply.
We are (with the exception of some prototype tests) going to be
completely EAP-TLS.
Your answer brings me back to my original issue--the CA_path does not
exist in the eap.conf file. If I add it, it doesn't seem to work (on
1.1.4).
Hm, here
Thank you for your reply.
We are (with the exception of some prototype tests) going to be
completely EAP-TLS.
Your answer brings me back to my original issue--the CA_path does not
exist in the eap.conf file. If I add it, it doesn't seem to work (on
1.1.4).
Just adding additional certs to the
Jeffrey Sewell wrote:
Than you.
So if I understand this correctly, radiusd is not looking for a
directory with checksum'd certificates, just one file with all the
certficates in it?
Both is possible.
CA_path = ${raddbdir}/certs/trustedCAs/
with c_rehash generated fingerprint symlinks for
Jeffrey Sewell wrote:
In the eap.conf, tls section, the comments say to use the 'CA_path'
variable in the radiusd.conf file to indicate where the trusted CA
chain will reside. However, this variable isn't in the tls section of
the radiusd.conf file (it is in the LDAP section, but I'm pretty
advice
in mind.
JS
On 1/22/07, Reimer Karlsen-Masur, DFN-CERT [EMAIL PROTECTED] wrote:
Jeffrey Sewell wrote:
In the eap.conf, tls section, the comments say to use the 'CA_path'
variable in the radiusd.conf file to indicate where the trusted CA
chain will reside. However, this variable isn't
In the eap.conf, tls section, the comments say to use the 'CA_path'
variable in the radiusd.conf file to indicate where the trusted CA
chain will reside. However, this variable isn't in the tls section of
the radiusd.conf file (it is in the LDAP section, but I'm pretty sure that
won't help me
6 matches
Mail list logo
