ClamAV

2 Posts
3 Users
5 Reactions
23 Views
-3
Topic starter

Hi,
i use the VM edition and take a look arround in the system. I see, squid and icap is used. i´m sure, there was a plan to integrate ClamAV in the eBlocker. But the Hardware was to small to give a nice performance.
So in the VM edition is enough power to realize such an feature, right?
Before i try to invest a lot of hour to find out, how it can this be abled, please can you tell me, how you did this work?
Because the http and https traffic is decrypted and it will be easy to scan. i hope so 🙂

Greetings Neppu

Client OS
Browser
eBlocker hardware
Browser version
1 Answer
2

@neppumuck 

Thanks for your feature request. 

First of all eBlocker‘s focus is to protect your privacy where other solutions fail (i.e. protecting Apps, SmartTV, IoT). For Anti-Virus protection there are great solutions available.

Unfortunately ClamAV‘s protection was very poor in the past (compared to other solutions) as a network stream based solution can not recognize possible virus execution patterns on the device level.

For these reasons we never considered to integrate ClamAV. But performance considerations never played a role for the decision, honestly.

Personally, I find we should not implement features where people trust the reliability but we fail to deliver. This would be the case if we claim „includes anti-virus“ but ClamAV‘s protection is too inferior and lets viruses pass. A very probable worst case scenario unfortunately. 

But I‘m not the one to judge pro or against a feature implementation - it‘s up to the community.

As eBlockerOS is fully Open Source of course you are invited to join our team if you feel like implementing ClamAV or something else.

You are very welcome and heartly invited 🤗 

 

Random 29/01/2023 11:06 am

@benne I agree - also from a technical perspective. Today eBlocker blocks malicious outbound requests at it‘s core. Neither AV detection nor email SPAM blocking can be implemented based on this core. They would just run as separate instances and would turn support into a bigger challenge (as we would support third party apps not build by us).

I seriously find we should not try to turn eBlocker into a swiss pocket knife. A pocket knife is never really great for a specific task but will always be below average of the specialists. Today eBlocker is a specialist in privacy and youth protection. We should keep it this way in my opinion.

Answer

Nach oben scrollen