內容簡介
**總結:**
Onionify 是一個獨立的外掛，讓 WordPress 網站能夠無縫地通過洋蔥服務（.onion）運作。該外掛並非 Tor Project 的聯盟或認可。
**問題與答案:**
1. Onionify 是什麼？
- Onionify 是一個讓 WordPress 網站能夠無縫地通過洋蔥服務（.onion）運作的獨立外掛。
2. Onionify 是否與 Tor Project 有聯繫？
- 這個外掛並非 Tor Project 的聯盟或認可。
3. Onionify 添加了哪些安全標準和合規集成？
- Onionify 會在 .onion 請求到達時，重新編寫運行時 URL，防止可能將洋蔥訪客暴露在 clearnet 的標準重定向，選擇性地添加官方 Onion-Location HTTP header，並為洋蔥流量應用額外的隱私強化措施（CSP、COEP、oEmbed 和資源提示控制）。
4. Onionify 的特點有哪些？
- 檢測 .onion 請求，安全地在運行時重新編寫生成的 WordPress URL 到配置的洋蔥主機。
- 不修改數據庫的 home 或 siteurl 值 - 所有重寫僅在運行時執行。
- 提供對多站點的支持：每個網站的洋蔥映射（通過網絡管理員）和可配置的網絡默認值。
- 選擇性地從 clearnet 網站發送 Onion-Location header，以幫助瀏覽器識別洋蔥鏡像。
- 為洋蔥訪客提供可選的隱私增強功能（CSP、COEP、X-Frame-Options、dis）。
外掛標籤
開發者團隊
② 後台搜尋「Onionify – Onion Service for WP」→ 直接安裝（推薦）
原文外掛簡介
Onionify is an independent plugin that enables WordPress websites to operate seamlessly through onion services (.onion).
This plugin is not affiliated with or endorsed by the Tor Project.
Onionify adds safe and standards-compliant integration for onion access – rewriting runtime URLs when requests arrive via .onion, preventing canonical redirects that might expose onion visitors to the clearnet, optionally adding the official Onion-Location HTTP header, and applying additional privacy-hardening measures (CSP, COEP, oEmbed and resource hints control) specifically for onion traffic.
The plugin follows WordPress.org guidelines and is designed for secure public distribution:
No modifications to WordPress core.
Uses WordPress filters and actions only.
Fully compatible with multisite environments (per-site mappings and network defaults).
Optional WP-CLI integration for advanced administration.
⚠ IMPORTANT WARNING
⚠ Warning: This plugin does not provide hosting-level anonymity or concealment of infrastructure. Onionify helps WordPress handle requests that arrive via onion service addresses, but it does not change or hide server configuration, hosting provider information, or other infrastructure-level metadata. If you require infrastructure-level protections or specialized operational procedures, consult authoritative technical documentation and qualified operational security professionals. Do not rely on this plugin for legal compliance or for anonymizing hosting details.
Features
Detects .onion requests and safely rewrites generated WordPress URLs to the configured onion host at runtime.
Does not modify database home or siteurl values – all rewrites occur at runtime only.
Multisite support: per-site onion mapping (via Network Admin) and configurable Network Defaults.
Optionally sends the Onion-Location header from the clearnet site to help browsers recognize the onion mirror.
Optional privacy enhancements for onion visitors (CSP, COEP, X-Frame-Options, disable oEmbed, and tighten resource hints).
Optional verification feature using a public list of known Tor exit addresses (opt-in only).
Includes WP-CLI commands to list, map, and manage onion host configurations.
Provides filter hooks for extensibility (including onion_is_onion_request and onion_verify_exit_list).
Carefully validated, defensive code compatible with PHP 7.4 – 8.x.
Quick usage (WP-CLI)
wp tor-onion list – show mapping table (multisite) or single-site status.
wp tor-onion map
wp tor-onion set --hardening=on|off --oembed=on|off --csp=strict|relaxed|off – quick toggles.
Settings explained (concise + clear)
.onion domain – Host only, no protocol. Example: abcd1234xyz.onion. Leave empty to use Network Default (multisite).
Send Onion-Location from clearnet – When enabled, the plugin adds an Onion-Location: http://
Enable onion hardening – When enabled, headers and filters designed to reduce external resource loading (and privacy leakage) are applied to requests only when served via .onion.
Disable oEmbed/embeds on .onion – Blocks automatic fetching of oEmbed content (YouTube, Twitter, etc.) and discovery links to avoid loading third-party resources for onion visitors.
CSP mode – Strict, Relaxed, Off, Custom.
Strict – safest. No inline scripts. Best for privacy; may break themes/plugins that rely on inline JS.
Relaxed – allows inline scripts/styles ('unsafe-inline'), useful for older themes.
Off – plugin does not send a CSP header.
Custom – plugin will send exactly the policy you place into the Custom CSP text box. Only use if you understand CSP syntax.
Custom CSP – clear guidance
The Custom CSP field is used only when CSP mode is set to Custom.
Enter the policy exactly as you want it sent. Examples below – copy/paste if needed:
1) Minimal secure WordPress (no external CDN):
default-src 'self';
script-src 'self';
style-src 'self' 'unsafe-inline';
img-src 'self' data:;
font-src 'self' data:;
connect-src 'self';
frame-src 'self';
frame-ancestors 'self';
base-uri 'self';
form-action 'self';
2) Relaxed (allows inline JS):
default-src 'self';
script-src 'self' 'unsafe-inline';
style-src 'self' 'unsafe-inline';
img-src 'self' data:;
font-src 'self' data:;
connect-src 'self';
frame-src 'self';
3) If you must use an external CDN – add only the exact host(s):
img-src 'self' https://cdn.example.com data:;
font-src 'self' https://cdn.example.com data:;
Tips & cautions:
– Start with Strict; if things break (admin bar, theme JS), switch to Relaxed.
– Use Custom only if you know CSP; incorrect CSP can break admin, media, or login.
– Avoid including public CDNs in onion mode where possible – best privacy practice is to host assets locally.
Multisite behavior
Per-site mapping: Network Admin → Onionify allows mapping each blog_id → onion host.
Network Defaults: Network Admin → Onionify → Network Defaults lets you set default values (default onion host, default CSP mode, default hardening toggles) that sites inherit unless they override locally.
Precedence: Per-site explicit setting → Network Default → Plugin internal default.
Filters & constants (developer)
apply_filters('onion_is_onion_request', bool $is_tor, array $server)
Allows other plugins/themes to override detection. $server is a copy of $_SERVER.
apply_filters('onion_verify_exit_list', bool $default)
Controls whether the plugin will verify IPs against the Tor exit list. Disabled by default.
define('TOS_VERIFY_TOR_EXIT', true); – alternative to enable exit-list verification in wp-config.php.
onion_support_* option names used by the plugin: see Settings page. The plugin cleans up these options on uninstall.
If you do not want automatic cleanup, do not use the admin “Delete” action; deactivate only.
Privacy, security, and limitations (be explicit)
This plugin only adjusts WordPress behavior (URL outputs, selected headers, CSP, and resource hint handling) based on how visitors access the site (clearnet vs .onion).
It does not anonymize or conceal server infrastructure details. Information such as hosting provider IP addresses, DNS records for clearnet domains, or other infrastructure-level metadata remains unchanged. Onionify is not designed or intended to provide anonymity or infrastructure concealment.
Enabling the optional exit-address verification feature performs external HTTP requests to a trusted public source (only when explicitly opted in). If your hosting environment restricts outbound HTTP requests, use the WP-CLI interface or wp-config.php configuration after verifying your allowed hosts.
The plugin operates with a privacy-first design: external requests are disabled by default, and its default configuration aims to reduce unnecessary third-party requests for onion visitors.
External services
This plugin can optionally fetch the official Tor exit relay list to verify requests against Tor exits.
Service: Tor Project – Exit addresses list
Endpoint: https://check.torproject.org/exit-addresses
What it is used for: When exit verification is enabled, the plugin downloads the public list of Tor exit relays to check inbound requests.
What data is sent and when: The plugin performs a normal HTTP GET request from the server to the Tor Project endpoint. No user PII is sent; the request includes a generic User-Agent header and, as with any HTTP request, the server’s IP address is visible to the Tor Project. This request happens at most once per 24 hours due to caching and only if exit verification is enabled by the site owner.
How to enable/disable: Exit verification is opt-in. It is disabled by default. It can be enabled via the plugin settings or by adding define(‘TOS_VERIFY_TOR_EXIT’, true) in wp-config.php. If your environment blocks external HTTP requests (WP_HTTP_BLOCK_EXTERNAL), the plugin will respect that unless the host is whitelisted in WP_ACCESSIBLE_HOSTS.
Provider policies: See the Tor Project privacy policy and terms on their official website.
Support
Use the WordPress.org support forum for the plugin. For commercial help or customizations contact https://infinitumform.com/.
