9 * DDOS possibilities when we increase cyrpto security?? What about that?
11 * write a Justification section to every setting, maybe have that later in the document.
13 * move the explanations to a later part of the document. Code snippets go *first* . The target group is sysadmins, must be easily copy & paste-able. Or find a different way so that they can easily use/read the document
15 * Write section 7.3 (-> Adi . How to chose your own cipher string + screenshots)
17 DONE * Decide/Discuss recommended ciphers:
18 - DH parameters: what is our recommendation? >2048? >=2048? leave default (aka 1024)?
19 --> answer: we trust IETF/IKE as described in ECRYPT2
21 * comments from IAIK integrate (--> Aaron)
22 * SHA-1 section: write why it is a problem
23 * include OpenSSL names/IANA names into appendix
24 * Document RNG problem in Apache (--> Pepi)
25 * Oracle ?? (--> Berg?? maybe . Or aaron: ask nic.at. Or link to T-Systems paper)
26 * DB2 (--> Berg. Or ask MLeyrer)
31 DONE * one-column layout: make page margins smaller
32 DONE * add large "DRAFT" letters on top of every page.
33 make the git version number part of the document
34 DONE * Layout of sample code (lstisting format) : make it pretty!
35 Rendering in Firefox (inline) on Windows seems to be really messed up. What happenened?
38 * make every section like the Apache section
43 * how to keep things up to date?
44 * how to automatically test compatibility?
45 * how to make sure that this document has the latest information on cipher strengths?
50 * scan our local region of the internet for https/smtp/imaps/pop3s
54 - key management , key life cycle
56 - common / default passphrases
60 * Wish List for software vendors?
61 * sweet spot, wo koennen wir was sinnvoll machen, was waere zu viel (8192 bit keys...)
64 1. document the abstract needs that we have for the cipher settings (HSTS etc)
65 Then find the best cipher setting strings per se
66 Only then put it to all servers and keep it rather uniformely (as much as possible)
70 * Test with more clients and other OSes than OSX / iPhone!!
75 - Playstation und XBox? --> LATER!
80 - chapter owner makes a test setup
81 - tested by: XXX , on: $date. Screenshot of SSLlabs/ $testtool. (checktls.com)
83 * document (cite) EVERYTHING! Why we chose certain values. Referneces, references, references. Otherwise it does not count!
85 * .bib file is completely wrong. Make good citations/references. Add books: Schneier, ...
86 * !! important: add the version string to everything that we tested!!
89 - security specialists / freaks who want the very best settings
90 - should as many clients work with the settings as possible
91 * look at TLS1.2 specs and really check if we want all of these settings
96 Definitely still missing these subsubsections:
97 * Exchange Server ?? (--> bei M$ angefragt, Evtl. Beitrag von A-Trust)
99 DONE * Exim4 (-> Adi & Wolfgang Breya)
101 * Asa / Palo Alto (-> Azet)
102 * Terminal Server (VNC ), ??
105 --> verweise auf die xmpp community bzw. auf xmpp.net verweisen.
106 Empfehlung: unbedingt ejabberd updaten!!
109 ----- snip ---- all protocols that we looked at --- snip ----
110 * whatsapp --> man kann nichts machen, out of scope
111 * Lync: == SIP von M$.
112 * Skype: man kann ncihts machen, out of scope.
113 * Wi-Fi APs, 802.1X, ... ???? --> out of scope
119 * L2TP over IPSec -> egal
122 * DNSSec ?? Verweis auf BCPxxx --> out of scope
124 What happens at the IETF at the moment?
125 * TOR?? --> out of scope
126 * S/Mime --> nachsehen, gibt es BCPs? (--> Ramin)
127 * TrueCrypt, LUKS, FileVault, etc ---> out of scope
128 * AFS -> out of scope
129 * Kerberos --> out of scope
130 * NNTP -> out of scope
131 * NTPs tlsdate -> out of scope
132 * BGP / OSPF --> out of scope
133 * irc,silc --> out of scope
134 !! * IPMI/ILO/RAC: Java --> important. Empfehlung: nie ins Internet, nur in ein eigenes mgmt VLAN, das via VPN erreichbar ist!!
135 * LDAP -> out of scope
136 * RADIUS? -> maybe later...
137 * Moxa , APC, und co... ICS . Ethernet to serial --> out of scope
139 * rsyslog --> out of scope
140 * ARP bei v6 spoofing -> out of scope
141 * tinc?? -> out of scope
142 * rsync -> nur ueber ssh fahren ausser public web mirrors
143 * telnets -> out of scope
144 * ftps -> out of scope
145 !! * seclayer-tcp --> review von Posch & co.
146 seclayer-tcp 3495/udp # securitylayer over tcp
147 seclayer-tcp 3495/tcp # securitylayer over tcp
149 * plesk -> out of scope
150 * phpmyadmin --> haengt am apache, out of scope
151 * DSL modems -> out of scope
152 * UPnP, natPmp --> out of scope
153 ----- snip ---- all protocols that we looked at --- snip ----
162 - add two, three sentences
164 - embedded devices are a problem
179 * Windows Active Directory
180 * SRP: not part of this document
181 * \cipherA , \cipherB setting ---> does not work in our \begin{listing} environment --> maybe there is a different listing environment or use awk/sed/make/perl/python
182 * What about 3270 terminal emulation? How to do crypto there? Can we? ( --> IBM sec. Stammtisch. Aaron)