7 * write a Justification section to every setting, maybe have that later in the document.
9 * 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
11 * Write section 7.3 (-> Adi . How to chose your own cipher string + screenshots)
13 * Decide/Discuss recommended ciphers:
14 - AES/CAMELLIA/ARIA20/...
15 - 256bit vs 128bit (security margin, ordering in recommended ciphers)
16 - DH parameters: what is our recommendation? >2048? >=2048? leave default (aka 1024)?
20 DONE * one-column layout: make page margins smaller
21 DONE * add large "DRAFT" letters on top of every page.
22 make the git version number part of the document
23 * Layout of sample code (lstisting format) : make it pretty!
29 * how to keep things up to date?
30 * how to automatically test compatibility?
31 * how to make sure that this document has the latest information on cipher strengths?
36 * scan our local region of the internet for https/smtp/imaps/pop3s
40 - key management , key life cycle
45 * Wish List for software vendors?
46 * sweet spot, wo koennen wir was sinnvoll machen, was waere zu viel (8192 bit keys...)
49 1. document the abstract needs that we have for the cipher settings (HSTS etc)
50 Then find the best cipher setting strings per se
51 Only then put it to all servers and keep it rather uniformely (as much as possible)
55 * Test with more clients and other OSes than OSX / iPhone!!
60 - Playstation und XBox? --> LATER!
65 * document (cite) EVERYTHING! Why we chose certain values. Referneces, references, references. Otherwise it does not count!
67 * .bib file is completely wrong. Make good citations/references. Add books: Schneier, ...
68 * !! important: add the version string to everything that we tested!!
71 - security specialists / freaks who want the very best settings
72 - should as many clients work with the settings as possible
73 * look at TLS1.2 specs and really check if we want all of these settings
78 Definitely still missing these subsubsections:
79 * Exchange Server ?? (--> bei M$ angefragt, Evtl. Beitrag von A-Trust)
81 DONE * Exim4 (-> Adi & Wolfgang Breya)
83 * Asa / Palo Alto (-> Azet)
84 * Terminal Server (VNC ), ??
87 --> verweise auf die xmpp community bzw. auf xmpp.net verweisen.
88 Empfehlung: unbedingt ejabberd updaten!!
91 ----- snip ---- all protocols that we looked at --- snip ----
92 * whatsapp --> man kann nichts machen, out of scope
93 * Lync: == SIP von M$.
94 * Skype: man kann ncihts machen, out of scope.
95 * Wi-Fi APs, 802.1X, ... ???? --> out of scope
101 * L2TP over IPSec -> egal
104 * DNSSec ?? Verweis auf BCPxxx --> out of scope
106 What happens at the IETF at the moment?
107 * TOR?? --> out of scope
108 * S/Mime --> nachsehen, gibt es BCPs? (--> Ramin)
109 * TrueCrypt, LUKS, FileVault, etc ---> out of scope
110 * AFS -> out of scope
111 * Kerberos --> out of scope
112 * NNTP -> out of scope
113 * NTPs tlsdate -> out of scope
114 * BGP / OSPF --> out of scope
115 * irc,silc --> out of scope
116 !! * IPMI/ILO/RAC: Java --> important. Empfehlung: nie ins Internet, nur in ein eigenes mgmt VLAN, das via VPN erreichbar ist!!
117 * LDAP -> out of scope
118 * Moxa , APC, und co... ICS . Ethernet to serial --> out of scope
120 * rsyslog --> out of scope
121 * ARP bei v6 spoofing -> out of scope
122 * tinc?? -> out of scope
123 * rsync -> nur ueber ssh fahren ausser public web mirrors
124 * telnets -> out of scope
125 * ftps -> out of scope
126 !! * seclayer-tcp --> review von Posch & co.
127 seclayer-tcp 3495/udp # securitylayer over tcp
128 seclayer-tcp 3495/tcp # securitylayer over tcp
130 * plesk -> out of scope
131 * phpmyadmin --> haengt am apache, out of scope
132 * DSL modems -> out of scope
133 * UPnP, natPmp --> out of scope
134 ----- snip ---- all protocols that we looked at --- snip ----
143 - add two, three sentences
145 - embedded devices are a problem
159 * Windows Active Directory