Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
83 changes: 83 additions & 0 deletions docs/en/blog/posts/2026-campus-tor-relay-template-kit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,83 @@
---
date: 2026-05-21
authors:
- toomore
categories:
- Community
- News
slug: 2026-campus-tor-relay-template-kit
image: "assets/images/post-update.png"
summary: "NZ has turned the NTNU campus Tor Relay rollout — proposal, outreach emails, deployment setup, FAQ — into a CC-BY 4.0 template kit other universities can adapt."
description: "NZ has turned the NTNU campus Tor Relay rollout — proposal, outreach emails, deployment setup, FAQ — into a CC-BY 4.0 template kit other universities can adapt."
---

# Campus Tor Relay templates: proposal, SOP, and FAQ now published

![Campus Tor Relay template kit](./assets/images/post-update.png){style="border-radius: 10px;box-shadow:1px 1px 0.6rem #00aeff;"}

In November 2025, the first campus Tor Relay in Taiwan went live at National Taiwan Normal University's CSIE department. Over the past six months, community member NZ (Su En-Li) — the student who pushed the proposal through — worked with the community to turn that experience into a reusable template kit. The three documents are now published under CC-BY 4.0, with a long-form interview as the entry point.

The templates are ready. The next step is for more universities to take them up.

<!-- more -->

## The template kit

Three documents cover the three roles in the rollout sequence: proposal author, technical operator, and the university administration team that gets asked questions.

!!! note "English translation status"

The three community documents below are currently only available in Mandarin. The Mandarin originals are the authoritative source and carry the full Taiwan-specific legal annotations. English versions will be added in a follow-up release.

