d0x
Active Member
A seperate "log" needs to be added for blocked threats. I recently noticed that in the last week or so it blocked 2 threats which is good..BUT
I have no idea what the threat was, where it came from, when it happened etc. Was it an app trying to do something? Was it from my browser?
The reason we need to be able to access this information is simple. So we can avoid it in the future. I could very well visit the same site or even still have the app installed but i cant tell. What if it is an app trying to contact a c&c server to download something or use my device as a ddos bot and next time adguard doesnt have the server its using in its block list? More and more android malware is being delivered this way, apps downloading files outside the store. Usually they wait until the app has a ton of downloads then update the app with a simple change that allows it to download a malicious payload.
It cant be that difficult to log the info to its own seperate log file. If it triggers a counter then there is already code in place... it just needs to be slightly expanded so instead of just adding 1 to the number on the main screen it also gets a log entry that is seperate from the normal log and it has to be seperate because nobody watches the log all day and you cant tell a blocked ad from a threat.
Please add this... it would enhance the users ability to protect themselves and the actual coding work required to implement it should be minimal.
I have no idea what the threat was, where it came from, when it happened etc. Was it an app trying to do something? Was it from my browser?
The reason we need to be able to access this information is simple. So we can avoid it in the future. I could very well visit the same site or even still have the app installed but i cant tell. What if it is an app trying to contact a c&c server to download something or use my device as a ddos bot and next time adguard doesnt have the server its using in its block list? More and more android malware is being delivered this way, apps downloading files outside the store. Usually they wait until the app has a ton of downloads then update the app with a simple change that allows it to download a malicious payload.
It cant be that difficult to log the info to its own seperate log file. If it triggers a counter then there is already code in place... it just needs to be slightly expanded so instead of just adding 1 to the number on the main screen it also gets a log entry that is seperate from the normal log and it has to be seperate because nobody watches the log all day and you cant tell a blocked ad from a threat.
Please add this... it would enhance the users ability to protect themselves and the actual coding work required to implement it should be minimal.
Last edited:
