biolizard89 wrote:

NMCSocks has some partial support for TLS, but there are no binaries, and as far as I can tell no one was able to make it build. It's discontinued, so it's doubtful that that code will be fixed/finished.I am pledging a 1 BTC bounty to the first developer to implement the TLS feature of the .bit 2.0 spec. Requirements (all must be met for the bounty to be awarded):1. TLS support implemented as described in the .bit 2.0 spec.2. Source code (under open source license) with build instructions. (Someone must be able to verify that the source code is buildable.)3. Windows binary. (Obviously Linux/OSX binaries would be awesome, but not a requirement.)4. Instructions for making it work with Firefox on Windows.5. I must be able to run the software for 1 week without crashes or other unexpected behavior.6. Must be posted on this forum.I think the centralization of the standard TLS infrastructure is a danger to the security of the Internet, and I think that .bit won't catch on if sites can't use TLS. Implementing TLS for .bit in a user-friendly way would help solve both issues.If unclaimed, this bounty will expire at 11:59PM UTC, March 31, 2013.(Warning for candidates: the latest binaries of NMCSocks crash periodically on Windows [at least for me], so if you use that code as your base, you'll need to make sure that it can meet requirement 5 above.)If clarifications are needed about what I'm requesting, just ask. (This is the first bounty I've offered, so if I've made an oversight, please point it out and I'll correct.)Thanks!EDIT: total pledges:1 BTC - biolizard891 BTC - phelix1 BTC - Namecoin Marketing and Development FundTwo two-letter .bit domains ( https://bitcointalk.org/index.php?topic=66212 ) - phelixEDIT 2: All pledges extended to July 31, 2013.