Google Web Environment Integrity Is the New Microsoft Trusted Computing

Re:Google Web Environment Integrity Is the New Microsoft Tru... by Knee_Pain on Thursday July 27, 2023 @06:04AM (#36891313)

Thank you for the knowledgeable reply.

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

[ Parent | on HN ]

Re:Google Web Environment Integrity Is the New Microsoft Tru... by BSEdlMMldESB on Thursday July 27, 2023 @07:04AM (#36891801)

you're calling the bottom line of hardware manufacturers "no good reason"!

[ Parent | on HN ]

Re:Google Web Environment Integrity Is the New Microsoft Tru... by yjftsjthsd-h on Thursday July 27, 2023 @02:23PM (#36898032)

Well... yes? Hardware can be very much bottom of the barrel and still be perfectly serviceable.

[ Parent | on HN ]

Re:Google Web Environment Integrity Is the New Microsoft Tru... by Peaches4Rent on Friday July 28, 2023 @06:39AM (#36905043)

It was sarcasm

[ Parent | on HN ]

Re:Google Web Environment Integrity Is the New Microsoft Tru... by sofixa on Thursday July 27, 2023 @07:26AM (#36891932)

> TPM 1.2 uses SHA1 for everything which is a broken hash function

> No reason

Using broken encryption is quite a decent reason.

[ Parent | on HN ]

Re:Google Web Environment Integrity Is the New Microsoft Tru... by AshamedCaptain on Thursday July 27, 2023 @07:47AM (#36892075)

Definitely not for the actual user of the device.

[ Parent | on HN ]

Re:Google Web Environment Integrity Is the New Microsoft Tru... by raxxorraxor on Friday July 28, 2023 @06:28AM (#36904977)

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.

[ Parent | on HN ]