X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=TODO.txt;h=ad0c77ad276debdfda5e57395dcc3dc775a585c1;hb=a23a8cf8ee1da51c4392b9f52e6b72b0c01e3b5e;hp=25a54cf14bcca281296132b815abf4e165f19546;hpb=7db382b5b9a4fe8cdaf7b7c18a86bdb35fdf2853;p=~andy%2Ffetchmail diff --git a/TODO.txt b/TODO.txt index 25a54cf1..ad0c77ad 100644 --- a/TODO.txt +++ b/TODO.txt @@ -1,6 +1,10 @@ Note that there is a separate todo.html with different content than this. soon - MUST: +- blacklist DigiNotar/Comodo/Türktrust hacks/certs, possibly with Chrome's serial# + list? +- check if wildcards from X.509 are handled as strictly as required by + the RFCs. - audit if there are further untrusted data report_*() calls. - Debian Bug #475239, MIME decoder may break up words (need to quote results) - put bare IP addresses in brackets for SMTP (check if there are RFC @@ -62,7 +66,7 @@ questionable: - fetch IMAP message in one go (fetchmail-devel by Adam Simpkins around Nov 2nd)? -6.4: +7.0: - Properly free host/user entries (through C++ class instantiation and destructors...) - Remove stupid options, such as spambounce, or deferred bounces for anything but wrong addresses @@ -107,7 +111,6 @@ questionable: - CRYPTO: perhaps port to NSS? Check license and features and required procedure changes. - Redhat Bugs #333741 (crypto consolidation), #346891 (port fetchmail to NSS) - CRYPTO: make the SSL default v3 (rather than v23). -- CRYPTO: remove sslfingerprint? too easily abused (see NEWS) - CRYPTO: force sslcertck - CRYPTO: by default forbid cleartext or other compromising password schemes over insecure connections? @@ -173,6 +176,17 @@ questionable: does it expect, what does it get instead, what does that mean, how can the user fix it; references to the manual) +- grarpamp suggested, on the fetchmail list in later April 2013, more + config file flexibility and explicitness, by marking polls, hosts, + accounts. See thread. + +- more selection options, Debian Bug#705291. + +- add a way to specify multiple fingerprints per host + +- add a way to specify non-MD5 fingerprints per host. SHA1 can be told + from its mere length; other digest algorithms would require some sort + of prefix. We may require the prefix for SHA1, too, for clarity. DOCUMENTATION: - Add info whether Keywords are global, server or user keywords