~ubuntu-branches/ubuntu/maverick/samba/maverick-security

« back to all changes in this revision

Viewing changes to docs/htmldocs/manpages/eventlogadm.8.html

  • Committer: Bazaar Package Importer
  • Author(s): Chuck Short
  • Date: 2010-01-29 06:16:15 UTC
  • mfrom: (0.27.9 upstream) (0.34.4 squeeze)
  • Revision ID: james.westby@ubuntu.com-20100129061615-37hs6xqpsdhjq3ld
Tags: 2:3.4.5~dfsg-1ubuntu1
* Merge from debian testing.  Remaining changes:
  + debian/patches/VERSION.patch:
    - set SAMBA_VERSION_SUFFIX to Ubuntu.
  + debian/smb.conf:
    - Add "(Samba, Ubuntu)" to server string.
    - Comment out the default [homes] share, and add a comment about "valid users = %s"
      to show users how to restrict access to \\server\username to only username.
    - Set 'usershare allow guests', so that usershare admins are allowed to create
      public shares in additon to authenticated ones.
    - add map to guest = Bad user, maps bad username to gues access.
  + debian/samba-common.conf:
    - Do not change priority to high if dhclient3 is installed.
    - Use priority medium instead of high for the workgroup question.
  + debian/mksambapasswd.awk:
    - Do not add user with UID less than 1000 to smbpasswd.
  + debian/control: 
    - Make libswbclient0 replace/conflict with hardy's likewise-open.
    - Don't build against ctdb, since its not in main yet.
  + debian/rules:
    - Enable "native" PIE hardening.
    - Add BIND_NOW to maximize benefit of RELRO hardening.
  + Add ufw integration:
    - Created debian/samba.ufw.profile.
    - debian/rules, debian/samba.dirs, debian/samba.files: install
  + Add apoort hook:
    - Created debian/source_samba.py.
    - debian/rules, debian/samba.dirs, debian/samba-common-bin.files: install
  + debian/rules, debian/samba.if-up: allow "NetworkManager" as a recognized address
    family... it's obviously /not/ an address family, but it's what gets
    sent when using NM, so we'll cope for now.  (LP: #462169). Taken from karmic-proposed.
  + debian/control: Recommend keyutils for smbfs (LP: #493565)
  + Dropped patches:
    - debian/patches/security-CVE-2009-3297.patch: No longer needed
    - debian/patches/fix-too-many-open-files.patch: No longer needed

Show diffs side-by-side

added added

removed removed

Lines of Context:
1
 
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>eventlogadm</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="eventlogadm.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>eventlogadm &#8212; push records into the Samba event log store</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">eventlogadm</code> [<code class="option">-d</code>] [<code class="option">-h</code>]  <code class="option">-o</code>
 
1
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>eventlogadm</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="eventlogadm"><a name="eventlogadm.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>eventlogadm &#8212; push records into the Samba event log store</p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">eventlogadm</code> [<code class="option">-d</code>] [<code class="option">-h</code>]  <code class="option">-o</code>
2
2
                <code class="literal">addsource</code>
3
3
                <em class="replaceable"><code>EVENTLOG</code></em>
4
4
                <em class="replaceable"><code>SOURCENAME</code></em>
10
10
                <code class="literal">dump</code>
11
11
                <em class="replaceable"><code>EVENTLOG</code></em>
12
12
                <em class="replaceable"><code>RECORD_NUMBER</code></em>
13
 
                 </p></div></div><div class="refsect1" lang="en"><a name="id2483560"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">eventlogadm</code> is a filter that accepts
 
13
                 </p></div></div><div class="refsect1" title="DESCRIPTION"><a name="id2489536"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.1.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(1)</span></a> suite.</p><p><code class="literal">eventlogadm</code> is a filter that accepts
14
14
        formatted event log records on standard input and writes them
15
15
        to the Samba event log store. Windows client can then manipulate
16
 
        these record using the usual administration tools.</p></div><div class="refsect1" lang="en"><a name="id2483589"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term"><code class="option">-d</code></span></dt><dd><p>
 
16
        these record using the usual administration tools.</p></div><div class="refsect1" title="OPTIONS"><a name="id2489566"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term"><code class="option">-d</code></span></dt><dd><p>
17
17
                The <code class="literal">-d</code> option causes <code class="literal">eventlogadm</code> to emit debugging
18
18
                information.
19
19
                </p></dd><dt><span class="term">
44
44
                output on screen.
45
45
                </p></dd><dt><span class="term"><code class="option">-h</code></span></dt><dd><p>
46
46
                Print usage information.
47
 
                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2483740"></a><h2>EVENTLOG RECORD FORMAT</h2><p>For the write operation, <code class="literal">eventlogadm</code>
 
47
                </p></dd></dl></div></div><div class="refsect1" title="EVENTLOG RECORD FORMAT"><a name="id2489716"></a><h2>EVENTLOG RECORD FORMAT</h2><p>For the write operation, <code class="literal">eventlogadm</code>
48
48
        expects to be able to read structured records from standard
49
49
        input. These records are a sequence of lines, with the record key
50
50
        and data separated by a colon character. Records are separated
51
 
        by at least one or more blank line.</p><p>The event log record field are:</p><div class="itemizedlist"><ul type="disc"><li><p>
 
51
        by at least one or more blank line.</p><p>The event log record field are:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
52
52
                <code class="literal">LEN</code> - This field should be 0, since <code class="literal">eventlogadm</code> will calculate this value.
53
 
                </p></li><li><p>
 
53
                </p></li><li class="listitem"><p>
54
54
                <code class="literal">RS1</code> - This must be the value 1699505740.
55
 
                </p></li><li><p>
 
55
                </p></li><li class="listitem"><p>
56
56
                <code class="literal">RCN</code> -  This field should be 0.
57
 
                </p></li><li><p>
 
57
                </p></li><li class="listitem"><p>
58
58
                <code class="literal">TMG</code> - The time the eventlog record
59
59
                was generated; format is the number of seconds since
60
60
                00:00:00 January 1, 1970, UTC.
61
 
                </p></li><li><p>
 
61
                </p></li><li class="listitem"><p>
62
62
                <code class="literal">TMW</code> - The time the eventlog record was
63
63
                written; format is the number of seconds since 00:00:00
64
64
                January 1, 1970, UTC.
65
 
                </p></li><li><p>
 
65
                </p></li><li class="listitem"><p>
66
66
                <code class="literal">EID</code> - The eventlog ID.
67
 
                </p></li><li><p>
 
67
                </p></li><li class="listitem"><p>
68
68
                <code class="literal">ETP</code> - The event type -- one of
69
69
                "INFO",
70
70
                "ERROR", "WARNING", "AUDIT
71
71
                SUCCESS" or "AUDIT FAILURE".
72
 
                </p></li><li><p>
 
72
                </p></li><li class="listitem"><p>
73
73
                <code class="literal">ECT</code> - The event category; this depends
74
74
                on the message file. It is primarily used as a means of
75
75
                filtering in the eventlog viewer.
76
 
                </p></li><li><p>
 
76
                </p></li><li class="listitem"><p>
77
77
                <code class="literal">RS2</code> - This field should be 0.
78
 
                </p></li><li><p>
 
78
                </p></li><li class="listitem"><p>
79
79
                <code class="literal">CRN</code> - This field should be 0.
80
 
                </p></li><li><p>
 
80
                </p></li><li class="listitem"><p>
81
81
                <code class="literal">USL</code> - This field should be 0.
82
 
                </p></li><li><p>
 
82
                </p></li><li class="listitem"><p>
83
83
                <code class="literal">SRC</code> - This field contains the source
84
84
                name associated with the event log. If a message file is
85
85
                used with an event log, there will be a registry entry
86
86
                for associating this source name with a message file DLL.
87
 
                </p></li><li><p>
 
87
                </p></li><li class="listitem"><p>
88
88
                <code class="literal">SRN</code> - The name of the machine on
89
89
                which the eventlog was generated. This is typically the
90
90
                host name.
91
 
                </p></li><li><p>
 
91
                </p></li><li class="listitem"><p>
92
92
                <code class="literal">STR</code> - The text associated with the
93
93
                eventlog. There may be more than one string in a record.
94
 
                </p></li><li><p>
 
94
                </p></li><li class="listitem"><p>
95
95
                <code class="literal">DAT</code> - This field should be left unset.
96
 
                </p></li></ul></div></div><div class="refsect1" lang="en"><a name="id2481612"></a><h2>EXAMPLES</h2><p>An example of the record format accepted by <code class="literal">eventlogadm</code>:</p><pre class="programlisting">
 
96
                </p></li></ul></div></div><div class="refsect1" title="EXAMPLES"><a name="id2487578"></a><h2>EXAMPLES</h2><p>An example of the record format accepted by <code class="literal">eventlogadm</code>:</p><pre class="programlisting">
97
97
        LEN: 0
98
98
        RS1: 1699505740
99
99
        RCN: 0
116
116
        tail -f /var/log/messages | \\
117
117
                my_program_to_parse_into_eventlog_records | \\
118
118
                eventlogadm SystemLogEvents
119
 
        </pre></div><div class="refsect1" lang="en"><a name="id2481661"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2481672"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were
 
119
        </pre></div><div class="refsect1" title="VERSION"><a name="id2487628"></a><h2>VERSION</h2><p>This man page is correct for version 3.0.25 of the Samba suite.</p></div><div class="refsect1" title="AUTHOR"><a name="id2487639"></a><h2>AUTHOR</h2><p> The original Samba software and related utilities were
120
120
        created by Andrew Tridgell.  Samba is now developed by the
121
121
        Samba Team as an Open Source project similar to the way the
122
122
        Linux kernel is developed.</p></div></div></body></html>