Skip to content

Commit c66b2ec

Browse files
committed
link syntax
1 parent 07f7667 commit c66b2ec

File tree

6 files changed

+13
-13
lines changed

6 files changed

+13
-13
lines changed

report/attacks/correlations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ Various existing research on this
44

55
"Encrypted (Network) Traffic Classification"
66

7-
* https://www.sciencedirect.com/science/article/pii/S2090447923002502
8-
* https://ieeexplore.ieee.org/document/8622812
9-
* https://www.mdpi.com/2073-8994/13/6/1080
7+
* <https://www.sciencedirect.com/science/article/pii/S2090447923002502>
8+
* <https://ieeexplore.ieee.org/document/8622812>
9+
* <https://www.mdpi.com/2073-8994/13/6/1080>
1010

1111
Does *not* depend on unencrypted SNI!

report/censorship.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22

33
## RU
44

5-
* Russia disallowing CDNs in order to block ECH: https://github.com/net4people/bbs/issues/417
6-
* https://therecord.media/russia-blocks-thousands-of-websites-that-use-cloudflare-service
5+
* Russia disallowing CDNs in order to block ECH: <https://github.com/net4people/bbs/issues/417>
6+
* <https://therecord.media/russia-blocks-thousands-of-websites-that-use-cloudflare-service>
77

88
## CN
99

@@ -15,7 +15,7 @@
1515
## KR
1616

1717
- Blocking by SNI:
18-
- https://www.bleepingcomputer.com/news/security/south-korea-is-censoring-the-internet-by-snooping-on-sni-traffic/
19-
- https://www.technadu.com/south-korea-extend-site-blocking-snooping-sni/58125/
18+
- <https://www.bleepingcomputer.com/news/security/south-korea-is-censoring-the-internet-by-snooping-on-sni-traffic/>
19+
- <https://www.technadu.com/south-korea-extend-site-blocking-snooping-sni/58125/>
2020
- Workaround: VPNs and ESNI
2121
- ESNI was removed from browses, ECH follows but harder to adopt

report/clients/browsers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ SOCKS, HTTPS
2323
Downloaded via HTTP but signed by the CA
2424
Blocking the access to the lists is possible with packet inspection due to the traffic being unencrypted
2525
Browser soft-fail by default
26-
OCSP is dead: https://letsencrypt.org/2022/09/07/new-life-for-crls/
26+
OCSP is dead: <https://letsencrypt.org/2022/09/07/new-life-for-crls/>
2727
Work ongoing to fix these issues
2828

2929
### QUIC and SPDY

report/clients/tor.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,6 @@ TOR’s architecture is designed to enhance security and privacy, which mitigate
55
Contrary to Do53 and DoH, TOR employs an alternative approach, utilizing DNS over the TOR network and subsequently through the exit node.
66
TOR inherently addresses the concerns that both DoH and ECH aim to resolve, particularly through its TOR onion services.
77

8-
- Detailed explanation on TOR's non-usage of DoH can be found here: https://lists.torproject.org/mailman3/hyperkitty/list/tor-dev@lists.torproject.org/thread/6GDO7CYEFIKID7QQCRVYVFNIVETWWWWY/#6ZBFGNSRPWRCEO7PVPSHHVLAOGF7KN3C
9-
- Discussion on DNS over HTTPS (DoH) in TOR: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/30753
10-
- Discussion on Encrypted ClientHello (ECH) in TOR: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42144
8+
- Detailed explanation on TOR's non-usage of DoH can be found here: <https://lists.torproject.org/mailman3/hyperkitty/list/tor-dev@lists.torproject.org/thread/6GDO7CYEFIKID7QQCRVYVFNIVETWWWWY/#6ZBFGNSRPWRCEO7PVPSHHVLAOGF7KN3C>
9+
- Discussion on DNS over HTTPS (DoH) in TOR: <https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/30753>
10+
- Discussion on Encrypted ClientHello (ECH) in TOR: <https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/42144>

report/deployment/incentives.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Various organizations that address humans in countries and regions with oppressi
99
In all regions, the same applies to whistle-blower platforms which are possible under close observation by political, legal or corporate organizations.
1010
## Malware - C2 operators
1111

12-
Unencypted SNI/Client Hello and TLS Metadata (cipher suite lists, advertised extensions) are being used to identify malware-generated traffic, e.g.: https://blogs.cisco.com/security/detecting-encrypted-malware-traffic-without-decryption
12+
Unencypted SNI/Client Hello and TLS Metadata (cipher suite lists, advertised extensions) are being used to identify malware-generated traffic, e.g.: <https://blogs.cisco.com/security/detecting-encrypted-malware-traffic-without-decryption>
1313
Therefore operators of malware networks have an interest in staying stealthy and thus implementing ECH. Consequently, this will hinder these traffic-analysis.
1414

1515
Currently, the usage of ECH is very low and thus in itself suspicious. To hide their ECH traffic, malware operators may be inclined to increase the general usage of ECH.

report/deployment/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Typically, DoH servers communicate with authoritative DNS servers using traditio
3535
- Which entity handles the rotation of these keys and reloads the web server configuration?
3636
- What component creates (or services) the WKECH directory, ensuring only public keys are exposed and private keys remain secure?
3737
- How is the ZF triggered after each key rotation, ideally operating separately on a different host?
38-
- For documentation, refer to: https://github.com/defo-project/ech-dev-utils#user-content-server-details.
38+
- For documentation, refer to: <https://github.com/defo-project/ech-dev-utils#user-content-server-details>.
3939

4040
## Complexity of Configuring the Zone Factory
4141

0 commit comments

Comments
 (0)