Originally, I had tried using an internal CA to issue the cert, which worked
fine for the packetfence ssl site. However, after running into the radius
issue, i reissued the cert using instructions from various sites online
(self-issued), which comprised of:
cd /tmp
openssl req -new > packetfence.csr
openssl rsa -in privkey.pem -out server.key
openssl x509 -in packetfence.csr -out server.crt -req -signkey server.key -days
365
mv server.crt /usr/local/pf/conf/ssl/
mv server.key /usr/local/pf/conf/ssl/
The actual cert references the server netbios name as the actual web site.
I did not install freeradius2 or any other permutation. Am I possibly
modifying/verifying the wrong files? I'm simply following the guidelines in
the packetfence v3 guide.
This is on centos 6 64bit.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
