ioerror/tlsdate — pull request #7 by grothoff (2012-02-14 00:17:46+00:00)
Title: enjoy

Here some comments on your TODO:

0) relocate source and configs into subdirs
move code into src/
move configs into configs/
=> configs/ is unusual, src/ may be overkill for these 2 tiny files

1) hack the client handshake to not leak the clock to the server
set it to all zeros or something cute or something random
=> not sure I find this reasonable or significant enough to bother, KISS!

2) allow users to pass certs for custom verification
=> maybe useful

3) add HTTP GET request to avoid network fingerprinting
=> not sure I see the need for this feature

5) daemonize and regularly slam the clock
=> crontab can do this very nicely already, again KISS?

6) skew the clock rather than slamming it
=> I'd rather keep it simple ;-)

7) drop privs earlier
=> we now do VERY little with privs ;-) I think this is done, and without libcap!

8) audit the code for show stopping bugs
=> I'm happy ;-)

9) make this work with Tor in a proxy safe manner (no DNS mode)
=> Again, fails with the racket, otherwise user can pass IP already, or not?

10) pin SSL certs for racket mode
=> not even sure what you mean by this

11) verification of remote certificate for Tor nodes
=> Not sure why / what this is supposed to be.

13) account for servers that do not send UTC (Microsoft sends local time)
=> Ugh. How?

14) port to nss, gnutls, yassl and other libraries
=> I'm against this; if you have 4+ versions of tlsdate against 3 libs it means you get to audit much more code and your have to warn your users against security issues in any of the possible dependencies; what good reason is there to have 4+ backends for this!?

15) starttls support (smtp, pop, imap, ftp, xmpp)
=> works fine with imaps for me, what do you mean?

16) ensure that 32bit time isn't near wrapping time on 32bit systems
=> I think we have that, right?

17) find others to audit it - we need more eyes!
=> always good...