On 14/01/2013 12:29, David Ceresuela wrote:
I've just installed cluebringer-v2.1.x-201211111115.tar.gz <http://devlabs.linuxassist.net/attachments/download/256/cluebringer-v2.1.x-201211111115.tar.gz> in my debian system an although it seems to be working alright I've some suggestions: cbpolicyd looks for files in /usr/local/lib/cbpolicyd-2.1/ and has its configuration in /etc/cbpolicyd/cluebringer.conf cbpadmin looks for files in /usr/local/lib/policyd-2.1/ and has its configuration in /etc/cluebringer.conf This means that you have to duplicate your configuration if you want to use both cbpolicyd and cbpadmin.
Fix should be committed today.
The INSTALL document only shows the steps needed to copy files into /usr/local/lib/policyd-2.1, but the perl code (cbpolicyd) looks for files in /usr/local/lib/cbpolicyd-2.1 so I do not know which one is the right one.
Fix should be committed today.
I've seen there is a debian folder, but how I have to use the scripts inside that folder is something that escapes me. Are they supposed to be used instead the steps specified in the INSTALL document or are they supposed to be used after? I guess it is after, because I do not see the database configuration. If you could expand this a little bit more it would be great.
The debian/ folder is Debian specific, its used in the same manner as the .spec file for building the .deb package.
The last suggestion is to change the behavior of the webui to make the options non-disabled by default, but I do not know if there is a special reason to do it that way.
On large production systems you do not want a policy to be immediately active when adding it, thats why they are added as disabled first. So they can be fully setup before being enabled.
Hope you find this information useful.
Thanks for the feedback :) -N
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Users mailing list [email protected] http://lists.policyd.org/mailman/listinfo/users_lists.policyd.org
