|
|
|
Dear Newsletter Subscriber,
|
At the beginning of the year, we have some news about eBlocker:
|
|
Renewing the HTTPS certificate in time
|
For security reasons, the eBlocker certificates for HTTPS support must be renewed every three years. For all users who have been with us since the launch of our open source project in 2020, this renewal is due this year again.
|
Important: If the new certificate is not installed in time and the old certificate expires, HTTPS connections will no longer be possible. In this case, the browser will display an error message – at this point at the latest, the new certificate must be installed on all devices.
|
eBlockerOS will remind you of the certificate expiration 30 days in advance in the dashboard with a yellow warning triangle and via system messages. The time remaining until the certificate expires will be displayed and the new certificate will be offered for installation.
|
Our recommendation: Install the new certificate as early as possible to avoid interruptions. The previous certificate should not be uninstalled. When installing the certificate, follow the instructions for your operating system and observe them carefully to avoid problems (see documentation on certificate installation).
|
New supporters – new features
We are delighted to welcome new members to our supporter team and are excited about their fantastic initiative. Our new colleagues @shedowe and @faber38 joined us last year and are currently working on highly requested features:
|
@shedowe has already developed an initial Docker version of eBlockerOS and welcomes feedback and suggestions for improvement. Next, he wants to focus on implementing encrypted and authenticated DNS via DoT.
|
@faber38 has already developed an initial prototype for using the Wireguard protocol for eBlocker Mobile (in addition to OpenVPN). The biggest technical challenges have already been resolved – now it's time to integrate it into the eBlocker user interface.
|
However, it will be some time before the features can be released, as we are all working as volunteers and part-time on the features. We will report further progress here in the newsletter.
|
Easy migration from eBlockerOS 3 to eBlockerOS 4
About a quarter of all users have already switched to eBlockerOS 4. At the same time, we are continuing to work on a convenient migration solution that will automatically transfer all settings from eBlockerOS 3. We are already well advanced in this work and hope to release a beta version soon.
|
Hardware buying recommendation for eBlockerOS 4
eBlockerOS 4 is a 64-bit system and requires at least 2 GB of RAM. After extensive testing on various platforms (many thanks to @CalimerO), we have found that memory consumption can be higher, especially when many filter lists are active. We therefore recommend a Raspberry Pi with 4 GB for new purchases to be optimally prepared for the future.
|
Thank you for your support
Last but not least, we would like to express our sincere gratitude to everyone who supports eBlocker financially or contributes to our project with their time, expertise, and volunteer work. Without your commitment, the continuous development of eBlocker as an open source project would not be possible!
|
With your donation, you directly support the further development of eBlockerOS and ensure that our servers can continue to operate reliably in the future.
Support eBlocker now with a donation – every contribution counts.
|
|
|
|
Thank you so much for your help!
|
Best regards,
Boris, Christian, and the entire eBlocker team
|
|
--
eBlocker Open Source GmbH
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
|
|
|
|
|
|
|
