sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-03-27 22:50:26 +03:00
Code

docs: Further discourage the use of the "event notification" options

Browse Source 
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14689

Signed-off-by: Andrew Bartlett <abartlet@samba.org>
Reviewed-by: Andreas Schneider <asn@samba.org>
This commit is contained in:
Andrew Bartlett 2021-04-15 14:45:07 +12:00
parent a778a3a642
commit 364b8be981
4 changed files with 39 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
docs-xml/smbdotconf/logon/autheventnotification.xml
View File

@ -10,16 +10,19 @@
registering as the service
<filename moreinfo="none">auth_event</filename>.</para>
<para>This should be considered a developer option (it assists
in the Samba testsuite) rather than a facility for external
auditing, as message delivery is not guaranteed (a feature
that the testsuite works around). Additionally Samba must be
compiled with the jansson support for this option to be
effective.</para>
<para>This is <emphasis>not</emphasis> needed for the audit
logging described in <smbconfoption name="log level"/>.</para>
<para>Instead, this should instead be considered a developer
option (it assists in the Samba testsuite) rather than a
facility for external auditing, as message delivery is not
guaranteed (a feature that the testsuite works around).</para>
<para>The authentication events are also logged via the normal
logging methods when the <smbconfoption name="log level"/> is
set appropriately.</para>
set appropriately, say to
<command moreinfo="none">auth_json_audit:3</command>.</para>
</description>
<value type="default">no</value>

14
docs-xml/smbdotconf/misc/dsdbeventnotification.xml
View File

@ -10,14 +10,18 @@
registering as the service
<filename moreinfo="none">dsdb_event</filename>.</para>
<para>This should be considered a developer option (it assists
in the Samba testsuite) rather than a facility for external
auditing, as message delivery is not guaranteed (a feature
that the testsuite works around).</para>
<para>This is <emphasis>not</emphasis> needed for the audit
logging described in <smbconfoption name="log level"/>.</para>
<para>Instead, this should instead be considered a developer
option (it assists in the Samba testsuite) rather than a
facility for external auditing, as message delivery is not
guaranteed (a feature that the testsuite works around).</para>
<para>The Samba database events are also logged via the normal
logging methods when the <smbconfoption name="log level"/> is
set appropriately.</para>
set appropriately, say to
<command moreinfo="none">dsdb_json_audit:5</command>.</para>
</description>

16
docs-xml/smbdotconf/misc/dsdbgroupchangenotification.xml
View File

@ -10,14 +10,18 @@
registering as the service
<filename moreinfo="none">dsdb_group_event</filename>.</para>
<para>This should be considered a developer option (it assists
in the Samba testsuite) rather than a facility for external
auditing, as message delivery is not guaranteed (a feature
that the testsuite works around).</para>
<para>This is <emphasis>not</emphasis> needed for the audit
logging described in <smbconfoption name="log level"/>.</para>
<para>The group events are also logged via the normal
<para>Instead, this should instead be considered a developer
option (it assists in the Samba testsuite) rather than a
facility for external auditing, as message delivery is not
guaranteed (a feature that the testsuite works around).</para>
<para>The Samba database events are also logged via the normal
logging methods when the <smbconfoption name="log level"/> is
set appropriately.</para>
set appropriately, say to
<command moreinfo="none">dsdb_group_json_audit:5</command>.</para>
</description>

16
docs-xml/smbdotconf/misc/dsdbpasswordeventnotification.xml
View File

@ -10,14 +10,18 @@
events by registering as the service
<filename moreinfo="none">password_event</filename>.</para>
<para>This should be considered a developer option (it assists
in the Samba testsuite) rather than a facility for external
auditing, as message delivery is not guaranteed (a feature
that the testsuite works around).</para>
<para>This is <emphasis>not</emphasis> needed for the audit
logging described in <smbconfoption name="log level"/>.</para>
<para>The password events are also logged via the normal
<para>Instead, this should instead be considered a developer
option (it assists in the Samba testsuite) rather than a
facility for external auditing, as message delivery is not
guaranteed (a feature that the testsuite works around).</para>
<para>The Samba database events are also logged via the normal
logging methods when the <smbconfoption name="log level"/> is
set appropriately.</para>
set appropriately, say to
<command moreinfo="none">dsdb_password_json_audit:5</command>.</para>
</description>