Thanks, Ludwig. The list of steps below help me to understand the concern. ----
1.) C obtains token and pop-key from AS 2.) C transmits token to RS and sets up secure communication (e.g. DTLS-PSK) using the pop-key 3.) C sends secure requests to the RS 4.) token expires, an attacker manages to get hold of the pop-key 5.) C continues to send requests containing sensitive information to the RS , attacker can now read the messages and spoof positive responses from the RS. C never notices that the token is invalid and that it is actually talking to the attacker. ---- In step (4) you tie the expiry of the token to the attacker getting hold of the key. What happens if the attacker gets hold of the pop key before the token expires? Additionally, if you use DTLS/TLS just having the PoP key still requires the attacker to run a new DTLS/TLS handshake with the RS. It would also be useful to know where the attacker got the PoP key from and how you can even detect the compromise. Additionally, there is the question why the RS wouldn't stop communicating if the token expired since it has that information. Normally, the idea is that the RS has a protected resource and the client wants to access it. That's why the RS is asking the client to send a token that gives it access. Ciao Hannes IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
