rfc:uniqid
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:uniqid [2016/09/12 02:48] – yohgaki | rfc:uniqid [2016/09/13 07:11] – yohgaki | ||
---|---|---|---|
Line 21: | Line 21: | ||
* Current entropy range: About 1 billion | * Current entropy range: About 1 billion | ||
- | * Proposed entropy range: 2^50. About 1048567 billions | + | * Proposed entropy range: 2^50 or more. About 1048567 billions. |
===== Proposal ===== | ===== Proposal ===== | ||
+ | * Change " | ||
* Enable "more entropy" | * Enable "more entropy" | ||
* Use php_random_bytes() as entropy source. | * Use php_random_bytes() as entropy source. | ||
- | ==== Note on usage ==== | + | <code php> |
+ | string uniqid([string $prefix [, int $number_of_entropy_chars ]]); | ||
+ | </ | ||
+ | |||
+ | Where $number_of_entropy_chars are: | ||
+ | |||
+ | * 0 for disable more entropy. (Compatible with current $more_entropy=FALSE) | ||
+ | * 1 for 10 digits entropy. (Compatible with current $more_entropy=TRUE. About 30 bits entropy) | ||
+ | * 13 to 255 for number of entropy [0-v]{13, | ||
+ | |||
+ | |||
+ | == Note on usage == | ||
Users should never use uniqid() for any crypt related purposes even with this change. uniqid() does not provide crypt secure random value. Users should use random_bytes() for crypt purposes. | Users should never use uniqid() for any crypt related purposes even with this change. uniqid() does not provide crypt secure random value. Users should use random_bytes() for crypt purposes. | ||
- | ==== Note on performance | + | == Note on performance == |
usleep(1) is not used when "more entropy" | usleep(1) is not used when "more entropy" | ||
- | ==== Note on uniqueness | + | == Note on uniqueness == |
Although it is unlikely, uniqueness is _not_ guaranteed even with this proposal, but this proposal improves uniqueness a lot. This nature will be documented in the manual. | Although it is unlikely, uniqueness is _not_ guaranteed even with this proposal, but this proposal improves uniqueness a lot. This nature will be documented in the manual. | ||
Line 135: | Line 147: | ||
===== Rejected Features ===== | ===== Rejected Features ===== | ||
Keep this updated with features that were discussed on the mail lists. | Keep this updated with features that were discussed on the mail lists. | ||
+ | |||
+ | ===== ChangeLog ===== | ||
+ | |||
+ | * Made 2nd parameter a int |
rfc/uniqid.txt · Last modified: 2021/07/07 09:30 by cmb