<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Dear list,<br>
<br>
let me open this thread to continue the discussion rising in GitHub
PR 74 [1].<br>
<br>
Tobias wrote:<br>
<blockquote type="cite">
<div class="comment-content">
<div class="edit-comment-hide">
<div class="comment-body markdown-body markdown-format
js-comment-body">
<p>[...]</p>
<p>The TeX files take what is there, it is about the linked
(example-)config files.<br>
Yes, it is theoretically possible to use macros and the
like for included stuff (We had that), but it is<br>
painful and produces sub-standard output.</p>
</div>
</div>
</div>
</blockquote>
Agreed.<br>
<blockquote type="cite">
<div class="comment-content">
<div class="edit-comment-hide">
<div class="comment-body markdown-body markdown-format
js-comment-body">
<p>IMHO a working way would be:</p>
<ol class="task-list">
<li>Have all config files (from <code>src/configuration/</code>)
moved to a template (eg, <code>configuration.template/</code>)</li>
<li>Replace hard-coded cipherstring with @@CIPHERSTRINGB@@
</li>
</ol>
</div>
</div>
</div>
</blockquote>
Agreed. What about the special cipherstrings for the Webserver
configs? These are quite different from CIPHERSTRINGA and
CIPHERSTRINGB. To be consistent within the guide, these "exceptions"
should be replaced. But then what about OpenSSH configs? Those are
in no way going to fit to a normal cipher string.<br>
<br>
Maybe we should define some well described exeptions (why, what,
differences to A/B, ...), which have their own macro?<br>
<blockquote type="cite">
<div class="comment-content">
<div class="edit-comment-hide">
<div class="comment-body markdown-body markdown-format
js-comment-body">
<p>And then to produce something usable:</p>
<ol class="task-list">
<li>Run a <code>sed</code> cmd on every file file in <code>configuration.template</code>
and put them into <code>configuration</code> (or <code>src/configuration</code>
for that matter</li>
<li>“Deliver” only files from the build configurations (<em>not</em>
the templates)
<ul class="task-list">
<li>via the repository (i.e., update the <code>configuration</code>
folder on every change to the cipherstring)</li>
<li>via the bettercrypto site</li>
<li>in the generated TeX output</li>
<li>(in hypothetical ebooks and whatnot…)</li>
</ul>
</li>
</ol>
</div>
</div>
</div>
</blockquote>
Sed is a good option, available on most Linux systems. <br>
<br>
Maybe do something like this:<br>
- create new branch "delivery"<br>
- in branch master, provide the templates<br>
- in branch delivery, provide the "compiled" stuff<br>
- changes in master get merged into delivery, preferably via CI
(Travis?)<br>
- delivery is the base for every further action like PDF rendering,
HTML, ebooks, ... (maybe generated via CI?)<br>
<br>
One pitfall I see arising anyway: if one changes this to use
templates, what about the \configfile macro in the TeX sources?
There are plenty of this using something like
\configfile{<line1>-<line2>}{<path>}, but in the
templates the line numbers will be different from the ones in the
"compiled" sources.<br>
<blockquote type="cite">
<div class="comment-content">
<div class="edit-comment-hide">
<div class="comment-body markdown-body markdown-format
js-comment-body">
<p>[...]<br>
</p>
<p>(I wont have time to do that before November, tho…)</p>
</div>
</div>
</div>
</blockquote>
If you are interested, I am willing to contribute to this. My
employer is somewhat interested in this... ;)<br>
<br>
Cheers,<br>
Oliver<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://github.com/BetterCrypto/Applied-Crypto-Hardening/pull/74">https://github.com/BetterCrypto/Applied-Crypto-Hardening/pull/74</a><br>
<br>
<pre class="moz-signature" cols="72">--
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
-------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
</pre>
</body>
</html>