Under the section heading "Privacy", the author wrote: "Censorship to maintain privacy is an important feature in the Unified log, and is responsible for so many of its entries being peppered with <private> instead of revealing potentially sensitive data."
So yes, this is privacy-related.
> Just enable more verbose logging to see all your personal details in said logs again.
From the article:
"Apple has now decided that some log content is too private to reveal even when privacy has been removed. I came across this recently..."
"Of course, it may be possible to turn this additional privacy off, but the documentation leads us once again to a guessing game."
This is overly general: whether or not secrets should be in diagnostic information depends on what you’re trying to diagnose. I’ve written PAM modules, for example, and logging TOTP secrets and passwords was absolutely essential for development purposes, even if I eventually deleted the relevant code for production.
But you shouldn't! Could you log your DB creds to your error logs for debugging? Sure! But they shouldn't go there! If you need to check them, use the mechanism for accessing creds.
Under the section heading "Privacy", the author wrote: "Censorship to maintain privacy is an important feature in the Unified log, and is responsible for so many of its entries being peppered with <private> instead of revealing potentially sensitive data."
So yes, this is privacy-related.
> Just enable more verbose logging to see all your personal details in said logs again.
From the article:
"Apple has now decided that some log content is too private to reveal even when privacy has been removed. I came across this recently..."
"Of course, it may be possible to turn this additional privacy off, but the documentation leads us once again to a guessing game."