Title
#core
theopolis

theopolis

12/03/2019, 1:40 PM
We might have to create a 4.1.2. Even after spending a lot of time with the new CPack configuration I did not notice the change in launchdaemon name from
com.facebook.osqueryd
to
com.osquery.osqueryd
and the
osqueryctl
tool had not been updated, nor did we include logic to remove the old path. This is not great and we should consider reverting this change back to
com.facebook.osqueryd
. An alternative is to add logic to
osqueryctl
to rename the existing launchdaemon path.
s

seph

12/03/2019, 1:45 PM
Com.osquery is wrong, we'd be io.osquery, right? While I think we should update osqueryctl, I'd also support fixing the launchdaemon name.
1:46 PM
Renaming feels like a 5.0 target.
theopolis

theopolis

12/03/2019, 1:47 PM
More importantly, if we are renaming we need to communicate and consider what migration/cleanup looks like for the old targets.
s

seph

12/03/2019, 1:47 PM
Yep!
2:07 PM
I made https://github.com/osquery/osquery/issues/6094 and a 5.0 milestone as placeholders