|
|
@@ -5,6 +5,10 @@
|
|
|
### Features
|
|
|
|
|
|
In addition to features provided by [Iridium Browser](//iridiumbrowser.de/) and [Inox patchset](//github.com/gcarq/inox-patchset), the following is also included:
|
|
|
+* Replace many web domains in the source code with non-existent alternatives ending in `qjz9zk` (known as domain substitution)
|
|
|
+* Strip binaries from the source code (known as source cleaning)
|
|
|
+ * This includes all pre-built executables, shared libraries, and other forms of machine code. They are substituted with system or user-provided equivalents, or built from source.
|
|
|
+ * However some data files (e.g. `icudtl.dat` for Unicode and Globalization support and `*_page_model.bin` that define page models for the DOM Distiller) are left in as they do not contain machine code and are needed for building.
|
|
|
* Remove additional detection of and disable specific functionality for Google hosts
|
|
|
* Disable searching in Omnibox
|
|
|
* Disable automatic formatting of URL in Omnibox
|
|
|
@@ -12,16 +16,19 @@ In addition to features provided by [Iridium Browser](//iridiumbrowser.de/) and
|
|
|
* Added menu item under "More tools" to clear the HTTP authentication cache on-demand
|
|
|
* Disable persistent per-site settings in Preferences file
|
|
|
* Force all pop-ups into tabs
|
|
|
-* Replace many domains in the source code with non-existent alternatives (known as domain substitution)
|
|
|
-* Strip binaries from the source code (known as source cleaning)
|
|
|
* Disable intranet redirect detector (unnecessary invalid DNS requests)
|
|
|
* Add more URL schemes allowed for saving
|
|
|
-* (Windows) Do not set the Zone Identifier on downloaded files (which is a hassle to remove)
|
|
|
-* Provide Debian build scripts
|
|
|
- * (Debian build scripts change) Move the chrome-sandbox into a separate package
|
|
|
* (Iridium Browser feature change) Prevent URLs with the `trk:` scheme from connecting to the Internet
|
|
|
* Also prevents any URLs with the top-level domain `qjz9zk` (as used in domain substitution) from attempting a connection.
|
|
|
* (Iridium and Inox feature change) Prevent pinging of IPv6 address when detecting the availability of IPv6
|
|
|
+* Support for building Debian and Ubuntu packages
|
|
|
+ * Creates a separate package `chrome-sandbox` for the SUID sandbox
|
|
|
+* Windows support with additional changes:
|
|
|
+ * Build `wow_helper.exe` from source instead of using the pre-built version
|
|
|
+ * Build `swapimport.exe` from source instead of downloading it from Google (requires [customized syzygy source code](https://github.com/Eloston/syzygy))
|
|
|
+ * Build `yasm.exe` from source instead of using the pre-built version
|
|
|
+ * Use user-provided building utilities instead of the ones bundled with Chromium (currently `gperf` and `bison`)
|
|
|
+ * Do not set the Zone Identifier on downloaded files (which is a hassle to unset)
|
|
|
|
|
|
**DISCLAIMER: Although I try my best to eliminate bugs and privacy-invading code, there will be those that slip by due to the enormity and continuing evolution of the Chromium project.**
|
|
|
|
|
|
@@ -38,7 +45,7 @@ The `master` branch is for development, so it is not guaranteed to be in a worki
|
|
|
|
|
|
## How ungoogled-chromium is designed
|
|
|
|
|
|
-Features are implemented through a combination of build flags, patches, and a few file inputs for automated source modification. All of these are stored in the `resources` directory. The `resources` directory contains the `common` directory, which has such files that apply to all platforms. All other directories, named by platform, contain additional platform-specific data. Most of the features, however, are stored in the `common` directory.
|
|
|
+Features are implemented through a combination of build flags, patches, and a few configuration files for scripts. All of these settings are stored in the `resources` directory. The `resources` directory contains the `common` directory, which has such files that apply to all platforms. All other directories, named by platform, contain additional platform-specific data. Most of the features, however, are stored in the `common` directory.
|
|
|
|
|
|
There are currently two automated scripts that process the source code:
|
|
|
* Source cleaner - Used to clean out binary files (i.e. do not seem to be human-readable text files, except a few required for building)
|
Eloston