@ForgottenFlux to [email protected]English • 2 months agoSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.comexternal-linkmessage-square254arrow-up1505arrow-down132cross-posted to: [email protected]privacytechnology[email protected][email protected]
arrow-up1473arrow-down1external-linkSignal under fire for storing encryption keys in plaintext on desktop appstackdiary.com@ForgottenFlux to [email protected]English • 2 months agomessage-square254cross-posted to: [email protected]privacytechnology[email protected][email protected]
minus-square@[email protected]linkfedilink1•edit-22 months ago Signal data will be encrypted if your disk is also encrypted. True. and you don’t have any type of verified boot process How motherboard refusing to boot from another drive would protect anything?
minus-square@[email protected]linkfedilink1•edit-22 months agoWell, yes. By refusing to boot. It can’t prevent booting if motherboard is replaced. EDIT: s/do anything/prevent booting/
minus-square@9tr6gyp3link1•2 months agoIf the hardware signatures don’t match, it wont boot without giving a warning. If the TPM/Secure Enclave is replaced/removed/modified, it will not boot without giving a warning.
minus-square@[email protected]linkfedilink1•edit-22 months ago If the hardware signatures don’t match Compromised hardware will say it is same hardware If the TPM/Secure Enclave is replaced/removed/modified, it will not boot without giving a warning. Compromised hardware controls execution of software. Warning is done in software. Conpromised hardware won’t let it happen.
minus-square@[email protected]linkfedilink1•2 months agoCompromised hardware can’t create new signatures, but it doesn’t matter because it controls execution of software and can skip any checks.
True.
How motherboard refusing to boot from another drive would protect anything?
Its more about protecting your boot process from malware.
Well, yes. By refusing to boot. It can’t prevent booting if motherboard is replaced.
EDIT: s/do anything/prevent booting/
Thats correct. Thats one of the many perks.
EDIT: s/do anything/prevent booting/
If the hardware signatures don’t match, it wont boot without giving a warning. If the TPM/Secure Enclave is replaced/removed/modified, it will not boot without giving a warning.
Compromised hardware will say it is same hardware
Compromised hardware controls execution of software. Warning is done in software. Conpromised hardware won’t let it happen.
Compromised hardware doesn’t know the signatures. Math.
Compromised hardware can’t create new signatures, but it doesn’t matter because it controls execution of software and can skip any checks.