Remove reference to "privacy" for base 36 encoding [develop] #447
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Base 36 encoding the entry ID gives no privacy whatsoever as it's not a hashing function. The only way of not being able to retrieve the original ID – without bruteforcing – would be to use a [hashids](http://hashids.org/)-like transformation.
Fantomas42
added a commit
that referenced
this pull request
Oct 20, 2015
Remove reference to "privacy" for base 36 encoding [develop]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Base 36 encoding the entry ID gives no privacy whatsoever as it's not a hashing function. The only way of not being able to retrieve the original ID – without bruteforcing – would be to use a hashids-like transformation.
Copy of #446 on the right branch.