[Feature Request] Please detect and remove Windows usernames from paths (in logging)

[dio-gh]

Currently, the emu logs contain full paths, meaning that on Windows, if the user has either their gamefiles or their RPCS3 folder located somewhere under their home folders, the username will land in the log (and possibly uploaded to here or to Discord).

This means that possibly personal data ends up in the logfiles, which is not very cool. Since this is something actually detectable and removeable (as opposed to any other piece of sensitive data that the users may mistakenly put into the path), I'd ask for this detection and anonymization to be done.

Furthermore, the user should be prompted in the first launch welcome message, that should the paths leading to their RPCS3 installation or their game files contain any sensitive information, they should look out for that (and that usernames are not included in this, on Windows).

[Asinin3]

Agree with censoring names in username folder, I actually suggested this back in 2018. Would be bad to see someone get Doxxed and could be more likely to happen to some popular Youtuber sharing a log or something. Don't agree with the warning message though, might put some people off and seems kinda pointless.

Would be nice to have another way of identifying a user without their username folder though e.g when we have people ban evading. Maybe someone has an idea for that, like hashing the name of the username folder. It would be some gibberish but still identifiable.

[elad335]

What I think is to replace full user path manually with a token which represents the user directory ike $user-directory/...

[arabek]

$HOME is the standard way to refer to user dir in all unix environments. Maybe use that as a universal mnemonic?

[MSuih]

The problem here is that we have file path printing in multiple locations across the codespace. If even one of those isn't handled properly (or someone adds a new one without carefully checking it) then paths will be exposed in log.

[arabek]

@MSuih In optimal case - file path logging would be handled by a path_logger function that'd sanitise all the output, and all places the code logs from would go trough that path_logger function to not leak the sensitive data. Of course, if someone carelessly adds a new function without using it - it'll expose stuff, but one can't pessimistically assume that.

[dio-gh]

Don't agree with the warning message though, might put some people off and seems kinda pointless.

I felt that was important, if we're making an attempt to address this properly, may as well go the whole way.

What I think is to replace full user path manually

That's fine, but not every place is under the user home folder, so might be overkill.

[MiYakuGaming]

I agree with this, I don't want my future business information revealed.

[dio-gh]

Wasn't taken seriously. Closing.

[elad335]

I don't understand why closing.

[HerrHulaHoop]

Don't see anyone rejecting this feature request. Just that doing it properly requires effort and nobody has invested it yet.

[dio-gh]

I must have misinterpreted the responses then. Either way, I'm unsubscribing, please track it to completion on behalf of me then.