- **Proposal template** (school-facing document, four outreach email patterns, two-month administrative timeline): [https://anoni.net/docs/zh-tw/community/campus-tor-relay-proposal/](https://anoni.net/docs/zh-tw/community/campus-tor-relay-proposal/){target="_blank"}
- **Deployment SOP** (torrc, UFW, status page architecture, monitoring runbook, IPv6, handover): [https://anoni.net/docs/zh-tw/community/campus-tor-relay-sop/](https://anoni.net/docs/zh-tw/community/campus-tor-relay-sop/){target="_blank"}
- **FAQ for university administration and legal counsel** (ten questions with Taiwan-specific annotations, plus two one-page summaries): [https://anoni.net/docs/zh-tw/community/campus-relay-faq/](https://anoni.net/docs/zh-tw/community/campus-relay-faq/){target="_blank"}

The hub page collects all three with case studies, project goals, and a backlog of external resources awaiting translation:

- [Tor Relay 校園建立研究專題](https://anoni.net/docs/zh-tw/community/relay-on-campus/){target="_blank"}

## For readers outside Taiwan

The case is grounded in Taiwan's TANet (the academic network) and Taiwanese legal context, but the kit transfers in pieces:

- The **proposal template's structure** — scope, technical resources, operational responsibility, legal positioning, academic value — is reusable across jurisdictions
- The **outreach email examples** show the registers that worked when approaching IT departments and faculty advisors; useful as a tone reference even when the local language and legal context differ
- The **torrc, UFW, and monitoring setups** in the SOP are jurisdiction-agnostic, and the graduation-handover discussion applies to any campus where students will eventually leave
- The **FAQ's Taiwan-specific legal annotations** need to be replaced with local equivalents, but the question structure of "what the university actually worries about" is the more portable part

If your university already runs a relay through EFF's Tor University Challenge program, we'd be glad to compare notes, particularly on how you handled the handover problem.

## Why Taiwan still needs more campus relays

Tor's anonymity rests on relay diversity. When relays concentrate in a few countries or network providers, the network's ability to resist traffic analysis weakens. Taiwan's relay count on Tor Metrics is still limited, and each stable node adds another margin of resistance. Real-time observation:

- [Tor Relays watcher](https://anoni.net/docs/zh-tw/taiwan/tor-relay-watcher/){target="_blank"}

University campuses are a reasonable place to close that gap: stable academic bandwidth, students and staff with the skill to operate the node, a clearer institutional review path than residential or small-company hosting, and direct alignment with EFF's [Tor University Challenge](https://toruniversity.eff.org/){target="_blank"}.

Taiwan's civil society has been raising attention to whistleblower protection, anti-stalking, and press freedom, areas where Tor's value to local users tracks with the global picture. A campus relay is the concrete contribution of "making this infrastructure usable in Taiwan," closer to the actual situation than an abstract statement about privacy.

## NZ's original materials

The templates are placeholder-scrubbed, sanitised versions. If you want to see what the real submission looked like, NZ has made the original Google Drive folder fully public:

- [NZ's original Google Drive folder](https://drive.google.com/drive/folders/1B9ysi2ELC9w46bD3o7TMsnv55nupI1nz){target="_blank"}

It contains the original NTNU project proposal (Google Doc), the slide deck from the December 21, 2025 on-campus sharing session, and on-site photos. The original Doc still carries NZ's personal email, advisor information, and the university's IP range. Please don't fork the raw Doc, change the school name, and submit it — it's easy to spot during review. The value of the archive is for comparing structure and wording. When you actually submit, use the placeholder-scrubbed templates on anoni.net.

The Taiwan case is also documented in English on the Tor Project blog, with NZ's first-hand account:

- [Setting up a Tor Relay at a university in Taiwan](https://blog.torproject.org/setting-up-tor-university-relay-taiwan/){target="_blank"}

The full long-form Mandarin interview with NZ on anoni.net covers the year-long arc through the proposal process. If you read Mandarin, this is the most complete record:

- [在台師大架設 Tor Relay:一段與學校溝通、留下可能性的實作經驗](https://anoni.net/docs/zh-tw/blog/posts/ntnu-nz/){target="_blank"}

## Acknowledgements

The kit's source materials were contributed by NZ (Su En-Li), drawn from his proposal, communication records, and operational experience at NTNU. NZ released the materials under CC-BY 4.0 as a template for other universities to adapt.

Every campus relay that goes live lowers the cost for the schools that follow. If you adapt the kit and roll out a relay at your university, in Taiwan or elsewhere, we'd be glad to hear about it. We can fold your case into the project page so the next wave has more reference points.

The template kit is a shared starting point. Any university can pick it up, rewrite it, and route it through its own internal review. The more schools take part, the more the shared template library grows, and the easier the work becomes for the ones who follow.
90 changes: 90 additions & 0 deletions docs/zh-TW/blog/posts/2026-campus-tor-relay-template-kit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,90 @@
---
date: 2026-05-21
authors:
- toomore
categories:
- 社群
- 公告
slug: 2026-campus-tor-relay-template-kit
image: "assets/images/post-update.png"
summary: "NZ 把台師大校園 Tor Relay 的提案計畫、溝通 email、技術設定、踩雷整理成三份 CC-BY 4.0 範本,給想響應的學校直接拿去用。"
description: "NZ 把台師大校園 Tor Relay 的提案計畫、溝通 email、技術設定、踩雷整理成三份 CC-BY 4.0 範本,給想響應的學校直接拿去用。"
---

# 校園 Tor Relay 範本工具包:提案、SOP、FAQ 三份範本上線

![校園 Tor Relay 範本工具包](./assets/images/post-update.png){style="border-radius: 10px;box-shadow:1px 1px 0.6rem #00aeff;"}

2025/11,台灣第一個校園 Tor Relay 在台師大資工系上線。社群這半年想把這段過程、「跟學校溝通、走 TANet 行政流程、技術部署、長期維運」的經驗整理成其他學校可以直接拿去用的文件,不要再讓每一所學校的學生從零開始摸索。

社群夥伴 NZ(蘇恩立)這半年陸續把當時的計畫書、溝通 email、技術設定、踩過的雷整理出來,跟社群一起改寫成可複製範本。三份範本目前都已經上線,並以 CC-BY 4.0 授權釋出,搭配[台師大案例訪談](./ntnu-nz.md)當入口。

範本已經齊了。接下來,希望能有更多學校一起響應。

<!-- more -->

## 範本工具包:三份檔案接力

工具包分三份,對應推動 Tor Relay 過程中三個不同角色的需求。

**[校園 Tor Relay 提案範本](../../community/campus-tor-relay-proposal.md)**:一份完整的「Tor University Challenge at <學校名>」提案計畫書、四封對外溝通 email(給指導教授、資訊中心網路組組長、系上網管申請主機/IP、對外開放 port 申請)、台師大實際走過的兩個月行政時間軸,以及提案前的準備清單與踩雷提醒。所有放在 `<placeholder>` 裡的欄位都標出來,複製出去把學校名、系所、IP 段、教授姓名填進去就能送進審核流程。

**[校園 Tor Relay 架設 SOP](../../community/campus-tor-relay-sop.md)**:提案通過、拿到機房位置與 IP 之後的技術部署文件。內容包含 torrc 參考設定(ContactInfo、Non-Exit 宣告、頻寬上限、MetricsPort 安全提醒)、UFW 防火牆設計(SSH 限校內 VPN 段、ORPort 9001 對外開放)、對外狀態網頁兩種架構選擇(Nginx + Onionoo 推薦,或 MetricsPort + Prometheus + Grafana)、監控與事件處置 runbook、IPv6 設定、畢業後交接清單。

**[校園 Tor Relay:給校方與法務的 FAQ](../../community/campus-relay-faq.md)**:十題校方資訊中心、法務、網管最常擔心的問題,每題都有台灣脈絡補充,刑法妨害電腦使用罪章、個資法第 2 條、TANet 對外連線審核機制都已經對到具體條文。頁尾另外整理「給網管的一頁摘要」與「給校方行政與法務的一頁摘要」,30 秒讀完,可以直接複製貼進 mail 開頭或當會議 handout。

三份檔案的整體入口、推動目標、案例累積,以及「待翻譯延伸閱讀」清單,都收在 [Tor Relay 校園建立研究專題](../../community/relay-on-campus.md)。

## 建議的閱讀順序

依角色挑切入點,省下繞路時間。

- **還在評估「該不該做」**:先讀[台師大案例訪談](./ntnu-nz.md),對全貌有感再決定
- **想推動但沒寫過提案**:提案範本 → FAQ → SOP。提案前先把 FAQ 讀完,被問到才不會答不上來
- **提案已通過、要開始裝**:直接跳 SOP,搭配[「如何搭建 Tor Relay」](../../community/setup-tor-relay.md)的個人 operator 視角補完基礎
- **單純被校方問到 Tor Relay**:把 FAQ 頁尾的兩份一頁摘要直接轉貼給對方

## NZ 公開釋出的原始素材

範本是 placeholder 化、去掉個人資訊的乾淨版本。如果你想看「真實案例長什麼樣」,NZ 把當時的原始 Google Drive 資料夾整份公開:

- [NZ 原始 Google Drive 資料夾](https://drive.google.com/drive/folders/1B9ysi2ELC9w46bD3o7TMsnv55nupI1nz){target="_blank"}

裡面包含台師大原版專案計畫說明書(Google Doc)、2025/12/21 校內分享 slides、現場照片。原始 Doc 裡有 NZ 個人 email、指導教授資訊、學校 IP 段等具體欄位,請不要直接 fork 原始 Doc 改學校名就送出去,容易在送件時被識破。原始存檔的價值是讓你對照寫作結構、用語拿捏,動手時還是用 anoni.net 上 placeholder 化過的範本。

英文版的案例脈絡,也已經刊在 Tor Project 官方部落格,國際同行看得到台灣這條線:

- [Setting up a Tor Relay at a university in Taiwan](https://blog.torproject.org/setting-up-tor-university-relay-taiwan/){target="_blank"}

## 為什麼台灣需要更多校園 Tor Relay

Tor 網路的匿名性靠多元的中繼節點支撐。當全球中繼集中在少數國家或少數網路供應商,Tor 對抗流量分析的能力就會降低。台灣目前在 Tor Metrics 上能觀測到的中繼數量仍然有限,每多一個穩定運作的節點,整個網路對抗流量分析的能力就多一分。即時觀測見 anoni.net 的 [Tor Relays 觀測點](../../taiwan/tor-relay-watcher.md)。

大學校園是補上這個缺口的合適切入點:

- **頻寬與人才**:學術網路頻寬穩定,資工、資管、資訊中心的師生有架設與維運能力,畢業交接也比個人架設容易延續
- **制度路徑清晰**:學校有正式的提案與審核流程,比個人或小公司架設更容易說清楚「誰負責、出事找誰」
- **教育與國際接軌**:架設過程本身是匿名網路、資安、開源治理的教學場景,並對接 EFF [Tor University Challenge](https://toruniversity.eff.org/zh-tw/){target="_blank"} 全球計畫

同時,台灣社會近年對揭弊者保護、家暴與跟蹤騷擾防制、新聞自由的關注持續上升,Tor 對這些情境的價值跟全球趨勢一致。校園 Relay 是「讓這套基礎設施在台灣可用」的具體貢獻。它的意義在於讓真正需要的人能順利使用,比抽象的隱私倡議更貼近實際處境。

## 號召:在台灣的大學生、社團、系所

如果你符合以下任一條件,特別歡迎加入:

- **資工、資安、資管、電機、網路相關系所的學生**:你的技術背景剛好,跟指導教授或系上網管討論起來不會有溝通落差
- **校內資安、開源、Linux、網路相關社團**:社團 email 與長期維運分工,正好補上「畢業交接」這個校園 Relay 最常斷掉的環節
- **指導教授、實驗室助理、資訊中心的教職員**:你掛名能讓提案順利不少。學校行政體系對「有教授掛名」的提案接受度普遍更高
- **正在找專題題目或修網路、資安課程的同學**:Tor Relay 架設本身就是完整的網路、系統管理、政策溝通實作題目,可以整理成專題、學位論文或 COSCUP 投稿

不需要架過 Tor Relay 也歡迎參與。「我想學」就是合理的加入動機,社群會搭配[「如何搭建 Tor Relay」](../../community/setup-tor-relay.md)文件協助你動手。

如果你正在自己學校推動、卡在某個環節想找人討論,或者已經有想法但不知道怎麼跟教授開口,任何一個階段都歡迎聯繫社群。常用入口整理在[社群自架服務](../../community/tools.md)頁面,Matrix 公開 room 也可以直接打招呼。

## 致謝

範本工具包的原始材料由社群夥伴 NZ(蘇恩立)提供,整理自他在國立臺灣師範大學的計畫書、溝通記錄、實作經驗、技術設計。NZ 同意以 CC-BY 4.0 授權釋出全部素材,作為台灣其他學校的參考範本。

每個成功上線的校園 Relay 都讓推動成本變低一點。你的案例會幫到後面響應的學校。社群會把新增的學校加進「Tor Relay 校園建立研究專題」的「已完成的事」段落,往後加入的學校可以有更多參考。

這份工具包是給想響應的學校一個共用起點,可被任何一所大學拿去、改寫、送進自己校園的審核流程。每多一所學校加入,共用範本庫就持續累積,後續推動的人會更省力。
2 changes: 1 addition & 1 deletion docs/zh-TW/blog/posts/ntnu-nz.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ description: "一位資工系學生,如何在學術網路體制內,讓匿名

!!! tip "想在自己學校也來一台?"

這篇是案例訪談,記下「**怎麼被做成**」的過程。如果你想實際在自己學校推動,請直接使用 NZ 同意公開的[**範本工具包**](../../community/relay-on-campus.md):
這篇是案例訪談,記下「**怎麼被做成**」的過程。如果你想實際在自己學校推動,請直接使用 NZ 同意公開的[**範本工具包**](../../community/relay-on-campus.md)([上線公告](./2026-campus-tor-relay-template-kit.md))

- [校園 Tor Relay 提案範本](../../community/campus-tor-relay-proposal.md):提案文件、四封溝通 email、行政時間軸
- [校園 Tor Relay 架設 SOP](../../community/campus-tor-relay-sop.md):torrc、UFW、狀態網頁、監控
Expand Down
10 changes: 5 additions & 5 deletions docs/zh-TW/community/campus-relay-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,23 +53,23 @@ icon: material/chat-question-outline

Tor 的使命是促進人權,並透過自由、開源的技術,讓使用者抵抗大規模監控與網路審查。Tor 社群對於任何將工具用於不法用途的行為,一向譴責。

請從這個角度理解這個問題:**犯罪的意圖在於人。** 工具本身不會主動製造犯罪,就像加密、電話、現金都會被惡意使用一樣。如果移除 Tor,有惡意的人會改用其他工具,並不會因此停止。
**犯罪的意圖在於人,不在工具。** 加密、電話、現金都會被惡意使用,Tor 也一樣。如果移除 Tor,有惡意的人會改用其他工具,並不會因此停止。

同時,Tor 與其他隱私工具能保護真正需要的人,包括防止身份盜竊、實體跟蹤等犯罪,也能協助執法單位調查案件、支持受害者。

**台灣脈絡補充**

台灣刑法第 358–363 條(妨害電腦使用罪章)規範的是「無故輸入他人帳號密碼」、「以電腦不正方法獲取他人電磁紀錄」等具體行為。**Middle Relay 不接觸內容、不解析使用者資料、不知道使用者身份**,在法律上跟「網路傳輸基礎設施」的性質類似,跟前述條款的犯罪行為構成要件無關。

個人資料保護法第 2 條對「個人資料」的定義是「**得以直接或間接方式識別該個人之資料**」。Middle Relay 處理的是 Tor 網路的加密 cells,**沒有可識別資料**,因此不涉及個資處理。
個人資料保護法第 2 條對「個人資料」的定義是「**得以直接或間接方式識別該個人之資料**」。Middle Relay 處理 Tor 網路的加密 cells,**沒有可識別資料**,因此不涉及個資處理。

??? question "那分散式阻斷服務攻擊(DDoS)呢?"

DDoS 攻擊通常仰賴成千上萬台電腦同時發送 UDP 封包,以癱瘓受害者頻寬。

Tor 僅傳輸正確的 TCP 連線,不傳輸所有 IP 封包。換言之,**Tor 無法傳送 UDP 封包,也無法進行 SYN Flood 等特殊攻擊**。常見的 DDoS 攻擊無法透過 Tor 完成。
Tor 僅傳輸正確的 TCP 連線,不傳輸所有 IP 封包。**Tor 無法傳送 UDP 封包,也無法進行 SYN Flood 等特殊攻擊**。常見的 DDoS 攻擊無法透過 Tor 完成。

此外,Tor 不允許頻寬放大攻擊你送進去多少資料,Tor 才會送出多少資料。若攻擊者真的擁有足夠頻寬發動 DDoS,他完全不需要依賴 Tor。
此外,Tor 不允許頻寬放大攻擊你送進去多少資料,Tor 才會送出多少資料。若攻擊者真的擁有足夠頻寬發動 DDoS,他完全不需要依賴 Tor。

**台灣脈絡補充**

Expand All @@ -81,7 +81,7 @@ icon: material/chat-question-outline

少數 Relay 可能會開啟 SMTP,但這跟架設一個開放式郵件伺服器沒有差別,並非 Tor 所造成的獨特風險。垃圾郵件發送者也可能透過 Tor 連到開放 HTTP Proxy,或利用安全性不足的 CGI 腳本寄信,甚至控制殭屍網路。事實上,他們在沒有 Tor 的情況下也能做到。

更重要的是,許多垃圾郵件技術(例如偽造的 UDP 封包)無法透過 Tor,因為 Tor 僅支援 TCP。
許多垃圾郵件技術(例如偽造的 UDP 封包)無法透過 Tor,因為 Tor 僅支援 TCP。

**台灣脈絡補充**

Expand Down
Loading