backend/tpm: Resolve issue with TPM 2 DA lockout
cover backend/tpm: Resolve issue with TPM 2 DA lockout
This series of patches resolves an issue with a TPM 2's dictionary attack lockout logic being triggered upon well-timed VM resets. Normally, the OS TPM driver sends a TPM2_Shutdown to the TPM 2 upon reboot and before a VM is reset. However, the OS driver cannot do this when the user resets a VM. In this case QEMU must send the command because otherwise several well- timed VM resets will trigger the TPM 2's dictionary attack (DA) logic and it will then refuse to do certain key-related operations until the DA logic has timed out.
Regards,
Stefan
Stefan Berger (2):
backends/tpm: Record the last command sent to the TPM backends/tpm: Send TPM2_Shutdown upon VM reset
backends/tpm/tpm_emulator.c | 44 +++++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/tpm_util.c | 9 ++++++++ backends/tpm/trace-events | 1 + include/sysemu/tpm_util.h | 3 +++ 5 files changed, 60 insertions(+)
Signature · 1 line
2.35.3
PATCH 1/2 backends/tpm: Record the last command sent to the TPM
Record the last command sent to the TPM. Knowing the last command sent to a TPM 2 will allow us to determine whether we need to send a TPM2_Shutdown() command when the VM is reset.
--- backends/tpm/tpm_emulator.c | 9 +++++++++ backends/tpm/tpm_util.c | 9 +++++++++ include/sysemu/tpm_util.h | 3 +++ 3 files changed, 21 insertions(+)
backends/tpm/tpm_emulator.c +9 -0
@@ -81,6 +81,8 @@ struct TPMEmulator { unsigned int established_flag_cached:1;TPMBlobBuffers state_blobs; + +uint32_t last_command;/* last command sent to TPM */ };struct tpm_error {
@@ -155,6 +157,12 @@ static int tpm_emulator_unix_tx_bufs(TPMEmulator *tpm_emu, {ssize_t ret;bool is_selftest = false; +uint32_t command; + + command =tpm_util_get_ordinal (in, in_len); +if (command !=TPM_ORDINAL_NONE ) { + tpm_emu->last_command = command; + }if (selftest_done) { *selftest_done = false;
@@ -910,6 +918,7 @@ static void tpm_emulator_inst_init(Object *obj) tpm_emu->options =g_new0 (TPMEmulatorOptions,1 ); tpm_emu->cur_locty_number = ~0 ; + tpm_emu->last_command =TPM_ORDINAL_NONE ;qemu_mutex_init (&tpm_emu->mutex); vmstate_register(NULL, VMSTATE_INSTANCE_ID_ANY,
backends/tpm/tpm_util.c +9 -0
@@ -103,6 +103,15 @@ bool tpm_util_is_selftest(const uint8_t *in, uint32_t in_len)return false; } +uint32_t tpm_util_get_ordinal (const uint8_t *in,uint32_t in_len) +{ +if (in_len >=sizeof (struct tpm_req_hdr )) { +return tpm_cmd_get_ordinal (in); + } + +return TPM_ORDINAL_NONE ; +} +/* * Send request to a TPM device. We expect a response within one second. */
include/sysemu/tpm_util.h +3 -0
@@ -29,6 +29,9 @@ void tpm_util_write_fatal_error_response(uint8_t *out, uint32_t out_len);bool tpm_util_is_selftest (const uint8_t *in,uint32_t in_len); +uint32_t tpm_util_get_ordinal (const uint8_t *in,uint32_t in_len); +#define TPM_ORDINAL_NONE 0x0 +int tpm_util_test_tpmdev (int tpm_fd,TPMVersion *tpm_version);static inline uint16_t tpm_cmd_get_tag (const void *b)
Signature · 1 line
2.35.3
PATCH 2/2 backends/tpm: Send TPM2_Shutdown upon VM reset
In reply to Stefan BergerSend a TPM2_Shutdown(TPM2_SU_CLEAR) command to the TPM emulator when the VM is reset. However, this is only necessary for a TPM 2 and only if the TPM2_Shutdown command has not been sent by the VM as the last command as it would do under normal circumstances. Further, it also doesn't need to be sent if the VM was just started.
This fixes a bug where well-timed VM resets may trigger the TPM 2's dictionary attack lockout logic due to the TPM 2 not having received a TPM2_Shutdown command when it was reset.
--- backends/tpm/tpm_emulator.c | 35 +++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/trace-events | 1 + 3 files changed, 39 insertions(+)
backends/tpm/tpm_emulator.c +35 -0
@@ -389,8 +389,43 @@ err_exit:return -1 ; } +static void tpm_emulator_send_tpm2_shutdown (TPMEmulator *tpm_emu) +{ +const struct tpm2_shutdown { +struct tpm_req_hdr hdr; +uint16_t shutdownType; + } tpm2_shutdown_clear = { + .hdr = { + .tag =cpu_to_be16 (TPM2_ST_NO_SESSIONS ), + .len =cpu_to_be32 (sizeof (tpm2_shutdown_clear)), + .ordinal =cpu_to_be32 (TPM2_CC_Shutdown), + }, + .shutdownType =cpu_to_be16 (TPM2_SU_CLEAR ), + }; +Error *local_err =NULL ; +uint8_t result[10 ]; + +trace_tpm_emulator_send_tpm2_shutdown (tpm_emu->last_command); + +if (tpm_emulator_unix_tx_bufs (tpm_emu, (uint8_t *)&tpm2_shutdown_clear, +sizeof (tpm2_shutdown_clear), + result,sizeof (result), +NULL , &local_err) <0 ) { +error_report_err (local_err); + } +} +static int tpm_emulator_startup_tpm (TPMBackend *tb,size_t buffersize) { +TPMEmulator *tpm_emu =TPM_EMULATOR (tb); + +/* In case of VM reset we may need to send a TPM2_Shutdown command */ +if (tpm_emu->tpm_version ==TPM_VERSION_2_0 && + tpm_emu->last_command !=TPM_ORDINAL_NONE && + tpm_emu->last_command != TPM2_CC_Shutdown) { +tpm_emulator_send_tpm2_shutdown (tpm_emu); + } +return tpm_emulator_startup_tpm_resume (tb, buffersize, false); }
backends/tpm/tpm_int.h +3 -0
@@ -64,6 +64,7 @@ struct tpm_resp_hdr {/* TPM2 defines */ #define TPM2_ST_NO_SESSIONS 0x8001 +#define TPM2_CC_Shutdown 0x00000145#define TPM2_CC_ReadClock 0x00000181#define TPM2_CC_GetCapability 0x0000017a
@@ -71,6 +72,8 @@ struct tpm_resp_hdr {#define TPM2_PT_MAX_COMMAND_SIZE 0x11e +#define TPM2_SU_CLEAR 0x0 +#define TPM_RC_INSUFFICIENT 0x9a#define TPM_RC_FAILURE 0x101#define TPM_RC_LOCALITY 0x907
backends/tpm/trace-events +1 -0
@@ -31,3 +31,4 @@ tpm_emulator_set_state_blobs_error(const char *msg) "error while setting state b tpm_emulator_set_state_blobs_done(void) "Done setting state blobs" tpm_emulator_pre_save(void) "" tpm_emulator_inst_init(void) "" +tpm_emulator_send_tpm2_shutdown(uint32_t ord) "Sending TPM2_Shutdown(TPM2_SU_CLEAR); last ordinal from VM was: 0x%08x"
Signature · 1 line
2.35.3
Hi
Quoted 9 lines · Stefan Berger
This series of patches resolves an issue with a TPM 2's dictionary attack lockout logic being triggered upon well-timed VM resets. Normally, the OS TPM driver sends a
TPM2_Shutdownto the TPM 2 upon reboot and before a VM is reset. However, the OS driver cannot do this when the user resets a VM. In this case QEMU must send the command because otherwise several well- timed VM resets will trigger the TPM 2's dictionary attack (DA) logic and it will then refuse to do certain key-related operations until the DA logic has timed out.
How does real hardware deal with that situation? Shouldn't this "shutdown"/reset logic be implemented on swtpm side instead, when CMD_INIT is received? (when the VM is restarted)
Quoted 18 lines
Regards,
StefanStefan Berger (2):
backends/tpm: Record the last command sent to the TPM backends/tpm: SendTPM2_Shutdownupon VM resetbackends/tpm/tpm_emulator.c | 44 +++++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/tpm_util.c | 9 ++++++++ backends/tpm/trace-events | 1 + include/sysemu/tpm_util.h | 3 +++ 5 files changed, 60 insertions(+)--
2.35.3
Quoted 13 lines · Marc-André Lureau
Hi
Quoted 9 lines · Stefan Berger
This series of patches resolves an issue with a TPM 2's dictionary attack lockout logic being triggered upon well-timed VM resets. Normally, the OS TPM driver sends a
TPM2_Shutdownto the TPM 2 upon reboot and before a VM is reset. However, the OS driver cannot do this when the user resets a VM. In this case QEMU must send the command because otherwise several well- timed VM resets will trigger the TPM 2's dictionary attack (DA) logic and it will then refuse to do certain key-related operations until the DA logic has timed out.
Quoted 3 lines
How does real hardware deal with that situation? Shouldn't this "shutdown"/reset logic be implemented on swtpm side instead, when
CMD_INITis received? (when the VM is restarted)
I don't know what real hardware can actually do when the machine is reset, presumably via some reset line, or the power is removed. Probably it has no way to react to this.
Typically the OS driver has to send the command and since it cannot do this I would defer it to the TPM emulator reset handler code, so the next layer down.
Quoted 20 lines
Quoted 19 lines
Regards,
StefanStefan Berger (2):
backends/tpm: Record the last command sent to the TPM backends/tpm: SendTPM2_Shutdownupon VM resetbackends/tpm/tpm_emulator.c | 44 +++++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/tpm_util.c | 9 ++++++++ backends/tpm/trace-events | 1 + include/sysemu/tpm_util.h | 3 +++ 5 files changed, 60 insertions(+)--
2.35.3
Quoted 16 lines · Stefan Berger
Quoted 13 lines · Marc-André Lureau
Hi
Quoted 9 lines · Stefan Berger
This series of patches resolves an issue with a TPM 2's dictionary attack lockout logic being triggered upon well-timed VM resets. Normally, the OS TPM driver sends a
TPM2_Shutdownto the TPM 2 upon reboot and before a VM is reset. However, the OS driver cannot do this when the user resets a VM. In this case QEMU must send the command because otherwise several well- timed VM resets will trigger the TPM 2's dictionary attack (DA) logic and it will then refuse to do certain key-related operations until the DA logic has timed out.
Quoted 6 lines
Quoted 3 lines
How does real hardware deal with that situation? Shouldn't this "shutdown"/reset logic be implemented on swtpm side instead, when
CMD_INITis received? (when the VM is restarted)I don't know what real hardware can actually do when the machine is reset, presumably via some reset line, or the power is removed. Probably it has no way to react to this.
Typically the OS driver has to send the command and since it cannot do this I would defer it to the TPM emulator reset handler code, so the next layer down.
Also, when this is done in QEMU we don't need to do a data channel operation (run TPM2_Shutdown) from within the control channel (upon CMD_INIT) inside of swtpm. This way we can deal with it properly. The usage model for the TPM 2 prescribes that a TPM2_Shutdown must be sent before a shutdown or reset of the system, so let's let QEMU do it if the OS cannot do it.
Quoted 23 lines
Quoted 23 lines
Quoted 22 lines
Regards,
StefanStefan Berger (2):
backends/tpm: Record the last command sent to the TPM backends/tpm: SendTPM2_Shutdownupon VM reset
backends/tpm/tpm_emulator.c| 44 +++++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/tpm_util.c | 9 ++++++++ backends/tpm/trace-events | 1 + include/sysemu/tpm_util.h | 3 +++5 files changed, 60 insertions(+)Signature · 1 line
2.35.3
Hi
Quoted 37 lines · Stefan Berger
Quoted 25 lines · Stefan Berger
Quoted 19 lines · Marc-André Lureau
Hi
Quoted 14 lines · Stefan Berger
This series of patches resolves an issue with a TPM 2's dictionary attack
lockout logic being triggered upon well-timed VM resets. Normally, the OS
TPM driver sends aTPM2_Shutdownto the TPM 2 upon reboot and before a VM
is reset. However, the OS driver cannot do this when the user resets a VM.
In this case QEMU must send the command because otherwise several well- timed VM resets will trigger the TPM 2's dictionary attack (DA) logic and
it will then refuse to do certain key-related operations until the DA logic has timed out.Quoted 3 lines
How does real hardware deal with that situation? Shouldn't this "shutdown"/reset logic be implemented on swtpm side instead, when
CMD_INITis received? (when the VM is restarted)Quoted 7 lines
I don't know what real hardware can actually do when the machine is reset, presumably via some reset line, or the power is removed. Probably it has no way to react to this.
Typically the OS driver has to send the command and since it cannot do this I would defer it to the TPM emulator reset handler code, so the next layer down.
Quoted 6 lines
Also, when this is done in QEMU we don't need to do a data channel operation (run
TPM2_Shutdown) from within the control channel (uponCMD_INIT) inside of swtpm. This way we can deal with it properly. The usage model for the TPM 2 prescribes that aTPM2_Shutdownmust be sent before a shutdown or reset of the system, so let's let QEMU do it if the OS cannot do it.
What if qemu is killed or crashed, and a new instance is connected to swtpm? Or more subtle, the VM reboots without qemu help (no reset handler). It feels like it would be more robust to handle the situation in swtpm. Why not have the same last operation tracking and shutdown logic there? If CMD_INIT is received and the last operation is not shutdown, I'd have a warning and do it (if this is compliant with the spec, I am trying to find relevant text).
Quoted 25 lines
Quoted 24 lines
Quoted 24 lines
Quoted 23 lines
Regards,
StefanStefan Berger (2):
backends/tpm: Record the last command sent to the TPM backends/tpm: SendTPM2_Shutdownupon VM resetbackends/tpm/tpm_emulator.c | 44 +++++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/tpm_util.c | 9 ++++++++ backends/tpm/trace-events | 1 + include/sysemu/tpm_util.h | 3 +++ 5 files changed, 60 insertions(+)--
2.35.3
Quoted 47 lines · Marc-André Lureau
Hi
Quoted 37 lines · Stefan Berger
Quoted 25 lines · Stefan Berger
Quoted 19 lines · Marc-André Lureau
Hi
Quoted 14 lines · Stefan Berger
This series of patches resolves an issue with a TPM 2's dictionary attack
lockout logic being triggered upon well-timed VM resets. Normally, the OS
TPM driver sends aTPM2_Shutdownto the TPM 2 upon reboot and before a VM
is reset. However, the OS driver cannot do this when the user resets a VM.
In this case QEMU must send the command because otherwise several well- timed VM resets will trigger the TPM 2's dictionary attack (DA) logic and
it will then refuse to do certain key-related operations until the DA logic has timed out.Quoted 3 lines
How does real hardware deal with that situation? Shouldn't this "shutdown"/reset logic be implemented on swtpm side instead, when
CMD_INITis received? (when the VM is restarted)Quoted 7 lines
I don't know what real hardware can actually do when the machine is reset, presumably via some reset line, or the power is removed. Probably it has no way to react to this.
Typically the OS driver has to send the command and since it cannot do this I would defer it to the TPM emulator reset handler code, so the next layer down.
Quoted 6 lines
Also, when this is done in QEMU we don't need to do a data channel operation (run
TPM2_Shutdown) from within the control channel (uponCMD_INIT) inside of swtpm. This way we can deal with it properly. The usage model for the TPM 2 prescribes that aTPM2_Shutdownmust be sent before a shutdown or reset of the system, so let's let QEMU do it if the OS cannot do it.
Quoted 7 lines
What if qemu is killed or crashed, and a new instance is connected to swtpm? Or more subtle, the VM reboots without qemu help (no reset handler). It feels like it would be more robust to handle the situation in swtpm. Why not have the same last operation tracking and shutdown logic there? If
CMD_INITis received and the last operation is not shutdown, I'd have a warning and do it (if this is compliant with the spec, I am trying to find relevant text).
Something to test with:
https://github.com/stefanberger/swtpm/pull/701
Quoted 28 lines
Quoted 27 lines
Quoted 26 lines
Quoted 26 lines
Quoted 25 lines
Regards,
StefanStefan Berger (2):
backends/tpm: Record the last command sent to the TPM backends/tpm: SendTPM2_Shutdownupon VM resetbackends/tpm/tpm_emulator.c | 44 +++++++++++++++++++++++++++++++++++++ backends/tpm/tpm_int.h | 3 +++ backends/tpm/tpm_util.c | 9 ++++++++ backends/tpm/trace-events | 1 + include/sysemu/tpm_util.h | 3 +++ 5 files changed, 60 insertions(+)--
2.35.3