fix(server): don't log invalid token in release builds #112
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The server logs a sent token, if the token is not valid:
e.g.:
rpaste -a invalid_token -V
This change prints the token only in debug mode. In release mode the log entry will look like this:
Motivation and Context
fixes #111
Let's say you use rpaste with the token in the config file (or curl with the auth_token as env var or in a file), but use different rustypaste servers. If you forget only once to add the
-a
flag (or add the header to curl), a production token for another instance will be logged.How Has This Been Tested?
Changelog Entry
Types of Changes
Checklist: