rotating the keys quicker than they can be exfiltrated, and expanded. similar to the original reason password rotation exists - that the hashes of passwords to

rotating the keys quicker than they can be exfiltrated, and expanded. similar to the original reason password rotation exists - that the hashes of passwords to all users were known to all parties, and were assumed cracked after a certain timeframe - passwords were required to be changed before that cyclic window. similarly, captcha's for high-sensitive sites embed the domain in the captcha, and only allow the captcha for a small timeframe. it then has a delay to show/fetch the captcha challenge, and must be completed/expires quickly. this reduces the chance of a MitM attack or a phishing attack to nil. ultimately, if you want to prevent information leakage, you'll have to create a event horizon surrounding the secret. and even then, Hawking predicts that black holes sweat, so even then, your 2^^8^^8 key is still derivable from collecting and de-entrophizing the sweated muons of a photon-sphere. *: unless you use reversible computing to generate the secret, then reverse the computation, but keep the result. this prevents people in the future from collecting information on current wave-states, barring entanglement.