@KevinSchildhorn I'm not sure that approach really makes sense in the context of Kermit. The reason is because when os_log is used directly, the default is for static strings to be displayed as public, and for dynamic strings to be private. In the context of Kermit, because we're delegating to os_log, everything is considered dynamic.

Users wouldn't expect the behavior of everything-private-by-default. They would expect logs to be public, just as they are on other platforms, and would elide dynamic data that should not be logged before sending it to Kermit. They would need to do this for the other platforms they are running on in any case. Therefore, I think it makes sense to use %{public}s by default, as that would offer consistency across platforms, and follow the principle of least surprise for users.

All that being said, I've done the implementation of opt-in public logging anyway. However, I can remove that second commit, or alternatively reverse the default, if you agree with my argument above.

Note also that this change will now conflict with #409. After that PR is merged, I can rebase this one.

Thank you for adding the opt-in for public logging. We understand your argument and the expected behavior, however we don't want to change the default implementation silently at this time. There may be existing users of Kermit that have sensitive data in their logs, and we don't want to change their logs that they expect are private to suddenly be public.

Thank you for adding the opt-in for public logging. We understand your argument and the expected behavior, however we don't want to change the default implementation silently at this time. There may be existing users of Kermit that have sensitive data in their logs, and we don't want to change their logs that they expect are private to suddenly be public.

Sounds good. I see you're already merged the conflicting changes into this branch. Were there any other changes needed here?