We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It is possible to run the module by passing in a user name and password, for example:
svn_report = svn.remote.RemoteClient(svn_item, username=user_name, password=mypassword_as_a_string ) svn_report.export(target_dir)
Even if you have followed all the good practices for handling passwords within your code, the svn package has two issues:
CommonBase
The password should be obscured before the errors or logs are made
The text was updated successfully, but these errors were encountered:
This ticket is a partial duplicate of #125
Sorry, something went wrong.
I have submitted a Pull Request with a fix in it. Hopefully it will be accepted.
Any plans for accepting the PR? I must admit I don't feel safe using the package with this problem on it.
This issue only affects the case where the credentials are being passed through Python. In many case there are other ways to avoid the issue:
That said I am not sure who we need to lobby/persuade to get the updates through.
No branches or pull requests
It is possible to run the module by passing in a user name and password, for example:
Even if you have followed all the good practices for handling passwords within your code, the svn package has two issues:
CommonBase
the full svn command is sent to the debug logThe password should be obscured before the errors or logs are made
The text was updated successfully, but these errors were encountered: