You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The runtime hardened protection on macOS ensures processes started with runtime hardened protected binaries are not inspected or altered. As an example, it is possible to start the td-agent deamon and inspect the process with lldb.
More on hardened runtine protection can be found here
It is best practice to secure binaries and all libraries used by it with the hardened runtime protection to avoid unwanted parties to inspect memory and/or alter flow of execution.
The runtime flag can be set on a binary with
Currently, the ruby binary coming with td-agent is not hardened
The runtime hardened protection on macOS ensures processes started with runtime hardened protected binaries are not inspected or altered. As an example, it is possible to start the td-agent deamon and inspect the process with
lldb
.More on hardened runtine protection can be found here
It is best practice to secure binaries and all libraries used by it with the hardened runtime protection to avoid unwanted parties to inspect memory and/or alter flow of execution.
The runtime flag can be set on a binary with
codesign -f -s 'apple_developper_certificate' --option=runtime /opt/td-agent/bin/ruby
This will also need to be done on other libraries used by the binary (ie:
/opt/td-agent/lib/*.dylib
).Is this something we could do as part of the build process here for td-agent on macOS?
The text was updated successfully, but these errors were encountered: