zlacker

[parent] [thread] 6 comments
1. Knee_P+(OP)[view] [source] 2023-07-27 10:04:12
Thank you for the knowledgeable reply.

This choice will still render a ton of devices basically e-waste for no real good reason

replies(2): >>BSEdlM+S7 >>sofixa+Z9
2. BSEdlM+S7[view] [source] 2023-07-27 11:04:49
>>Knee_P+(OP)
you're calling the bottom line of hardware manufacturers "no good reason"!
replies(1): >>yjftsj+nK1
3. sofixa+Z9[view] [source] 2023-07-27 11:26:30
>>Knee_P+(OP)
> TPM 1.2 uses SHA1 for everything which is a broken hash function

> No reason

Using broken encryption is quite a decent reason.

replies(2): >>Ashame+ic >>raxxor+oy3
◧◩
4. Ashame+ic[view] [source] [discussion] 2023-07-27 11:47:12
>>sofixa+Z9
Definitely not for the actual user of the device.
◧◩
5. yjftsj+nK1[view] [source] [discussion] 2023-07-27 18:23:27
>>BSEdlM+S7
Well... yes? Hardware can be very much bottom of the barrel and still be perfectly serviceable.
replies(1): >>Peache+sz3
◧◩
6. raxxor+oy3[view] [source] [discussion] 2023-07-28 10:28:42
>>sofixa+Z9
SHA1 is not for encryption, it is a signature algorithm.

It is considered broken because there is a faster way than simple brute force to create a collision. The currently know approach is still computationally expensive.

It is correct to call it broken, but I don't see the implications for TMP at all. TPM is shitty tech in the first place in my opinion, but aside from that there is little practical relevance.

◧◩◪
7. Peache+sz3[view] [source] [discussion] 2023-07-28 10:39:38
>>yjftsj+nK1
It was sarcasm
[go to top]