diff options
author | Nick Mathewson <nickm@torproject.org> | 2023-10-14 19:10:56 -0400 |
---|---|---|
committer | Nick Mathewson <nickm@torproject.org> | 2023-10-14 19:10:56 -0400 |
commit | 4ebef6db0a7c4acddba4192f836592cfe8f421ee (patch) | |
tree | 90ffb787499f7bd7249652bbf87ca5fb1590aec2 /spec/gettor-spec.md | |
parent | 81e888dca8d971948eff15e3acc4e61cbdfa1b99 (diff) | |
download | torspec-4ebef6db0a7c4acddba4192f836592cfe8f421ee.tar.gz torspec-4ebef6db0a7c4acddba4192f836592cfe8f421ee.zip |
Enforce the rule that no document has multiple top-level headings.
Diffstat (limited to 'spec/gettor-spec.md')
-rw-r--r-- | spec/gettor-spec.md | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/spec/gettor-spec.md b/spec/gettor-spec.md index 446f116..337413d 100644 --- a/spec/gettor-spec.md +++ b/spec/gettor-spec.md @@ -4,13 +4,13 @@ Jacob Appelbaum <a id="gettor-spec.txt-0"></a> -# Preface +## Preface This document describes GetTor and how to properly implementation GetTor. <a id="gettor-spec.txt-1"></a> -# Overview +## Overview GetTor was created to resolve direct and indirect censorship of Tor's software. In many countries and networks Tor's main website is blocked and @@ -24,7 +24,7 @@ methods such as SMTP between a non-trusted third party or with IRC and XDCC. <a id="gettor-spec.txt-2"></a> -# Implementation +## Implementation Any compliant GetTor implementation will implement at least a single transport to meet the needs of a certain class of users. It should be i18n and l10n @@ -38,13 +38,13 @@ per transport basis. <a id="gettor-spec.txt-2.1"></a> -## Reference implementation +### Reference implementation We have implemented\[0\] a compliant GetTor that supports SMTP as a transport. <a id="gettor-spec.txt-3"></a> -# SMTP transport +## SMTP transport The SMTP transport for GetTor should allow users to send any RFC822 compliant message in any known human language; GetTor should respond in whatever @@ -55,7 +55,7 @@ descriptions. <a id="gettor-spec.txt-3.1"></a> -## SMTP transport security considerations +### SMTP transport security considerations Any GetTor instance that offers SMTP as a transport should optionally implement the checking of DKIM signatures to ensure that email is not forged. @@ -64,7 +64,7 @@ response with a blinded message. <a id="gettor-spec.txt-3.2"></a> -## SMTP transport privacy considerations +### SMTP transport privacy considerations Any GetTor instance that offers SMTP as a transport must at least store the requester's address for the time that it takes to process a response. This @@ -78,14 +78,14 @@ information about any of the requester beyond language selection. <a id="gettor-spec.txt-4"></a> -# Other transports +## Other transports At this time no other transports have been specified. IRC XDCC is a likely useful system as is XMPP/Jabber with the newest OTR file sharing transport. <a id="gettor-spec.txt-5"></a> -# Implementation suggestions +## Implementation suggestions It is suggested that any compliant GetTor instance should be written in a so called "safe" language such as Python. |