From ac41ee3ccf0e71d00ee1d25f65fa2bb02c186979 Mon Sep 17 00:00:00 2001 From: uazo Date: Tue, 28 Mar 2023 13:17:52 +0000 Subject: [PATCH] AUTOMATED - git apply results --- build/patches/00Viewport-Protection-flag.patch | 2 +- .../00Warning-message-for-unsupported-hardware-aes.patch | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/build/patches/00Viewport-Protection-flag.patch b/build/patches/00Viewport-Protection-flag.patch index be44625f..4a6e941c 100644 --- a/build/patches/00Viewport-Protection-flag.patch +++ b/build/patches/00Viewport-Protection-flag.patch @@ -2,7 +2,7 @@ From: uazo Date: Tue, 20 Dec 2022 11:06:42 +0000 Subject: Viewport Protection flag -Scale the viewport and the screen by a random factor to +Scale the viewport and the screen by a random factor to prevent coordinate-based fingerprinting scripts. The factor is changed at each change of origin. The feature is controlled by a feature flag (default enabled) diff --git a/build/patches/00Warning-message-for-unsupported-hardware-aes.patch b/build/patches/00Warning-message-for-unsupported-hardware-aes.patch index 1899ec02..eab285cd 100644 --- a/build/patches/00Warning-message-for-unsupported-hardware-aes.patch +++ b/build/patches/00Warning-message-for-unsupported-hardware-aes.patch @@ -6,7 +6,7 @@ In boringssl the lack of support for native aes instructions in the cpu leads to a change in the order of the encryption methods in the tls1.3 stack and thus to an additional fingerprint bit. The use of software aes is discouraged due to possible side channel -attacks, so it is better to warn the user of the presence of an +attacks, so it is better to warn the user of the presence of an unsupported device. you can remove the message by going to chrome://flags/#no-hw-aes-warning ---