Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Obfuscating the /home/username path with system variable for user path #141

Closed
spirillen opened this issue Dec 21, 2020 · 6 comments
Closed
Assignees

Comments

@spirillen
Copy link
Contributor

Is your feature request related to a problem? Please describe.
See title

Describe the solution you'd like
Obfuscating the /home/SomeRealUserName with default system variables as $HOME in log outputs

This will help protect the real identity of a user, hence lift the level of privacy from a copy/paste interaction

@funilrys funilrys self-assigned this Dec 21, 2020
@funilrys funilrys added this to the 4.0.0 milestone Dec 21, 2020
@spirillen
Copy link
Contributor Author

APPENDIX 1:

Maybe only use relative path in output rather than full path?

@funilrys
Copy link
Owner

The output directory can virtually be everywhere!!

@funilrys
Copy link
Owner

This is going to be a nightmare to write because of the cross-platform (*nix, macOS, windows, ...) support but there has to be a way to do this.

The reason, I had that path explicitly, is because I'm thinking a bit ahead of what is coming. For example: How to know which data are from a single file in the filesystem the day we will have to play with an API that virtually anybody can use to retrieve its own data.

@funilrys
Copy link
Owner

funilrys commented Dec 21, 2020

I really don't want to force everyone to use a special PyFunceble directory location in their filesystem.
Therefore the full path. But I'm willing to make a concession on the storage of the full path in order to protect the real identity of a user.

By the way: In a traceback, we can't change the full path (at least not without heavy computation).

@spirillen
Copy link
Contributor Author

I know, that's why I was a bit un-precise in my suggestion, as this need to be thought throug before programming

@funilrys funilrys modified the milestones: 4.0.0, __future__ Jan 4, 2021
@funilrys
Copy link
Owner

Closing because of #215.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Development

No branches or pull requests

2 participants