Privacy Pass issuer keys need a retirement and redemption plan
Privacy Pass lets a client obtain a token from an issuer and redeem it later at an origin. The design can support rate limiting, access control, or other policy decisions without requiring the origin to track the client directly. The architecture separates the client, origin, issuer, and attester, and the issuance and redemption protocols have their own trust relationships.
That separation is useful, but it creates operational questions that a simple bot-defense rollout may not answer. Which issuer is trusted? How does the origin know a token was issued for its challenge? What happens when an issuer rotates a key? How does the origin detect a token reused across independent services?…