Presumably, OpenDNS is using its own tech - so I would therefore like to know, as a matter of customer convenience and security, *when* the development and release schedule from OpenDNS for releasing its production DNSCrypt-Proxy daemon (or even an executable) will be made public in order that special characters can be used in OpenDNS account passwords (i.e. e.g. transmitted over HTTPS/SPDY using encryption) - broadening the character space for OpenDNS passwords, and mitigating the risk of a breach on your backhaul? Open source community development on dnscrypt-proxy is in quite a sorry state.
Experience has taught us we need the entire UTF-8 character space available for passwords as an elemental aspect of security. Without this, mark me - and this post - that your being compromised by a third party is, on the balance of probabilities, simply a matter of time. Note: as at time of posting, Google is far from completing their inter-datacenter encryption infrastructure.
I am aware you've basically got 1, maybe 2, people working on dnscrypt-proxy - I humbly suggest you consider re-allocating HR to focus much more and with considerable urgency on DNScrypt Proxy.
N.B.: Can you please make a note on my account to keep me advised of internal progress (not merely Github) on DNSCrypt-Proxy - in return I shall offer, if you'd like, to test your dev work periodically.
Take care and thanks once again.
Please sign in to leave a comment.