On 24/02/12 10:33 AM, Derek Wuelfrath wrote: > 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.
FYI I just added the following note to UPGRADE (which is the one linked from our website) to avoid further confusion: - Scan configuration changes - scan.ssl no longer exists, get rid of it, it never really did anything since 1.8.3. - scan.nessusclient_file was renamed scan.nessus_clientfile - scan.nessusclient_policy was renamed scan.nessus_clientpolicy - scan.port was renamed scan.nessus_port Thanks for letting us know Dan! -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
