I read through almost the entire chain of posts, but was not able to find a response from apple tech?
MacBook Pro 13", macOS 10.13
What exactly are you doing or running when you get that?
halo commented on Aug 10, 2018
@lwee77 Hi!
The error message you see is not specific to macosvpn in particular. I believe that error is displayed on macOS whenever a command is run with superuser privileges, without going through XPC (which is a way of communicating between processes).
I use XPC extensively in this GUI app because you don't want a GUI to have superuser privileges. Instead you talk via XPC to a small, separate executable (that has been authorized by the user) and that small executable has superuser privileges.
So it's basically a security concern and that's why it's deprecated to bypass XPC. However, in a command line tool such as macosvpn it makes sense to use the "deprecated" way, because it is an executable that is fired once and not a GUI application or a recurring process. It has been deprecated for years, but it is still perfectly valid to use it.
The error could be caused by any software on your system. Look at the prefix in the console to find out which one is causing it.
For example, if you see this:
(com.apple.quicklook[3854]): Endpoint has been activated...
then you know that Quicklook is the one causing it.
I assume that it is not macosvpn causing it when you boot into macOS recovery, because I see no reason why it should run there.
What exactly are you doing or running when you get that?
halo commented on Aug 10, 2018
@lwee77 Hi!
The error message you see is not specific to macosvpn in particular. I believe that error is displayed on macOS whenever a command is run with superuser privileges, without going through XPC (which is a way of communicating between processes).
I use XPC extensively in this GUI app because you don't want a GUI to have superuser privileges. Instead you talk via XPC to a small, separate executable (that has been authorized by the user) and that small executable has superuser privileges.
So it's basically a security concern and that's why it's deprecated to bypass XPC. However, in a command line tool such as macosvpn it makes sense to use the "deprecated" way, because it is an executable that is fired once and not a GUI application or a recurring process. It has been deprecated for years, but it is still perfectly valid to use it.
The error could be caused by any software on your system. Look at the prefix in the console to find out which one is causing it.
For example, if you see this:
(com.apple.quicklook[3854]): Endpoint has been activated...
then you know that Quicklook is the one causing it.
I assume that it is not macosvpn causing it when you boot into macOS recovery, because I see no reason why it should run there.
Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook