Re: [Bacula-users] Bacula daemon message- where did it come from?
2015-08-24 09:53:56
Apologies for the late response to this thread. Michael is correct in that these daemon messages are Bacula created and not delivered when created. Not only the example that he provided, but when an attempt to connect to the director from an unknown
and invalid client will generate these messages. They only appear in the bacula log and the mail log when the director is shutdown, not when the incident occurs. I consider this a bug in Bacula. Not only a bug, but a security bug because the delay in reporting
prevents responsive action if required. I have checked my messages and traced them to our security team probing our systems for security holes. I just don't see this from Bacula until the next director shutdown. Where Bacula keeps the messages until then,
I do not know.
Patti Clark
Linux System Administrator
R&D Systems Support Oak Ridge National Laboratory
This message is for the named person(s) use only. It may contain confidential proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete
it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Mocho Trading LLC
reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any
such entity.
|
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|