3 ms·

Pretty sure this is privacy related. Just enable more verbose logging to see all your personal details in said logs again.

by zappb 3y ago

lapcat 3y ago
> Pretty sure this is privacy related. 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."
- bastawhiz 3y ago
  > Apple has now decided that some log content is too private to reveal even when privacy has been removed. I came across this recently... If this is true then why is it being logged in the first place? Logs probably aren't the right way to expose that data.
  - saagarjha 3y ago
    There are surely ways to make those show up as well.
    - bastawhiz 3y ago
      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.
  - fiddlerwoaroof 3y ago
    It's better to have one place to look for diagnostic information. This sort of just-in-time masking seems optimal to me.
    - bastawhiz 3y ago
      Diagnostic information shouldn't contain secrets. If you need access to that, there are mechanisms to access it.
      - fiddlerwoaroof 3y ago
        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.

Pretty sure this is privacy related. Just enable more verbose logging to see all your personal details in said logs again.

by zappb 3y ago

Pretty sure this is privacy related. Just enable more verbose logging to see all your personal details in said logs again.

lapcat 3y ago

> Pretty sure this is privacy related. 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."

bastawhiz 3y ago
> Apple has now decided that some log content is too private to reveal even when privacy has been removed. I came across this recently... If this is true then why is it being logged in the first place? Logs probably aren't the right way to expose that data.
- saagarjha 3y ago
  There are surely ways to make those show up as well.
  - bastawhiz 3y ago
    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.
- fiddlerwoaroof 3y ago
  It's better to have one place to look for diagnostic information. This sort of just-in-time masking seems optimal to me.
  - bastawhiz 3y ago
    Diagnostic information shouldn't contain secrets. If you need access to that, there are mechanisms to access it.
    - fiddlerwoaroof 3y ago
      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.