The first experience is: FreeSpeechMe works great with Tor, and it was also much easier to set up a hidden service than I thought! domob.bit and nameid.bit are both now accessible via Tor resolution, too (and as plain hidden services, obviously). Some things where I'd appreciate input:
- How to configure subdomains (in particular "www") with .onion addresses? I'm currently just using the "tor" field, but then nmcontrol only resolves getOnion for the domain without "www". Is it possible to resolve every subdomain via the same .onion, just like the "map *" thing for IP4?
- What about adding some way to FreeSpeechMe to see how the current page was resolved? One can extract it from the debug logs printed, but it would be cool for testing to just have a "Resolved by ..." tooltip or dialog or something somewhere. (But one can test by disabling non-Tor resolvers temporarily for now.)
- HTTPS and Tor do not work together when using FreeSpeechMe. I think this was pointed out already by biolizard89 some time ago and of course, TLS is redundant when using Tor, but in combination with .bit it seems not too unnecessary. I want that https://nameid.bit/ works also when using Tor resolution, and it at least ensures the user that their connection is encrypted without having to know that Tor was used and that also HTTP alone is secure.
Code: Select all
[error] Hostname 6tu4hqziyjly7fns.onion provided via SNI and hostname nameid.bit provided via HTTP are different