Hello,
Thanks for your replies. I've not changed permissions on these files
since the 2.03 update, here's what they are:
total 16
-rw-r--r-- 1 root wheel 4357 May 25 2007 bacula.example.crt
-rw-r----- 1 root wheel 887 May 25 2007 bacula.example.key
-rw-r--r-- 1 root wheel 1659 May 25 2007 ca-cert.pem
-rw-r--r-- 1 root wheel 1720 May 27 2007 master.crt
-rw-r--r-- 1 root wheel 3415 May 27 2007 zeus-fd.pem
I tried starting via the commandline using the bacula_flags and -d option,
got the same msg.
I checked the private key which seems to be the cause of this and the
permissions i remember setting because i read that private keys should not
be world readable, the file and storage daemons are utilizing the same flags
and do not have issues accessing it.
If the permissions and memberships are wrong or insecure let me know
what they should be, but as i said in 2.03 the same configs gave me no
issue.
Thanks.
Dave.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
