You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Why won't `hardened-chromium` start on Nvidia?](#hardened-chromium-start-nvidia)
32
-
-[Why don't some websites that require JIT/WebAssembly work in `hardened-chromium` even with the V8 Optimizer toggle enabled?](#hardened-chromium-exceptions)
33
-
-[Why don't extensions work in `hardened-chromium`?](#hardened-chromium-extensions)
29
+
-[Why won't Trivalent start when bubblejailed?](#trivalent-bubblejail)
30
+
-[Why won't Trivalent start on Nvidia?](#trivalent-nvidia)
31
+
-[Why don't some websites that require JIT/WebAssembly work in Trivalent even with the V8 Optimizer toggle enabled?](#trivalent-v8-exceptions)
32
+
-[Why don't extensions work in Trivalent?](#trivalent-extensions)
34
33
-[How do I customize secureblue?](#customization)
35
34
36
35
### Why is Flatpak included? Should I use Flatpak?
@@ -169,38 +168,25 @@ Similar to the AppImage FAQ, the KDE Vault default backend `cryfs` depends on fu
169
168
ujust distrobox-assemble
170
169
```
171
170
172
-
### Why aren't my apps loading on Nvidia Optimus?
173
-
{: #nvidia-optimus}
171
+
### Why won't Trivalent start when bubblejailed?
172
+
{: #trivalent-bubblejail}
174
173
175
-
There is an [upstream bug](https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/21). You may need to run:
174
+
`bubblejail`**SHOULD NOT** be used on Trivalent, there are issues reported with the pairing and removing the `bubblejail` config after it is applied can be difficult. It should also be noted that applying additional sandboxing may interfere with chromium's own internal sandbox, so it can end up reducing security.
This should no longer be required as of F41: https://discussion.fedoraproject.org/t/gdk-message-error-71-protocol-error-dispatching-to-wayland-display/127927/42
182
-
183
-
### Why won't `hardened-chromium` start?
184
-
{: #hardened-chromium-start}
185
-
186
-
Try starting `hardened-chromium` from the commandline by running `chromium-browser`. If you get an error about the current profile already running on another device, this is an issue with upstream chromium which can happen when you `rpm-ostree update` or `rpm-ostree rebase`. To fix this, simply run `rm ~/.config/chromium/SingletonLock`.
187
-
188
-
`bubblejail`**SHOULD NOT** be used on `hardened-chromium`, there are issues reported with the pairing and removing the `bubblejail` config after it is applied can be difficult. It should also be noted that applying additional sandboxing may interfere with chromium's own internal sandbox, so it can end up reducing security.
189
-
190
-
### Why won't `hardened-chromium` start on Nvidia?
191
-
{: #hardened-chromium-start-nvidia}
176
+
### Why won't Trivalent start on Nvidia?
177
+
{: #trivalent-nvidia}
192
178
193
-
On some Nvidia machines, `hardened-chromium` defaults to the X11 backend. Since secureblue disables Xwayland by default, this means that you will need to run `ujust toggle-xwayland` and reboot, for `hardened-chromium` to work.
179
+
On some Nvidia machines, Trivalent defaults to the X11 backend. Since secureblue disables Xwayland by default, this means that you will need to run `ujust toggle-xwayland` and reboot, for Trivalent to work.
194
180
195
-
### Why don't some websites that require JIT/WebAssembly work in `hardened-chromium` even with the V8 Optimizer toggle enabled?
196
-
{: #hardened-chromium-exceptions}
181
+
### Why don't some websites that require JIT/WebAssembly work in Trivalent even with the V8 Optimizer toggle enabled?
182
+
{: #trivalent-v8-exceptions}
197
183
198
184
This is an [upstream bug](https://issues.chromium.org/issues/373893056) that prevents V8 optimization settings from being applied to iframes embedded within a parent website. As a result, WebAssembly may not function on services that use a separate URL for their content delivery network or other included domains, such as VSCode Web ([https://github.dev](https://github.dev)). To make VSCode Web work properly, you need to manually allow V8 optimizations for the CDN by adding `https://[*.]vscode-cdn.net` to your list of trusted websites.
199
185
200
-
### Why don't extensions work in `hardened-chromium`?
201
-
{: #hardened-chromium-extensions}
186
+
### Why don't extensions work in Trivalent?
187
+
{: #trivalent-extensions}
202
188
203
-
Extensions in `hardened-chromium` are disabled by default, for security reasons it is not advised to use them. If you want content/ad blocking, that is already built into `hardened-chromium` and enabled by default. If you require extensions, you can re-enable them by disabling the `Disable Extensions` toggle under `chrome://settings/security`, then restart your browser (this toggle is per-profile).
189
+
Extensions in Trivalent are disabled by default, for security reasons it is not advised to use them. If you want content/ad blocking, that is already built into Trivalent and enabled by default. If you require extensions, you can re-enable them by disabling the `Disable Extensions` toggle under `chrome://settings/security`, then restart your browser (this toggle is per-profile).
204
190
\
205
191
\
206
192
If the extension you installed doesn't work, it is likely because it requires WebAssembly (WASM) for some cryptographic library or some other optimizations (this is the case with the Bitwarden extension). To re-enable JavaScript JIT and WASM for extensions, enable the feature `chrome://flags/#internal-page-jit`.
@@ -190,7 +190,7 @@ When using a non-wheel user, you can add the user to other groups if you want. F
190
190
### Setup system DNS
191
191
{: #dns}
192
192
193
-
Interactively setup system DNS resolution for systemd-resolved (optionally also set the resolver for hardened-chromium via management policy):
193
+
Interactively setup system DNS resolution for systemd-resolved (optionally also set the resolver for Trivalent via management policy):
194
194
195
195
```
196
196
ujust dns-selector
@@ -244,12 +244,12 @@ To validate your secureblue setup, run:
244
244
ujust audit-secureblue
245
245
```
246
246
247
-
### Optional: `hardened-chromium` Flags
248
-
{: #hardened-chromium-flags}
247
+
### Optional: Trivalent Flags
248
+
{: #trivalent-flags}
249
249
250
-
The included [hardened-chromium](https://github.com/secureblue/hardened-chromium) browser has some additional settings in `chrome://flags` you *may* want to set for additional hardening and convenience (can cause functionality issues in some cases).
250
+
The included [Trivalent](https://github.com/secureblue/Trivalent) browser has some additional settings in `chrome://flags` you *may* want to set for additional hardening and convenience (can cause functionality issues in some cases).
251
251
252
-
You can read about these settings in the [hardened-chromium post-install](https://github.com/secureblue/hardened-chromium?tab=readme-ov-file#post-install) instructions.
252
+
You can read about these settings in the [Trivalent post-install](https://github.com/secureblue/Trivalent?tab=readme-ov-file#post-install) instructions.
0 commit comments