force use of pandoc version >= 3.1.12.2

The `bin/pandoc-wrapper.sh` tool will verify that the ssytem
has a recent enough version of `pandoc(1)`.

We explain why we insist on `pandoc(1)`. version >= 3.1.12.2
in comments where the $PANDOC_MIN_VERSION is set.

Added `--wrap=preserve` as a default argument to `pandoc(1)`.
While this change will impact every HTML file generated,
we believe this will improve the ability of someone to look
at the generated HTML and correlate with the original markdown.

Changed `bin/pandoc-wrapper.sh` VERSION from "1.4.2 2024-03-17"
to "1.4.3 2024-03-18".

Performed `make www` to achieve all of the above and to generate
HTML using the new  `--wrap=preserve` `pandoc(1)` mode.
This commit is contained in:
Landon Curt Noll committed 2024-03-18 01:26:39 -07:00
1 parent 9eb7a54e9f
commit b0b212acb1
402 files changed
+37061 -55132

No files matched your search

+44 -71
View File
@@ -129,9 +129,9 @@
<h2 id="author"><a name="author"></a>Author:</h2>
<ul>
<li>Name: <a href="../../authors.html#Stephen_Sykes">Stephen
Sykes</a><br> Location: <a href="../../location.html#FI">FI</a> -
<em>Republic of Finland </em> (<em>Finland</em>) <br><br></li>
<li>Name: <a href="../../authors.html#Stephen_Sykes">Stephen Sykes</a><br>
Location: <a href="../../location.html#FI">FI</a> - <em>Republic of Finland </em> (<em>Finland</em>)
<br><br></li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-author.sh -->
@@ -144,8 +144,7 @@ Sykes</a><br> Location: <a href="../../location.html#FI">FI</a> -
<h3 id="bugs-and-misfeatures">Bugs and (Mis)features:</h3>
<p>The current status of this entry is:</p>
<pre><code>STATUS: INABIAF - please **DO NOT** fix</code></pre>
<p>For more detailed information see <a
href="../../bugs.html#2004_sds">2004 sds bugs</a>.</p>
<p>For more detailed information see <a href="../../bugs.html#2004_sds">2004 sds bugs</a>.</p>
<h2 id="to-use">To use:</h2>
<div class="sourceCode" id="cb3"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb3-1"><a href="#cb3-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./sds</span></span></code></pre></div>
<h2 id="try">Try:</h2>
@@ -153,24 +152,22 @@ href="../../bugs.html#2004_sds">2004 sds bugs</a>.</p>
<h2 id="judges-remarks">Judges’ remarks:</h2>
<p>Why not use the program to hide another program in the program? It
must have seemed reasonable at the time.</p>
<p>The ability to hide a message in plain text is quite charming,
really. We must admit to a bit of uncertainty about where you’d find
such messages, or how useful they’d be. Or, of course, whether all those
<p>The ability to hide a message in plain text is quite charming, really.
We must admit to a bit of uncertainty about where you’d find such
messages, or how useful they’d be. Or, of course, whether all those
horribly badly formatted emails spammers send might contain secret
messages. Annoyingly, it’s a little too obvious that SOMETHING has been
done to a message for us to hide one in the remarks. :)</p>
messages. Annoyingly, it’s a little too obvious that SOMETHING has
been done to a message for us to hide one in the remarks. :)</p>
<h2 id="authors-remarks">Author’s remarks:</h2>
<p><a
href="https://en.wikipedia.org/wiki/Steganography">Steganography</a> is
the term for the family of techniques used for hiding information within
other information. Today, it has many real world uses, particularly for
digital watermarking.</p>
<p>This program uses a steganographic technique to hide information in
any text file. The specific technique used is aimed at writers of
obfuscated programs for the IOCCC, as the hidden information is encoded
in the whitespace in the source file. As we know, there are up to an
additional 2048 characters of whitespace available to entrants to the
IOCCC, so it turns out that this is an ideal place to hide things.</p>
<p><a href="https://en.wikipedia.org/wiki/Steganography">Steganography</a> is the term for the
family of techniques used for hiding information within other information.
Today, it has many real world uses, particularly for digital watermarking.</p>
<p>This program uses a steganographic technique to hide information in any text
file. The specific technique used is aimed at writers of obfuscated programs
for the IOCCC, as the hidden information is encoded in the whitespace in the
source file. As we know, there are up to an additional 2048 characters of
whitespace available to entrants to the IOCCC, so it turns out that this is an
ideal place to hide things.</p>
<p>The program as provided is the steganographic decoder. Rather than
provide a separate encoding program, you should not be surprised to
learn that I opted to steganographically hide the encoder inside the
@@ -179,86 +176,62 @@ decoder.</p>
<div class="sourceCode" id="cb5"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb5-1"><a href="#cb5-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./sds</span> <span class="op">&lt;</span> sds.c</span></code></pre></div>
<p>You should see the encoder program displayed. Now save it, like:</p>
<div class="sourceCode" id="cb6"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb6-1"><a href="#cb6-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./sds</span> <span class="op">&lt;</span> sds.c <span class="op">&gt;</span> encoder.c</span></code></pre></div>
<p>Then compile <code>encoder.c</code>. You now have the complete system
ready.</p>
<p>Then compile <code>encoder.c</code>. You now have the complete system ready.</p>
<p>The encoder expects to get a filename as an argument. This filename
is the name of the file containing the information to be hidden. It
expects the file in which to hide the information to be on the standard
input, and will output the results on the standard output.</p>
<p>You can use it like this (assuming you have a file called
remarks):</p>
expects the file in which to hide the information to be on the
standard input, and will output the results on the standard output.</p>
<p>You can use it like this (assuming you have a file called remarks):</p>
<div class="sourceCode" id="cb7"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb7-1"><a href="#cb7-1" aria-hidden="true" tabindex="-1"></a><span class="bu">echo</span> <span class="st">&#39;Hello, World!&#39;</span> <span class="op">&gt;</span> message</span>
<span id="cb7-2"><a href="#cb7-2" aria-hidden="true" tabindex="-1"></a><span class="ex">./encoder</span> message <span class="op">&lt;</span> remarks <span class="op">&gt;</span> remarks_msg</span></code></pre></div>
<p>Then to decode:</p>
<div class="sourceCode" id="cb8"><pre class="sourceCode sh"><code class="sourceCode bash"><span id="cb8-1"><a href="#cb8-1" aria-hidden="true" tabindex="-1"></a><span class="ex">./sds</span> <span class="op">&lt;</span> remarks_msg</span>
<span id="cb8-2"><a href="#cb8-2" aria-hidden="true" tabindex="-1"></a><span class="ex">Hello,</span> World!</span></code></pre></div>
<p>C programs are mostly unaffected by adding steganographic content,
but it is possible in certain circumstances for whitespace to be changed
inside strings where it should be left alone. Plain text files are good
candidates for hiding information in, but the added spacing may render
the text somewhat difficult to read.</p>
but it is possible in certain circumstances for whitespace to be
changed inside strings where it should be left alone. Plain text
files are good candidates for hiding information in, but the added
spacing may render the text somewhat difficult to read.</p>
<h3 id="obfuscation">Obfuscation</h3>
<p>This program is obfuscated in a number of ways:</p>
<ul>
<li>The code is all but impossible to read due to the spacing.</li>
<li>The algorithm is well hidden in the code due to copious
red-herrings.</li>
<li>The long expressions cause indentation tools to give poor
results.</li>
<li>And good old fashioned ternary operators are the icing on the
cake.</li>
<li>The algorithm is well hidden in the code due to copious red-herrings.</li>
<li>The long expressions cause indentation tools to give poor results.</li>
<li>And good old fashioned ternary operators are the icing on the cake.</li>
</ul>
<h3 id="compiling-the-program">Compiling the program</h3>
<p>The program (and the encoder program) should compile on any
reasonable compiler. In particular, they are known to compile under GNU
C.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0
License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights
Reserved. You are free to share and adapt this file under the terms of
this license:</p>
reasonable compiler. In particular, they are known to compile under
GNU C.</p>
<h2 id="copyright-and-cc-by-sa-4.0-license">Copyright and CC BY-SA 4.0 License:</h2>
<p>This file is Copyright (c) 2023 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:</p>
<pre><code>Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)</code></pre>
<p>For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/</p>
<p>For more information, see: https://creativecommons.org/licenses/by-sa/4.0/</p>
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content for HTML phase 22 by: bin/output-index-inventory.sh via bin/md2html.sh -->
<!-- START: this line starts content generated by: bin/output-index-inventory.sh -->
<h1 id="inventory-for-2004sds"><a name="inventory"></a>Inventory for
2004/sds</h1>
<h1 id="inventory-for-2004sds"><a name="inventory"></a>Inventory for 2004/sds</h1>
<p><a href="#top">Jump to top</a></p>
<h2 id="primary-files">Primary files</h2>
<ul>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/sds.c">sds.c</a>
- entry source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/Makefile">Makefile</a>
- entry Makefile</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/sds.orig.c">sds.orig.c</a>
- original source</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/try.sh">try.sh</a>
- how to run</li>
<li><a href="2004_sds.tar.bz2">2004_sds.tar.bz2</a> - download entry
source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/sds.c">sds.c</a> - entry source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/Makefile">Makefile</a> - entry Makefile</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/sds.orig.c">sds.orig.c</a> - original source</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/try.sh">try.sh</a> - how to run</li>
<li><a href="2004_sds.tar.bz2">2004_sds.tar.bz2</a> - download entry source</li>
</ul>
<h2 id="secondary-files">Secondary files</h2>
<ul>
<li><a href="index.html">index.html</a> - entry home page</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/.entry.json">.entry.json</a>
- description of entry in JSON</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/.gitignore">.gitignore</a>
- list of files that should not be committed under git</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/.entry.json">.entry.json</a> - description of entry in JSON</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/.gitignore">.gitignore</a> - list of files that should not be committed under git</li>
<li><a href=".path">.path</a> - directory path from top directory</li>
<li><a
href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/README.md">README.md</a>
- markdown source for index.html</li>
<li><a href="https://github.com/ioccc-src/temp-test-ioccc/blob/master/2004/sds/README.md">README.md</a> - markdown source for index.html</li>
</ul>
<!-- END: next line ends content generated by: bin/output-index-inventory.sh -->