Level 1 — Expert — VPN Knowledge Test

1

How does REALITY protocol avoid detection by mimicking legitimate TLS handshakes?

It replays captured TLS sessions from real servers without modification It performs a real TLS handshake with an unblocked server, extracts its certificate and ServerHello, then uses those to respond to the client It generates synthetic TLS records that statistically match observed traffic patterns It tunnels through legitimate TLS sessions by hijacking their connection state

2

What is the primary difference in goals between REALITY and XTLS-Vision?

REALITY targets decoy servers while XTLS-Vision targets CDN providers only XTLS-Vision aims to hide the target SNI by peeling TLS layers; REALITY aims to make any connection look like a real handshake to a decoy server REALITY requires client certificate pinning; XTLS-Vision does not XTLS-Vision protects against passive DPI; REALITY only against active probing

3

What does uTLS provide and why is it significant for circumvention?

A Go library that implements TLS fingerprinting resistance by mimicking browser TLS client behaviors A UDP-based alternative to TLS that avoids middlebox detection entirely A certificate authority for generating self-signed certs on-the-fly A protocol that negotiates only deprecated TLS 1.0 ciphers to evade inspection

4

What is MASQUE and what capability does it enable?

An IETF working group defining mechanisms to tunnel arbitrary IP traffic over encrypted QUIC connections A DNS masking protocol that hides query content from recursive resolvers A TLS extension that encrypts SNI by rotating domain names per packet A BGP security mechanism that masks route origins from path analysis

5

What distinct capability does HTTP/3 introduce compared to HTTP/1.1 and HTTP/2?

Built-in compression of response headers using HPACK encoding Connection migration: clients can switch networks (e.g., WiFi to LTE) without dropping the connection Multiplexing of multiple requests over a single TCP connection Server push capability to proactively send resources to clients

6

What is QUIC connection migration?

The process of moving a QUIC connection state from one server to a backup replica The ability to maintain a QUIC connection across changes in client IP address or network interface using connection IDs decoupled from 5-tuple A mechanism to convert a QUIC connection into a TCP connection when UDP is blocked The protocol's method of seamlessly shifting from one encryption key to another

7

How does Encrypted Client Hello (ECH) advance beyond ESNI (Encrypted Server Name Indication)?

It encrypts the entire ClientHello message to a public key advertised in DNS, hiding not just SNI but ciphers, versions, and extensions It adds post-quantum key exchange to ESNI's SNI encryption mechanism It removes the need for DNS queries by embedding the server public key in TLS 1.2 It encrypts Client Hello only on the second handshake in a resumption

8

What is Hybrid Public Key Encryption (HPKE) and where is it applied in modern TLS?

A construction combining classical and post-quantum KEM algorithms; used in ECH and anticipated in TLS 1.3 key exchange A method of splitting the server's private key across multiple hardware tokens A mode of TLS that requires both RSA and ECDSA certificates simultaneously An optimization that reduces computational cost by using symmetric keys for initial handshakes

9

Which of the following represents a current approach to post-quantum key exchange in TLS?

Kyber/X25519Kyber768: hybrid mode negotiating both X25519 and Kyber768 in the same handshake Pure Kyber-only negotiation without classical ECDH to ensure strongest security Sequential handshakes where Kyber is run after X25519 agreement completes Kyber key establishment only on resumption, not on full handshake

10

What is CRYSTALS-Kyber at a high level?

A post-quantum key encapsulation mechanism (KEM) based on lattice problems, standardized as ML-KEM by NIST A symmetric cipher suite designed as a drop-in replacement for AES-256 A QUIC congestion control algorithm optimized for satellite links A cryptographic hash function derived from Keccak for post-quantum signatures

11

How do BGP route leaks differ from BGP hijacks in intent and mechanism?

Route leaks are intentional attacks; hijacks are unintended misconfigurations that leak prefixes to unauthorized neighbors Hijacks are intentional takeovers of prefixes; leaks are typically unintended advertisements of routes to peers they should not receive Route leaks target only individual IP addresses; hijacks target entire ASNs Leaks are prevented by RPKI; hijacks cannot be detected by any mechanism

12

What does RPKI attempt to solve and what does it validate?

It solves prefix ownership spoofing by validating that an AS is authorized to announce a specific prefix using ROAs (Route Origin Authorizations) It prevents all BGP attacks by encrypting BGP advertisements with certificates It detects in real-time whether a route is being actively hijacked on the internet It eliminates the need for AS_PATH validation by replacing it with certificate chains

13

How does DNSSEC differ from DoH and DoT in what cryptographic property it actually guarantees?

DNSSEC proves the authenticity and integrity of DNS records themselves; DoH/DoT prove only the privacy of the channel between client and resolver DNSSEC encrypts all DNS queries; DoH/DoT only authenticate the resolver identity DoH/DoT validate the zone ownership; DNSSEC does not address query privacy All three prove identical security properties but use different key types

14

What is DANE and why has its adoption remained limited?

DANE (DANE Authentication Named Entities) is a DNSSEC-based TLS certificate authentication mechanism; adoption is limited because it requires DNSSEC and DANE record publication, adding operational complexity DANE is a DNS protocol for certificate revocation; adoption is low because CRLs are already standard DANE encrypts DNS responses; low adoption because DoH and DoT already do this DANE is a TLS extension that mandates certificate pinning in DNS; it conflicts with automatic renewal

15

What is an example of a side-channel attack against TLS?

Timing analysis of decryption operations to infer plaintext length or key material A network path that bypasses the TLS handshake entirely Spoofing the server's certificate authority to issue a fake certificate A BGP hijack that reroutes TLS traffic to a malicious endpoint

16

What capability do Tor onion services provide that Tor exit nodes do not?

Bidirectional end-to-end encryption and authentication without exposing the service's IP address or requiring exit nodes Faster connection speeds by avoiding the exit node bottleneck The ability to serve clearnet (non-Tor) clients without modification Protection against traffic analysis on the service side

17

What is a v3 onion address and why is it longer than v2?

A 56-character base32-encoded address derived from a 32-byte ed25519 public key; v2 used 16-byte RSA-1024, making v3 longer An IPv3 address format that Tor uses internally for routing; length increased for larger address space A v3 refers to Tor protocol version 3; onion length is unrelated to protocol version A longer address that includes an embedded DNSSEC signature for improved security

18

What does a circuit in Tor consist of?

A sequence of 3+ randomly selected relays through which the client's traffic is encrypted and routed in nested layers A single persistent connection from the client to a random guard relay A peer-to-peer connection between the client and one onion service A BGP path used to route traffic between Tor directory servers

19

What does WireGuard's Noise protocol framework provide?

A lean, formally verified cryptographic handshake with 1-RTT connection establishment and post-compromise forward secrecy through per-packet key rotation A protocol for noise floor reduction in VPN audio calls Authentication using biometric data stored on client devices A method for detecting and mitigating DPI-based packet inspection

20

What does Tailscale's coordination server do and not see?

It sees IP mappings and key material to facilitate NAT traversal and relay selection, but does not see packet content due to end-to-end encryption It sees and logs all traffic content for debugging purposes It sees only the geographic location of clients but not their identities It does not see IP addresses but maintains a complete audit log of all data transmitted