Hi,
here with the actual patches...
Regards
Carsten
>From 0b956e2e22388d368452ede5e630205a3d326b57 Mon Sep 17 00:00:00 2001
From: Carsten Leonhardt <l...@debian.org>
Date: Sat, 30 Nov 2024 12:19:38 +0100
Subject: [PATCH 1/2] Change **StartTLS** to \texttt{StartTLS}
For consistency with commit 71e9f56f8add21709bfd0491c3f4c592101eaf90
---
docs/manuals/en/main/dirdconf.tex | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/manuals/en/main/dirdconf.tex b/docs/manuals/en/main/dirdconf.tex
index abcd04a5..a48ec19c 100644
--- a/docs/manuals/en/main/dirdconf.tex
+++ b/docs/manuals/en/main/dirdconf.tex
@@ -4239,7 +4239,7 @@ where \texttt{parameters} are the space separated list of one or more plugin par
point and \texttt{<filter>} is a standard LDAP search object filter which support dynamic string
substitution: \texttt{\%u} will be replaced by credential's username and \texttt{\%p} by credential's
password, i.e. \texttt{query=dc=bacula,dc=com/(cn=\%u)}.
- \item [starttls] - instruct BPAM LDAP Plugin to use **StartTLS** extension if LDAP Directory service
+ \item [starttls] - instruct BPAM LDAP Plugin to use \texttt{StartTLS} extension if LDAP Directory service
will support it and follback to no TLS if this extension is not available.
\item [starttlsforce] - does the same what `starttls` but resport error on fallback.
\end{itemize}
@@ -4815,7 +4815,7 @@ where \texttt{parameters} are the space separated list of one or more plugin par
point and \texttt{<filter>} is a standard LDAP search object filter which support dynamic string
substitution: \texttt{\%u} will be replaced by credential's username and \texttt{\%p} by credential's
password, i.e. \texttt{query=dc=bacula,dc=com/(cn=\%u)}.
- \item [starttls] - instruct BPAM LDAP Plugin to use **StartTLS** extension if LDAP Directory service
+ \item [starttls] - instruct BPAM LDAP Plugin to use \texttt{StartTLS} extension if LDAP Directory service
will support it and follback to no TLS if this extension is not available.
\item [starttlsforce] - does the same what `starttls` but resport error on fallback.
\end{itemize}
--
2.39.5
>From f7d1b5676d0a5feab3d8d13928addbaea1b59a30 Mon Sep 17 00:00:00 2001
From: Carsten Leonhardt <l...@debian.org>
Date: Sat, 30 Nov 2024 12:22:15 +0100
Subject: [PATCH 2/2] Fix build errors with newer LaTex
Some change after Latex as distributed in Texlive after version
2022.20230122 causes errors without these changes.
---
docs/manuals/en/main/cdp.tex | 2 +-
docs/manuals/en/main/postgresql.tex | 2 +-
docs/manuals/en/main/tls.tex | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/docs/manuals/en/main/cdp.tex b/docs/manuals/en/main/cdp.tex
index 25e35820..d5b06f2f 100644
--- a/docs/manuals/en/main/cdp.tex
+++ b/docs/manuals/en/main/cdp.tex
@@ -1,4 +1,4 @@
-\chapter{Using \bacula{} \acl{CDP}}
+\chapter{Using \bacula{} CDP}
\label{blb:cdp}
\index[general]{CDP}
\index[general]{Continuous Data Protection}
diff --git a/docs/manuals/en/main/postgresql.tex b/docs/manuals/en/main/postgresql.tex
index 589b2d80..f8319bad 100644
--- a/docs/manuals/en/main/postgresql.tex
+++ b/docs/manuals/en/main/postgresql.tex
@@ -305,7 +305,7 @@ mt -f /dev/nst0 weof
Where you should replace \bfilename{/dev/nst0} with the appropriate tape drive
device name for your machine.
-\section{Installing \postgresql{} from \acsp{RPM}}
+\section{Installing \postgresql{} from RPM}
\index[general]{\postgresql{}!Installing from \acsp{RPM}}
\index[general]{Installing \postgresql{} from \acsp{RPM}}
If you are installing \postgresql{} from \acsp{RPM}, you will need to install
diff --git a/docs/manuals/en/main/tls.tex b/docs/manuals/en/main/tls.tex
index 914b8e35..db125a84 100644
--- a/docs/manuals/en/main/tls.tex
+++ b/docs/manuals/en/main/tls.tex
@@ -841,7 +841,7 @@ Let's consider ``darkstar-fd'' (on ``darkstar.example.com'') and ``arrakis-fd''
Please note that the \bdirectivename{\acs{TLS} Allowed CN} directive is only configured on the Storage Daemon side.
This is due to the fact that the communication in this case is always between the Storage Daemon acting as a ``\acs{TLS} server'' and the File Daemon acting as a ``\acs{TLS} client''. In this case, the client is the peer in the \acs{TLS} communications context. The \ac{CN} in the client's certificate subject will be checked by the Storage Daemon if it is an ``\emph{Allowed \acs{CN}}''. in the case of the above example, \bdirectivename{\acs{TLS} Allowed CN = darkstar.example.com, arrakis.example.com} is allowing ``darkstar-fd'' (at darkstar.example.com) and ``arrakis-fd'' (at arrakis.example.com) clients to connect to ``caladan-sd'' storage daemon at ``caladan.example.com'' using \acs{TLS}.
-\subsection{Using Certificates Issued by Different Root \acsp{CA}}
+\subsection{Using Certificates Issued by Different Root CA}
It is possible to have a \acs{TLS} environment that uses certificates issued by different \acsp{CA}. In the above examples, we have been using only one root \acs{CA}:
\begin{bVerbatim}
--
2.39.5
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
