SelfProtect.app is using 1GB, and seems to be part of BitDefender VPN for Mac OS. Is it essential to the operation of the VPN?
Hello.
I believe that @camarie, who works at Bitdefender as Principal Software Developer and/or @Alexandru_BD, who works for Bitdefender, can give you more insights on this matter.
Regards.
Yeah, I'll do some research and get back to you.
@Theodore99 I'm not sure to what refers SelfProtect.app - I assume this is on macOS.
There is a self protect on the Bitdefender agent, named com.bitdefender.agentui.sp (process), and the extension is com.bitdefender.agentui.sp.systemextension. This is your comment referring to?
Hello again.
I promoted you to Level 2.
You can now post screenshot(s) of the issue, so we can better understand it.
@camarie
The post was originally posted in the "Mac" category, but i moved it to the proper "VPN" category.
So, i assume that the OP is talking about Bitdefender VPN on macOS.
I imagined it's about macOS, but not being directly involved in macOS development… when I'm not sure, I ask.
Yes indeed this is in MacOS. “SelfProtect” was brought to my attention by “AppCleanerAndUninstaller.app”, and as you see from the attached image there is nothing beside the title “SelfProtect” beyond the indication that it is using 1.06GB. Further down in the image see that it is a kernel extension located in /Library/Bitdefender/… .
I do note this morning that AppCleaner … associates with SelfProtect several pieces of code involving Bitdefender…Agent, Bitdefender … Uninstaller, etc.
All of this suggests that I would make a mess of BitDefender by telling AppCleaner to remove SelfProtect.
So here’s the bottom line from my point of view (which I offer in a spirit of charity, having used Bitdefender on my machines years for more than 10 years). The published Support documentation should inform us about what this important bock of code is doing and why tampering with it is a bad idea; since all we see at first is this strange name “SelfProtect”.
Thank you for detailing. I passed this along to the VPN/macOS guys, and, while I'm not sure how things works there, the message has been received.
