|
|
|
Hello Newsletter Subscriber,
|
There is much news at eBlocker again:
|
User poll for further development
Today, eBlockerOS is already available on various platforms - from the White Cube to Raspberry Pi and Virtual Environments. However, we do not collect any data about eBlocker usage or the devices used. In order to further develop eBlockerOS and plan the next software generation, we appreciate your participation in a short poll regarding the platform used.
|
Bugfix release eBlockerOS 3.0.3
The release 3.0.3, which has already been distributed to all eBlockers with activated automatic updates, contains a bug fix that only had an effect when eBlockerOS was newly installed. Due to a bug, the DNS firewall crashed so neither the "Open Source License Agreement" could be retrieved nor other Internet domains could be accessed. We have also improved some processes in eBlockerOS as part of the bug fix to increase stability even further.
|
eBlockerOS images for new installs
At the same time, we have updated the eBlockerOS images for Raspberry Pi, PC Boot and VirtualBox to the latest version 3.0.3, so that new installations work smoothly again. Images for other Virtual Environments that have been created by the community in the past are still open. Here we would appreciate your help again: Many thanks in advance to @CalimerO, @Fluffy and all other eBlocker supporters with VM experience!
|
For those interested only: Technical background of the bug
The DNS bug was triggered externally: eBlockerOS checks during initial installation whether certain router domains such as fritz.box, o2.box or kabel.box are accessible and then automatically adds them to the eBlocker DNS for extra convenience. Previously, public .box domains could not be registered, so the domain query always returned a defined error code or the router IP address. With the registration of fritz.box by third parties at the end of January 2024, a different return value (a CNAME) was suddenly sent instead of the error code. This return value "confused" the DNS firewall and ultimately caused it to crash, so no domain resolutions were possible at all. 😥
|
eBlocker.box registered
We immediately took the bug as an opportunity to register the now publicly registrable domain eBlocker.box for ourselves. This ensures that potential attackers cannot fake phishing or other dangerous websites for eBlocker users. Thanks at this point to @Random for his patience and persistence with the "crypto" domain registration in Web3.
|
|
Support in the first quarter
|
Because the first quarter of each year is always a financial challenge due to lower donations, we would like to invite all users to support our non-profit project once again.
|
Only thanks to your help and support we are able to ensure the future of eBlocker and continue our fight for an anonymous, free internet without trackers and advertising!
|
1000 thanks and best regards
|
Best regards
Boris, Christian and the entire eBlocker team
|
|
--
eBlocker Open Source UG (haftungsbeschränkt)
Hudtwalckertwiete 10
22299 Hamburg
Germany
|
office@eBlocker.org
www.eBlocker.org
|
Geschäftsführer/General Managers:
Dipl.-Math. Christian Bennefeld
|
Sitz/Registered office: Hamburg
Register: Amtsgericht Hamburg, HRB 160491
Steuernr./TaxID: 49 / 717 / 02295
|
|
|
|
|
|
|
