自托管暗网站点的技术挑战与需求
问题概述
在Tor隐藏服务中,用户面临性能优化、安全防护、HTTPS证书获取、电路标识追踪以及多站点端口冲突等具体技术难题,并对不同域名的必要性提出疑问。
痛点标签
- 在Tor隐藏服务中需要将资源嵌入Base64、使用内联CSS并尽量避免JavaScript,以满足性能和安全要求。
- 必须添加Onion-Location HTTP头以实现Tor浏览器的自动重定向。
- 隐藏服务的端口绑定和多服务端口冲突问题,需要使用非127.0.0.1地址和独立端口以防冲突。
- 获取HTTPS证书并启用HTTP/2多路复用以提升页面加载速度。
- 对多个隐藏站点使用不同主机名的必要性仍不明确,用户对其益处持疑问。
待验证问题
- 是否有用户对现有工具(如自动生成Onion-Locationheader的插件)的需求?
- 用户在性能优化方面最常遇到的具体瓶颈是什么?
- 目前是否有开源项目提供易于配置的多隐藏服务端口管理方案?
证据
原话 · @Anonymous
What I really love about Onion sites is that if they are big enough, performance engineering really becomes Tor-specific.
原话 · @Anonymous
My personal website has been hosted on Tor for years. It's easy to do from your home even behind a NAT because it's an outgoing connection from your point of view (which also makes it a great way to expose local services even when you are behind a NAT and don't not have a static IP), and by design your personal IP is hidden from your visitors.
原话 · @Anonymous
You probably want to add the Onion-Location header to the clearnet site so Tor Browser can automatically inform the visitor about it.
原话 · @Anonymous
Besides using a separate port, I would also suggest running the hidden service on a non-127.0.0.1 bind address, just in case you ever host something else on that port and forget to disable the hidden service:> HiddenServicePort 80 127.13.37.1:8080> listen 127.13.37.1:8080;
原话 · @Anonymous
A few more tips.1. If you want to improve page load speed you need to buy a HTTPS certificate so you are not limited to HTTP/1.1. Multiplexing in HTTP/2 is important for getting sites to load fast.
免责声明:本卡片由 AI 从社区讨论中提炼,属于「痛点证据」,是需求分析与验证的起点,不等同于「已验证的市场需求」。AI 存在分析局限,关键决策前请打开上方原始讨论人工复核。