Brave Browser 1.89.132

[removed: Leaving the ][added: This ]policy [removed: unset or setting it to Enabled allows users to view and use the Google Lens button in the search box on the New Tab page. Setting the policy to Disabled means users will not see the Google Lens button in the search box on the New Tab page. Starting in Brave 147, this policy will be ][added: is ]deprecated. [removed: IT Admins can use SearchContentSharingSettings to control this feature going forward.][added: Its usage is discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: Lens Overlay lets users perform contextual Google searches either via a screenshot or by asking a question about the current page's contents. ]This [removed: feature requires the end user to opt-in. This feature is available to all users with Google as their default search engine, unless it is disabled by this policy. When ]policy is [removed: set to 0 - Allow or not set, the feature will be available to users. When policy ][added: deprecated. Its usage ]is [removed: set to 1 - Do not allow, the feature will not be available. Starting in Brave 140, if the policy is unset, its behavior is determined by the GenAiDefaultSettings policy. Starting in Brave 147, this policy will be deprecated. IT Admins can use SearchContentSharingSettings to control this feature going forward.][added: discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: Leaving the ][added: This ]policy [removed: unset or setting it to Enabled allows users to view and use the Google Lens region search menu item in the context menu. Setting the policy to Disabled means users will not see the Google Lens region search menu item in the context menu when Google Lens region search ]is [removed: supported. Starting in Brave 147, this policy will be ]deprecated. [removed: IT Admins can use SearchContentSharingSettings to control this feature going forward.][added: Its usage is discouraged. Read more at https://support.google.com/chrome/a/answer/7643500]

This policy [removed: configures whether Brave will offer a post-quantum key agreement algorithm in TLS, using the ML-KEM NIST standard. Prior to Brave 131, the algorithm was Kyber, an earlier draft iteration of the standard. This allows supporting servers to protect user traffic from being later decrypted by quantum computers. If this policy ][added: is removed. It ]is [removed: Enabled or ]not [removed: set, Brave will offer a post-quantum key agreement in TLS connections. User traffic will then be protected from quantum computers when communicating ][added: compatible ]with [removed: compatible servers. If ]this [removed: policy is Disabled, Brave will not offer a post-quantum key agreement in TLS connections. User traffic will then be unprotected from quantum computers. Offering a post-quantum key agreement is backwards-compatible. Existing TLS servers and networking middleware are expected to ignore the new option and continue selecting previous options. However, devices that do not correctly implement TLS may malfunction when offered the new option. For example, they may disconnect in response to unrecognized options or the resulting larger messages. Such devices are not post-quantum-ready and will interfere with an enterprise's post-quantum transition. If encountered, administrators should contact the vendor for a fix. This policy is a temporary measure and will be removed sometime after Brave ]version [removed: 145. It may be Enabled to allow you to test for issues, and may be Disabled while issues are being resolved.][added: of Brave. Read more at https://support.google.com/chrome/a/answer/7643500]

[removed: Enables the UI Automation accessibility framework provider in Brave for use by accessibility tools. ]This policy is [removed: supported in Brave for a one-year transition period to allow enterprise administrators to control the deployment of the browser's UI Automation accessibility framework provider. Accessibility and other tools that use the UI Automation accessibility framework to interoperate ][added: removed. It is not compatible ]with [removed: the browser may require updates to function properly with the browser's UI Automation provider. Administrators can use ]this[removed: policy to temporarily disable the browser's UI Automation provider (thereby reverting to the old behavior) while they work with vendors to provide updates to impacted tools. When set to false, Brave only enables its Microsoft Active Accessibility provider. Accessibility and other tools that use the newer UI Automation accessibility framework to interoperate with the browser will communicate with it by way ][added: version ]of [removed: a compatibility shim in Microsoft® Windows®. When set to true, Brave enables its UI Automation provider in addition to its Microsoft Active Accessibility provider. Accessibility and other tools that use the newer UI Automation accessibility framework to interoperate with the browser will communicate directly with it. When left unset, the variations framework in Brave is used to enable or disable the provider. Support for this policy setting will end in Brave 146.][added: Brave. Read more at https://support.google.com/chrome/a/answer/7643500]