sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-12 09:18:10 +03:00
Code

Put in ab's conversion to XML. First step: Make all the SGML docs

Browse Source 
conform to the (more strict) XML syntax.
This commit is contained in:
Jelmer Vernooij 0001-01-01 00:00:00 +00:00
parent 0930628bd5
commit d9cf973a46
7 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/docbook/devdoc/NetBIOS.sgml
View File

@ -101,7 +101,7 @@ rfc1001.txt describes, amongst other things, the implementation and use
of, a 'NetBIOS Name Service'. NT/AS offers 'Windows Internet Name Service'
which is fully rfc1001/2 compliant, but has had to take specific action
with certain NetBIOS names in order to make it useful. (for example, it
deals with the registration of <1c> <1d> <1e> names all in different ways.
deals with the registration of &lt;1c&gt; &lt;1d&gt; &lt;1e&gt; names all in different ways.
I recommend the reading of the Microsoft WINS Server Help files for full
details).
</para>

4
docs/docbook/devdoc/Tracing.sgml
View File

@ -80,11 +80,11 @@ stderr output from this command to a file for later perusal. For
example, if I'm using a csh style shell:
</para>
<para><command>strace -f -p 3872 >& strace.out</command></para>
<para><command>strace -f -p 3872 &gt;&amp; strace.out</command></para>
<para>or with a sh style shell:</para>
<para><command>strace -f -p 3872 > strace.out 2>&1</command></para>
<para><command>strace -f -p 3872 > strace.out 2&gt;&amp;1</command></para>
<para>
Note the "-f" option. This is only available on some systems, and

16
docs/docbook/devdoc/cifsntdomain.sgml
View File

