[Ach] [PATCH] Added latex2html to Makefile

[Aaron Zauner]

On 20 Nov 2013, at 17:39, L. Aaron Kaplan <kaplan at cert.at> wrote:

> 
> On Nov 20, 2013, at 8:50 AM, Arsen STASIC <arsen.stasic at univie.ac.at> wrote:
> 
>> * Arsen STASIC <arsen.stasic at univie.ac.at> [2013-11-20 08:28 (+0100)]:
>>> Hi all!
>>> 
>>> * Adam Lewicki <adam at lewicki.at> [2013-11-20 07:09 (+0000)]:
>>>> 
>>>> Quoting Pepi Zawodsky <pepi.zawodsky at maclemon.at>:
>>>> 
>>>>> While these are typographically correct as an apostropohe (like in
>>>>> a possesive case) they do break command line strings and config
>>>>> lines that are meant to be copy/pasteable. Well, you can still
>>>>> copy them, but they break the command or config file you paste
>>>>> them in.
>>>> 
>>>> If I may add my 2 cents. As a webserver guy here I'd suggest
>>>> producing a document in more than one format. While PDF is nice to
>>>> print out and put in a binder or show around in a management-esque
>>>> meeting, it's not my preferred go-to-source for c&p-able code/conf
>>>> snippets.
>>>> 
>>>> I'm not really confident in TeX, but isn't there an option to
>>>> produce plain-text documents or even simple html?
>>>> Both formats are quite okay for copy&paste.
>>>> 
>>>> You may now tear my arguments apart :)
>>> 
>>> +1
>>> 
>>> latex2html could be a tool for that.
>>> 
>>> Let me introduce myself. I work as an DevOp since 2001 mainly on Linux,
>>> FreeBSD and AIX. I my spare time I hacked a little bit on OpenBSD.
>> 
>> Find attached a patch which adds latex2html to Makefile.
>> What is the best way to contribute to this interesting and really
>> important project?
>> Can You give me write permissions to your git-repo?
>> 
> 
> 
> Well, off the top of my head: there are a few sections missing.
> So, if you feel like adding to the project, just take a look at the \todo{} sections.
> Also, we keep a TODO.txt file in the git repo.
> 
> Another very crucial open issue is testing.
> We need to be able to test our recommendations and make sure 
> that there are no bugs there.
> 
> We need reviewers and proof reading. Ideally a native speaker.
> 
> Today is also the last day for adding additional features (for version 1 of the document). 
> So if you still find some important section missing, let us know today if possible.
> 
> Another completely open task is improving the bettercrypto.org website. I managed to make it a little bit pretty, but we don't have much content yet.
> 
> Finally, what's *really* needed urgently: 
> * someone with more crypto background (IAIK?) to look at our recommendations and to correc them.
>  So far they are just educated guesses.
> * writing seciton 7 (RNGs)

Do we have someone who’s capable of writing a solid section on this topic? This is quite complicated - so if  we do not find someone I’d recommend removing the section completly.

Also I do not have insight if HAVEGE is well audited, there are some papers on how it works, but the project is quite old and I can’t find proper analysis of the RNG.

Aaron

> * cleaning up section 8
>  * writing 8.3
>  * checking 8.2
>  * adding screenshots of ssllabs tests to 8.5
>  * integrate 8.5.6 and 8.5.7 (these two parts were the "old section 8". They still contain good info) 
> In general, section 8 is still a bit messy.
> 
> * every subsection in section 9 should be structured as "apache" 9.1.1.
> 
> 
>> Signed-off-by: Arsen Stasic <arsen.stasic at univie.ac.at>
>> 
>> ---
>> src/Makefile | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>> 
>> diff --git a/src/Makefile b/src/Makefile
>> index 8411373..33adb70 100644
>> --- a/src/Makefile
>> +++ b/src/Makefile
>> @@ -9,5 +9,9 @@ all:
>>       #dvipdfm -z 9 applied-crypto-hardening
>>       #dvipdf applied-crypto-hardening.dvi
>> 
>> +html:
>> +       latex2html applied-crypto-hardening
>> +
>> clean:
>> -       rm -f applied-crypto-hardening.aux applied-crypto-hardening.bbl
>>       applied-crypto-hardening.blg applied-crypto-hardening.dvi
>> applied-crypto-hardening.log applied-crypto-hardening.pdf
>> applied-crypto-hardening.toc
>> +       rm -f applied-crypto-hardening.aux applied-crypto-hardening.bbl
>> applied-crypto-hardening.blg applied-crypto-hardening.dvi
>> applied-crypto-hardening.log applied-crypto-hardening.pdf
>> applied-crypto-hardening.toc 
>> +       rm -rf applied-crypto-hardening/
>> -- 
>> 1.8.3.2
>> _______________________________________________
>> Ach mailing list
>> Ach at lists.cert.at
>> http://lists.cert.at/cgi-bin/mailman/listinfo/ach
> 
> --- 
> // L. Aaron Kaplan <kaplan at cert.at> - T: +43 1 5056416 78
> // CERT Austria - http://www.cert.at/
> // Eine Initiative der nic.at GmbH - http://www.nic.at/
> // Firmenbuchnummer 172568b, LG Salzburg
> 
> 
> 
> 
> _______________________________________________
> Ach mailing list
> Ach at lists.cert.at
> http://lists.cert.at/cgi-bin/mailman/listinfo/ach

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1091 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.cert.at/pipermail/ach/attachments/20131120/b9e840dc/attachment.sig>