git://git.exim.org
/
exim.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
dd80338
)
Docs: more subsections
author
Jeremy Harris
<jgh146exb@wizmail.org>
Fri, 25 Oct 2024 11:35:46 +0000
(12:35 +0100)
committer
Jeremy Harris
<jgh146exb@wizmail.org>
Fri, 25 Oct 2024 11:35:46 +0000
(12:35 +0100)
doc/doc-docbook/spec.xfpt
patch
|
blob
|
history
diff --git
a/doc/doc-docbook/spec.xfpt
b/doc/doc-docbook/spec.xfpt
index 76bdd1396028f6d325a392162517c84a8ca1dd9e..3da27cdea67e53842a79c010f764b6df97576499 100644
(file)
--- a/
doc/doc-docbook/spec.xfpt
+++ b/
doc/doc-docbook/spec.xfpt
@@
-28220,7
+28220,7
@@
There are good and bad examples at the end of the next section.
-.section "The PLAIN authentication mechanism" "SECID172"
+.s
ubs
ection "The PLAIN authentication mechanism" "SECID172"
.cindex "PLAIN authentication mechanism"
.cindex authentication PLAIN
.cindex "binary zero" "in &(plaintext)& authenticator"
.cindex "PLAIN authentication mechanism"
.cindex authentication PLAIN
.cindex "binary zero" "in &(plaintext)& authenticator"
@@
-28304,7
+28304,7
@@
always fails if its second argument is empty. However, the second way of
writing the test makes the logic clearer.
writing the test makes the logic clearer.
-.section "The LOGIN authentication mechanism" "SECID173"
+.s
ubs
ection "The LOGIN authentication mechanism" "SECID173"
.cindex "LOGIN authentication mechanism"
.cindex authentication LOGIN
The LOGIN authentication mechanism is not documented in any RFC, but is in use
.cindex "LOGIN authentication mechanism"
.cindex authentication LOGIN
The LOGIN authentication mechanism is not documented in any RFC, but is in use
@@
-28352,7
+28352,7
@@
the password conform to the Exim syntax. At the LDAP level, the password is an
uninterpreted string.
uninterpreted string.
-.section "Support for different kinds of authentication" "SECID174"
+.s
ubs
ection "Support for different kinds of authentication" "SECID174"
A number of string expansion features are provided for the purpose of
interfacing to different ways of user authentication. These include checking
traditionally encrypted passwords from &_/etc/passwd_& (or equivalent), PAM,
A number of string expansion features are provided for the purpose of
interfacing to different ways of user authentication. These include checking
traditionally encrypted passwords from &_/etc/passwd_& (or equivalent), PAM,