March 19th 2021
With the release of eBlockerOS 2.6 we have focused to improve “annoyances” like stability on low memory devices, HTTPS compatibility as well as the user interface. This release is also compatible to Raspberry Pi 3 again. Please find all details in the following list.
This release is brought to you by an international community of contributors in various fields. Our special thanks go to @mainzelM, @tomy, @pio78, @valentin, @navigator and our core maintainer @bpr.
- Added Cookie-Banner blocking list (disabled by default). Users who want to block Cookie-Consent-Banner can enable this feature via Settings>Blocker>Pattern Tracker Blocker>…
- Added DuckDuckGo Tracker Radar list (disabled by default) which can be enabled via Settings>Blocker>Pattern Tracker Blocker>…
- Added the possibility to define “ad hoc” blocker lists (pattern and domains) by just editing a text field (Settings>Blocker>”Select desired list container (i.e. pattern ad blocker)>Add – then choose “Text field” and start adding blocker rules. Please be aware that no syntax or other validation of the entered rules takes place.
- Added a new feature as early alpha release (for internal testing purposes) that improves the handling of SSL/HTTPS-connections. In future (after the final release) apps or websites that initially did not work with eBlocker HTTPS should now be recognized automatically. This will (hopefully) avoid connection errors or the definition of individual Trusted Apps. Hint: If an App/Website does not work properly initially please try again if this new features is enabled, as the new feature can only improve the second (and all forthcoming requests) but not the initial one.
- Improved user interface for device details (Settings>Devices>”select device”) to show all the available device dependent setting within the visible area (not below the fold).
- Improved speed for eBlocker with more than 1 GB RAM: now additional worker threads are started in parallel automatically. This will increase thru-put especially for high bandwidth users (>100 MBit/s). For 1GB eBlockers there is only one worker thread instead.
- Improved memory handling for devices with more than 1 GB RAM to allow the addition of very large filter lists.
- Improved auto-restart of Squid (a central eBlocker component) in case of low memory situations to improve stability (specifically for devices with 1GB RAM).
- Improved handling of HTTP/3 communication so no data can leak via the new protocol.
- Improved eBlocker Mobile OpenVPN configuration so that deprecated compression directives don’t cause warnings with OpenVPN apps.
- Improved the central ICAP server component to be compatible to Java JDK 11.
- Improved Java code formatting for better team collaboration.
- Fixed spontaneous “freeze” bug that occurred on Raspberry Pi 3 only.
- Fixed display of HTTPS tests in the dashboard that resulted in a wrong display of an exclamation mark although everything was working correctly.
- Fixed counter for blocked malware (previously zero was shown always).
- Fixed a bug where disabled eBlocker provide domain blocker list got accidentally re-enabled after reboot.
- Updated all Linux packages to the most recent versions which improves speed and enhances the core security.