Fix linux build

.gitattributes

@@ -1 +1,4 @@
-*.zip binary
+*.zip binary
+*.ttf binary
+*.otf binary
+*.ttc binary

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -22,6 +22,8 @@ body:
           required: true
         - label: "I have searched the existing issues for my problem. This is a new ticket, NOT a duplicate or related to another open issue."
           required: true
+        - label: "I have read the [FAQs](https://github.com/uazo/cromite/blob/master/FAQ.md)."
+          required: true
         - label: "I have updated Cromite to the latest version. The bug is reproducible on this latest version."
           required: true
         - label: "This is a bug report about the Cromite browser; not the website nor F-Droid nor anything else."

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -24,6 +24,8 @@ body:
       options:
         - label: "I have read the [README](https://github.com/uazo/cromite/blob/master/README.md)"
           required: true
+        - label: "I have read the [FAQs](https://github.com/uazo/cromite/blob/master/FAQ.md)."
+          required: true
         - label: "I have searched [existing issues](https://github.com/uazo/cromite/issues) for my feature request. This is a new issue (NOT a duplicate) and is not related to another issue."
           required: true
         - label: "I have searched [wont fix issues](https://github.com/uazo/cromite/issues?q=label%3Awontfix) and this request is not among them"

.github/workflows/build-images.yaml

@@ -163,8 +163,8 @@ jobs:
           path: cromite
           add-paths: |
             tools/under-control/*
-          commit-message: '[AUTO][FILECONTROL] - version ${{ env.NEW_VERSION }}'
-          title: '[AUTO][FILECONTROL] - version ${{ env.NEW_VERSION }}'
+          commit-message: 'AUTOMATED - new files under control ${{ env.NEW_VERSION }}'
+          title: New files under control ${{ env.NEW_VERSION }}
           body: ${{ env.MESSAGE }}
           delete-branch: true
           branch-suffix: short-commit-hash

.github/workflows/build_cromite.yaml

@@ -397,7 +397,7 @@ jobs:
           gn args out/lin64/ --list >out/lin64/gn_list
           echo "::endgroup::"
 
-          ninja -C out/lin64 chrome chrome_sandbox
+          ninja -C out/lin64 chrome
 
           cp ../../cromite/build/RELEASE out/lin64
 

.github/workflows/check-git-apply.yaml

@@ -147,8 +147,8 @@ jobs:
           #push-to-fork: uazo/cromite
           add-paths: |
             build/patches/*.patch
-          commit-message: '[AUTO] Patches auto-rebase'
-          title: '[AUTO] Patches auto-rebase for ${{ env.BRANCH }} branch'
+          commit-message: 'AUTOMATED - git apply results'
+          title: Git apply result for ${{ env.BRANCH }} branch
           body: ${{ env.MESSAGE }}
           delete-branch: true
           branch-suffix: short-commit-hash

.github/workflows/release.yaml

@@ -193,6 +193,9 @@ jobs:
           $GH release upload $VERSION-$CROMITE_SHA arm64_symbols.zip
           echo "::endgroup::"
 
+          # workaround for https://github.com/cli/cli/issues/6599
+          sleep 30s
+
           TIMESTAMP=$(date +%s -r chrome-win.zip)
           echo >updateurl.txt "browser=chromium;os=windows;architecture=64-bit;timestamp=$TIMESTAMP;editor=uazo;channel=stable;repository=https://github.com/uazo/cromite/releases;download=https://github.com/uazo/cromite/releases/latest/download/chrome-win.zip;version=$(cat $OUTPUTFILE_WIN/RELEASE);revision=1;commit=$CROMITE_SHA"
           $GH release upload $VERSION-$CROMITE_SHA updateurl.txt

.github/workflows/update-patches-doc.yaml

@@ -13,8 +13,8 @@ permissions:
 
 on:
   push:
-    branches:
-      - 'master'
+    branches-ignore:
+      - 'ci'
     paths:
       - 'build/**'
 
@@ -75,8 +75,8 @@ jobs:
           base: ${{ env.BRANCH }}
           add-paths: |
             build/patches/*.patch
-          commit-message: '[AUTO][DOC] Generate patches doc for master branch'
-          title: '[AUTO][DOC] Generate patches doc for master branch'
+          commit-message: 'AUTOMATED - update patch docs'
+          title: Generate patches doc for ${{ env.BRANCH }} branch
           body: ${{ env.MESSAGE }}
           delete-branch: true
           branch-suffix: short-commit-hash

README.md

@@ -91,9 +91,6 @@ you can activate the 'RendererAppContainer' flag from the command line with
   --enable-features=RendererAppContainer
 ```
 
-### Auto-update setup for linux
-working in progress in https://github.com/uazo/cromite/issues/771
-
 # Contributing
 
 Please submit issues following the issue template; beware that GitHub does not display the templates from mobile.
@@ -115,8 +112,6 @@ For any usage or development discussion please use GitHub Discussions: https://g
   * [Inox patchset](https://github.com/gcarq/inox-patchset) for some patches (via ungoogled-chromium)
   * [Brave Browser](https://github.com/brave/brave-core) for some patches
 
-thanks to [austinhuang0131](https://github.com/austinhuang0131) for the svg icon
-
 # License
 
 Cromite is published under [GNU GPL v3](./LICENSE).

build/RELEASE

@@ -1 +1 @@
-125.0.6422.76
+123.0.6312.106

build/components/README.md

@@ -0,0 +1,55 @@
+## Components on Cromite
+
+Cromite needs to download certain static files for certain features.
+Specifically, the need arises from making the fonts used by the browser standard, in order to minimise the use of fingerprint scripts based on the fonts present on the device.
+
+To do this, the automatic update of components was reactivated with some differences compared to Chromium:
+
+- Since there is no backend, the response to the request for updates is static (see `query.json`). It currently resides on the cromite.org site because, deliberately, no request log is active.
+- The update file (a zip file) is downloaded only once and, if already done, nothing more is requested externally, unless the user goes to `chrome://components` and requests the update check.
+
+It is possible to generate a zip for the components in this way:
+
+### prerequisites
+
+- generate a der file, used to 'sign' the zip:
+
+```
+openssl genrsa 4096 | openssl pkcs8 \
+   -inform PEM -nocrypt -topk8 -outform DER \
+   -out cromite.pkcs8.der
+```
+
+currently the certificate used for cromite is in the pkcs8.der.asc, encrypted with gpg, so not public, for security reasons.
+
+- build `crx3_build_action`, necessary for 'signing' the zip:
+
+```
+ninja -C out/lin64 crx3_build_action
+```
+
+### how to generate the zip
+
+simply:
+
+```
+zip -j fonts.zip fonts/*
+out/lin64/crx3_build_action fonts_component.zip fonts.zip pkcs8.der
+```
+
+the resulting zip cannot currently be unzipped with system tools.
+
+The zip must contain the file `manifest.json`.
+
+### important sections in the query.json
+
+- `appid`:
+is the value used to identify the component. currently I do not know how to create a new one, there is no documentation or code to generate it.
+- `codebase`:
+is the base url from which to download the file
+- `name`:
+is the name of the file to download, the url is "codebase + name"
+- `hash_sha256`:
+is the hash of the resulting zip, used for comparison. compatible with sha256sum
+- `fp`:
+currently not used, is an additional protection mechanism for which I have found no documentation.