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
I noticed when looking at some log files posted on a Joplin issue report, that where the user is a Joplin cloud user, the log file may contain mildly sensitive information. An example output with the information redacted is:
01-02T10:03:16: userFetcher: Got user: {"account_type":2,"can_use_share_permissions":0,"created_time":1696361973193,"email":"REDACTED","full_name":"REDACTED","id":"S0ttpZ09fP0v9Op8VvlXA0","inbox_email":"REDACTED","inbox_id":"","updated_time":1735840837861}
In userFetcher.ts, the code writes the owner details to the log via this line:
logger.info('Got user:', owner);
Expected behaviour
Before writing the owner details to the log, the email and full_name should to be obfuscated. The inbox_email is potentially fine to print to the log as is
Logs
No response
The text was updated successfully, but these errors were encountered:
Operating system
Windows
Joplin version
3.2.3
Desktop version info
No response
Current behaviour
I noticed when looking at some log files posted on a Joplin issue report, that where the user is a Joplin cloud user, the log file may contain mildly sensitive information. An example output with the information redacted is:
01-02T10:03:16: userFetcher: Got user: {"account_type":2,"can_use_share_permissions":0,"created_time":1696361973193,"email":"REDACTED","full_name":"REDACTED","id":"S0ttpZ09fP0v9Op8VvlXA0","inbox_email":"REDACTED","inbox_id":"","updated_time":1735840837861}
In userFetcher.ts, the code writes the owner details to the log via this line:
logger.info('Got user:', owner);
Expected behaviour
Before writing the owner details to the log, the email and full_name should to be obfuscated. The inbox_email is potentially fine to print to the log as is
Logs
No response
The text was updated successfully, but these errors were encountered: