Dan,
As of PacketFence 3.2, these configuration parameters are no longer
valid. This is why you were getting an error and this is also why they
were no longer in the conf/documentation.conf.
We add a point in the UPGRADE document but it was not covering all of
the changes for this modification.
Please see inline for how to make the correct modifications
Also, are you using any kind of conformity scanning in your environment?
If not, you can easily get rid of these.
[scan.ssl]
type=text
description=<<EOT
Use SSL.
EOT
scan.ssl is no longer used. You can remove it from your configuration file.
[scan.port]
type=text
description=<<EOT
Port to listen on.
EOT
Due to the new OpenVAS implementation, we deprecated scan.port and
introduced scan.nessus_port -OR- scan.openvas_port
[scan.nessusclient_file]
type=text
description=<<EOT
file to use.
EOT
[scan.nessusclient_policy]
type=text
description=<<EOT
policy to use.
EOT
In a naming convention matter, we renamed those two to
scan.nessus_clientfile and scan.nessus_clientpolicy
As I stated previously, if you are not using Nessus or OpenVAS in
conjunction with your PacketFence installation, you can easily get rid
of these configuration parameters in your pf.conf file.
Thanks!
--
Derek Wuelfrath
[email protected] <mailto:[email protected]> :: +1.514.447.4918
x110 :: www.inverse.ca <http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (www.sogo.nu <http://www.sogo.nu>)
and PacketFence (www.packetfence.org <http://www.packetfence.org>)
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Packetfence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
