Web-Environment-Integrity

5

#2 opened 2023-04-28 01:37:04 +02:00 by bakkot

tokens bound to the device

2

#3 opened 2023-05-01 04:24:25 +02:00 by betuldurak

can this proposal facilitate integrity of the running script?

4

#4 opened 2023-05-04 02:09:22 +02:00 by michaelficarra

holdbacks diminish the value of the proposal and don't protect browser diversity

2

#5 opened 2023-05-04 02:15:44 +02:00 by michaelficarra

HTTP client hints

2

#6 opened 2023-05-04 02:35:48 +02:00 by michaelficarra

explainer assumes the existence of a base64 encoder

3

#8 opened 2023-05-08 22:21:19 +02:00 by bakkot

What extra fingerprinting does this allow?

3

#11 opened 2023-05-11 23:14:10 +02:00 by jyasskin

investigating the causes of unexpected integrity attestation failures

4

#12 opened 2023-05-12 00:49:54 +02:00 by michaelficarra

RFC 8890 Compliance

7

#13 opened 2023-05-12 08:56:26 +02:00 by rektide

Who determines what Attesters are acceptable?

4

#14 opened 2023-05-12 09:04:28 +02:00 by rektide

Surveillance by Attester concerns

2

#15 opened 2023-05-12 09:07:33 +02:00 by rektide

Attestation holdback

6

#16 opened 2023-06-06 16:42:03 +02:00 by SergeyKaG

What should the attester identity be?

2

#20 opened 2023-06-19 17:28:44 +02:00 by RupertBenWiser

Provide an example of validating tokens

#25 opened 2023-06-22 12:31:14 +02:00 by RupertBenWiser

What error codes should be thrown?

7

#26 opened 2023-06-23 17:39:23 +02:00 by RupertBenWiser

Include content binding hash type in the EnvironmentIntegrity response?