@ -2175,7 +2175,7 @@ return 0 - indicates success
</sect3>
</sect2>
<sect2
<sect2>
<title>LSA SAM Logon</title>
<para><emphasis>
@ -2279,7 +2279,7 @@ Note: presumably, the SAM_INFO structure is validated, and a (currently
<para><emphasis>
Note: mailslots will contain a response mailslot, to which the response
should be sent. the target NetBIOS name is REQUEST_NAME<20>, where
should be sent. the target NetBIOS name is REQUEST_NAME&lt;20&gt;, where
REQUEST_NAME is the name of the machine that sent the request.
</emphasis></para>
@ -2361,7 +2361,7 @@ Note: mailslots will contain a response mailslot, to which the response
</variablelist>
</sect3>
</sect2
</sect2>
<sect2>
<title>SAM Logon</title>
@ -2663,16 +2663,16 @@ pwdump(machine$) (initially) == md4(lmowf(unicode(machine)))
<title>Protocol</title>
<para>
C->S ReqChal,Cc S->C Cs
C-&gt;S ReqChal,Cc S-&gt;C Cs
</para>
<para>
C & S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))
C &amp; S compute session key Ks = E(PW[9..15],E(PW[0..6],Add(Cc,Cs)))
</para>
<para>
C: Rc = Cred(Ks,Cc) C->S Authenticate,Rc S: Rs = Cred(Ks,Cs),
assert(Rc == Cred(Ks,Cc)) S->C Rs C: assert(Rs == Cred(Ks,Cs))
assert(Rc == Cred(Ks,Cc)) S-&gt;C Rs C: assert(Rs == Cred(Ks,Cs))
</para>
<para>
@ -2682,7 +2682,7 @@ on registry settings. This will also occur weekly afterwards.
</para>
<para>
C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S ServerPasswordSet,Rc',Tc,
C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C-&gt;S ServerPasswordSet,Rc',Tc,
arc4(Ks[0..7,16],lmowf(randompassword()) C: Rc = Cred(Ks,Rc+Tc+1) S:
assert(Rc' == Cred(Ks,Rc+Tc)), Ts = Time() S: Rs' = Cred(Ks,Rs+Tc+1)
S->C Rs',Ts C: assert(Rs' == Cred(Ks,Rs+Tc+1)) S: Rs = Rs'
@ -2694,7 +2694,7 @@ such as workstation and domain omitted)
</para>
<para>
C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C->S NetLogonSamLogon,Rc',Tc,U,
C: Tc = Time(), Rc' = Cred(Ks,Rc+Tc) C-&gt;S NetLogonSamLogon,Rc',Tc,U,
arc4(Ks[0..7,16],16,ntowf(P),16), arc4(Ks[0..7,16],16,lmowf(P),16) S:
assert(Rc' == Cred(Ks,Rc+Tc)) assert(passwords match those in SAM) S:
Ts = Time()

6
docs/docbook/devdoc/encryption.sgml
View File

@ -90,7 +90,7 @@
</sect1>
<sect1>
<title><anchor id="SMBPASSWDFILEFORMAT">The smbpasswd file</title>
<title><anchor id="SMBPASSWDFILEFORMAT"/>The smbpasswd file</title>
<para>In order for Samba to participate in the above protocol
it must be able to look up the 16 byte hashed values given a user name.
@ -102,11 +102,11 @@
/etc/passwd</filename> and the <filename>smbpasswd</filename> file,
a utility, <command>mksmbpasswd.sh</command>, is provided to generate
a smbpasswd file from a UNIX <filename>/etc/passwd</filename> file.
</para
</para>
<para>To generate the smbpasswd file from your <filename>/etc/passwd
</filename> file use the following command :</para>
</filename> file use the following command:</para>
<para><prompt>$ </prompt><userinput>cat /etc/passwd | mksmbpasswd.sh
&gt; /usr/local/samba/private/smbpasswd</userinput></para>

8
docs/docbook/devdoc/printing.sgml
View File

@ -28,7 +28,7 @@ Printing Interface to Various Back ends
<para>
Samba uses a table of function pointers to seven functions. The
function prototypes are defined in the <VarName>printif</VarName> structure declared
function prototypes are defined in the <varname>printif</varname> structure declared
in <filename>printing.h</filename>.
</para>
@ -199,7 +199,7 @@ object when the client issues a GetJob(level == 2) request.
<sect1>
<title>
ChangeID & Client Caching of Printer Information
ChangeID and Client Caching of Printer Information
</title>
<para>
@ -345,7 +345,7 @@ information</para></listitem>
</itemizedlist>
<para>
A <VarName>SPOOL_NOTIFY_INFO</VarName> contains:
A <varname>SPOOL_NOTIFY_INFO</varname> contains:
</para>
<itemizedlist>
@ -359,7 +359,7 @@ in the SPOOL_NOTIFY_INFO_DATA array</para></listitem>
</itemizedlist>
<para>
The <VarName>SPOOL_NOTIFY_INFO_DATA</VarName> entries contain:
The <varname>SPOOL_NOTIFY_INFO_DATA</varname> entries contain:
</para>
<itemizedlist>

4
docs/docbook/devdoc/sam.sgml
View File

@ -27,7 +27,7 @@ accessed.</para>
For example, when you call
</para>
<programlisting><
<programlisting>
NTSTATUS sam_get_account_by_name(const SAM_CONTEXT *context, const
NT_USER_TOKEN *access_token, uint32 access_desired, const char *domain,
const char *name, SAM_ACCOUNT_HANDLE **account)
@ -182,7 +182,7 @@ This is where smbd, samtest and whatever end-user replacement we have
for pdbedit sits. They use only the SAM interface, and do not get
'special knowledge' of what is below them.
</para>
</sect2>
<sect2>
<title>SAM Interface</title>

2
docs/docbook/devdoc/unix-smb.sgml
View File

@ -13,7 +13,7 @@
<para>
This is a short document that describes some of the issues that
confront a SMB implementation on unix, and how Samba copes with
them. They may help people who are looking at unix<->PC
them. They may help people who are looking at unix&lt;-&gt;PC
interoperability.
</para>