Exercises
ex-ch17-e01
EasyVerify the STC converse: why does necessary for perfect secrecy follow from the one-time pad lower bound?
Shannon's OTP theorem: key length message length for perfect secrecy.
User must decode a full file ( bits) from .
Shannon's OTP
Perfect secrecy of -bit message requires -bit uniform key. Otherwise leakage exists.
Apply to coded caching
is independent of (secrecy). User recovers from . Hence must contain bits of key for each file decoded β .
ex-ch17-e02
EasyFor , , : compute STC secure rate and compare to non-secure MAN.
STC rate
, . .
MAN rate
. .
Penalty
Secure rate (1.5) higher than non-secure (1.0) β secrecy costs 0.5 files/use.
ex-ch17-e03
MediumShow that STC's achievable rate converges to the non-secure MAN rate as at fixed .
Compare and .
Limit
As : . Both rates approach since the shift becomes negligible.
Interpretation
Secrecy penalty vanishes at library scale. For CDN-scale libraries (), secure rate is essentially free.
ex-ch17-e04
MediumWalk through Shamir threshold sharing for a binary secret .
Polynomial of degree over or .
Users receive ; any two reconstruct.
Polynomial
with random over .
Shares
User 1: . User 2: . User 3: .
Reconstruction from users 1 and 2
Subtract: recover . Then .
Security from user 1 alone
Knowing only with uniform: remains uniform conditional on this. Zero leakage.
ex-ch17-e05
MediumA system with users, files, : is secure delivery feasible? Compute secure rate if yes.
Feasibility
feasible.
Effective memory
. .
Secure rate
files/channel-use.
Non-secure comparison
. Secure rate higher by ~10% β small penalty at this scale.
ex-ch17-e06
HardProve the STC security claim: in the STC scheme, where is the broadcast.
Keys are uniform and independent of .
XOR of uniform key with anything is uniform.
Key distribution
Each uniform on and independent of (by Shamir construction).
Broadcast masking
. Since uniform: uniform.
Independence of $\mathcal{W}$
uniform independent of everything, including . Hence .
Extending to full broadcast
Full is a concatenation of ; each independent of .
ex-ch17-e07
HardSuppose the eavesdropper has partial cache access (e.g., has compromised of users' caches). Derive the required memory overhead.
Generalize to or similar.
Adversary model
holds plus caches of users with .
Secrecy requirement
.
Shamir adjustment
Use -threshold sharing instead of : any shares still learn nothing; reconstruct. Additional share cost: shares amortization per-user memory approximately.
Generalized lower bound
for ; for fixed ratio. Degrades gracefully with .
ex-ch17-e08
MediumCompare STC with encrypting each MAN XOR with AES-128-CTR. Tradeoffs?
Info-theoretic vs computational security.
Key size and key rotation.
STC (info-theoretic)
Perfect secrecy; quantum-safe; 1 file of key material per user; key rotation per delivery.
AES-128-CTR (computational)
128-bit security; quantum-vulnerable (Grover's speedup); 16-byte key + 16-byte nonce per user; key rotation based on sequence number.
Storage
STC: bits per user (large). AES: bytes per user (tiny).
Use cases
STC: high-security applications (government, financial), post-quantum roadmap. AES: general CDN, computational security acceptable.
ex-ch17-e09
HardDesign a joint privacy + secrecy scheme for , , . Specify placement and one delivery round.
Parameters
, non-integer. Use time-sharing or round to .
Placement
MAN: each file split into 3 subfiles (for ). User caches for all . Shamir keys for each pair. Private permutation on per user.
Demands masked
.
MAN delivery on masked demands + STC masking
, then .
Decoding
Each user unmasks its messages using Shamir-reconstructed keys, then decodes via MAN. Privacy: insiders don't know for . Secrecy: eavesdropper sees uniform noise.
ex-ch17-e10
MediumExplain why decentralized caching (Ch 13) does not trivially combine with STC.
Decentralized placement: random bits, no subset structure.
STC requires keys indexed by subsets.
Decentralized structure
Each user caches random bits independently; no combinatorial subset structure to index keys by.
Key indexing challenge
STC's key-per--subset structure doesn't translate. Random access to file bits: keys must be indexed by bit position, not subset.
Workaround
Use random-placement-compatible key derivation (e.g., PRG with position as input). Loses info-theoretic secrecy; gains practicality.
Open problem
A fully decentralized, info-theoretic secure scheme with the MAN rate is an open problem as of 2024.
ex-ch17-e11
HardProve the STC converse using the cut-set argument more formally.
Consider a subset of users' cached data plus broadcast.
Use Fano + I-MMSE bounds.
Fano's inequality
For user decoding : .
Secrecy constraint
.
Decomposition
.
Conclusion
, so as .
ex-ch17-e12
MediumIn an IoT scenario with tiny sensors, each with only files of cache, is STC feasible? If not, what are alternatives?
Feasibility
STC infeasible.
Alternatives
- Hybrid TLS + MAN. TLS encryption (computational secrecy), MAN caching for bandwidth. Loses info-theoretic but works with small cache.
- Downscale security. Accept weak secrecy bound for small , trading off via weaker key material.
- Larger cache. Add flash storage to sensors.
Lesson
is fundamental. Small-cache IoT devices cannot use info-theoretic STC; must resort to computational schemes.
ex-ch17-e13
HardDerive the STC converse for the multi-eavesdropper case: eavesdroppers with independent observations that might collude.
Combined leakage: .
If all (same observation): single-eavesdropper case.
Symmetric case
If eavesdroppers observe identical : equivalent to single eavesdropper. suffices.
Independent observations
If are genuinely different (e.g., different channels): more info leaked; stricter bound. But if is secure individually, it's secure jointly.
Collusion
Colluding eavesdroppers with MAC-like observations may gain more. STC's construction extends: use larger field / stronger Shamir bounds.
Generic bound
For colluding eavesdroppers: still sufficient if we use independent keys per channel. Engineering overhead: fresh keys per round.
ex-ch17-e14
HardIn the joint privacy + secrecy scheme, is the rate exactly STC rate, or is there an additional penalty?
Privacy is free (Wan-Caire); secrecy costs 1 file.
Privacy cost
Wan-Caire: zero rate cost. Masking permutation doesn't change XOR structure.
Secrecy cost
STC: 1 file of memory. .
Joint
Rate = STC rate (only secrecy imposes rate penalty).
Moral
Combining two orthogonal security properties: pay only for the one that has cost. Layered security works.
ex-ch17-e15
MediumThe STC scheme assumes a passive eavesdropper. How should the scheme change for an active eavesdropper (can inject/modify messages)?
Active adversary: need authentication.
MAC (message authentication code) or info-theoretic authentication.
Active threat
Eavesdropper not only observes but also injects hoping users decode it as legitimate.
Authentication
Add MAC (HMAC-SHA256) per XOR message. Eavesdropper can't forge without key.
Info-theoretic authentication
Use universal hash functions (Carter-Wegman) for unconditional authentication. Additional key material: bits per message.
Cost
Authentication + STC secrecy + privacy: combined overhead dominated by the 1-file STC key. Authentication overhead is lower-order.