What is adguard-tcpkill and why does it want to connect via the RAW port?
- Thread starter xx_
- Start date
M
myMoon
Guest
@xx_
Hello!
Adguard-tcpkill is closing needed browser connections to filter it all.
About signed, as I can see:
codesign --verbose -v adguard-tcpkill
adguard-tcpkill: valid on disk
adguard-tcpkill: satisfies its Designated Requirement
What actually did you use to check in signed status?
Hello!
Adguard-tcpkill is closing needed browser connections to filter it all.
About signed, as I can see:
codesign --verbose -v adguard-tcpkill
adguard-tcpkill: valid on disk
adguard-tcpkill: satisfies its Designated Requirement
What actually did you use to check in signed status?
Never mind, it does appear to have a code signature by Performiks OOO. I use Little Snitch alongside AdGuard, so this is the information it provided me on AdGuard trying to connect via adguard-tcpkill.
You mention: "Adguard-tcpkill is closing needed browser connections to filter it all." However, I am not sure I still don't understand what it does or why it is needed. Can you please elaborate? Since I initially didn't know what it was, I blocked it on Little Snitch for any connection, and it still seems AdGuard works fine, so I'm not sure why it's necessary. What is the RAW protocol for?
To be able to filter connections, e.g. open ones, it needs to close them first (and then the connections can reopen, with AG for Mac filtering them). As far as I know, this is needed to prevent an issue where some connections might not be filtered (more-or-less fixed in 1.5.5 RC) like YouTube ads slipping through in Safari.
Thank you. I am using 1.5.5 and it seems to be working fine without adguard-tcpkill being granted access to establish connections. Will it cause problems if I leave it like this? Should I really be enabling it, or is it mostly an optional thing. If it's absolutely crucial, then I guess I'll enable it, but so far, it doesn't appear to be giving me problems, but I also don't want to run into problems in the future.