[過去ログ] 【Chrome】uBlock Origin ★6【Chromium】 (1002レス)
上下前次1-新
このスレッドは過去ログ倉庫に格納されています。
次スレ検索 歴削→次スレ 栞削→次スレ 過去ログメニュー
730(1): 不思議Angel ◆Akina/PPII ハンター[Lv.281][SR武][SR防][苗] 09/24(水)03:58 ID:h346rbB20(14/21) AAS
BEアイコン:miyabi.gif
>>729
# Chromium binaries directory (string):
# Relative (to chrlauncher directory) or full path (env. variables supported).
ChromiumDirectory=.\bin
To prevent deletion by Microsoft Defender each time the browser is updated, check the user-data-dir folder by modifying it accordingly.
Enable network process sandbox in windows
I don't include any setups because I don't like the experience of not knowing what they do, so you must manually run this command on first installation:
cd <where_is_the_exe>
icacls . /grant "*S-1-15-2-2:(OI)(CI)(RX)"
see uazo/bromite-buildtools#51
Enable AppContainer for renderer process in windows
you can activate (highly recommended) the 'RendererAppContainer' flag from the command line with
--enable-features=RendererAppContainer
Auto-update setup for linux
working in progress in #771
Making Cromite work in Ubuntu 24.04 and its derivatives (kubuntu, etc)
This happens because, starting with Ubuntu 24.04, Apparmor restricts the use of unprivileged user namespaces. To fix this, you have several options:
1. Creating an apparmor profile for cromite
Create /etc/apparmor.d/chrome, and write:
abi <abi/4.0
include <tunables/global>
profile cromite /home/user/cromite/chrome-lin/chrome flags=(unconfined) {
userns,
include if exists <local/chrome>
}
replacing the cromite binary path with where you have placed cromite.
Now, run sudo apparmor_parser -r /etc/apparmor.d/cromite to apply the changes.
2. Disabling the restriction until next reboot
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
3. Disabling the restriction permanently
Add kernel.apparmor_restrict_unprivileged_userns=0 to the file /etc/sysctl.d/60-apparmor-namespace.conf. Create the file if not exists.
上下前次1-新書関写板覧索設栞歴
あと 272 レスあります
スレ情報 赤レス抽出 画像レス抽出 歴の未読スレ AAサムネイル
ぬこの手 ぬこTOP 0.015s