-
-
Save earthgecko/3089509 to your computer and use it in GitHub Desktop.
#!/bin/bash | |
# bash generate random alphanumeric string | |
# | |
# bash generate random 32 character alphanumeric string (upper and lowercase) and | |
NEW_UUID=$(cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1) | |
# bash generate random 32 character alphanumeric string (lowercase only) | |
cat /dev/urandom | tr -dc 'a-z0-9' | fold -w 32 | head -n 1 | |
# Random numbers in a range, more randomly distributed than $RANDOM which is not | |
# very random in terms of distribution of numbers. | |
# bash generate random number between 0 and 9 | |
cat /dev/urandom | tr -dc '0-9' | fold -w 256 | head -n 1 | head --bytes 1 | |
# bash generate random number between 0 and 99 | |
NUMBER=$(cat /dev/urandom | tr -dc '0-9' | fold -w 256 | head -n 1 | sed -e 's/^0*//' | head --bytes 2) | |
if [ "$NUMBER" == "" ]; then | |
NUMBER=0 | |
fi | |
# bash generate random number between 0 and 999 | |
NUMBER=$(cat /dev/urandom | tr -dc '0-9' | fold -w 256 | head -n 1 | sed -e 's/^0*//' | head --bytes 3) | |
if [ "$NUMBER" == "" ]; then | |
NUMBER=0 | |
fi |
on macOS (/dev/urandom does not spits out any valid CTYPE, is this M1 related?)
# generate single letter in range a-z
head /dev/urandom | base64 | tr -dc 'a-z' | fold -w 1 | head -n 1
The base64
approach is interesting to make every byte count (for a-zA-Z and 0-9). only I am not really sure if base64 maps the bytes uniformingly on a-zA-Z0-9 . I didn't check so far, has anyone experience?
@pier4r that's a fair question, though base64 breaks streams in 6bits chars, given that the source of randomnes should minimize the correlation between the previous N bits and the current ones, the only reduction of information is due to the tr step, which is intrinsic in the goal of the opertions (generate range of alphachars/numbers/both)
base64
should be the best thing you can do. This way no incoming bit will be ignored. tr
on the other hand is not the best thing in my opinion. But it also would be a bit more complicated if you always want to make every bit count.
When generating one or two 10-20 char length strings which method you pick up probably is not that important.
How about putting the question differently - which method would be least resource-intensive and won't require installation of additional tool? Let's imagine you need to generate 5000 strings each 160 char length.
invisible see https://gist.github.com/earthgecko/3089509#gistcomment-3827754 (achieved on a very small footprint OS, openwrt)
@pier4r Thanks. But what performance would look like compared to other methods?
@invisible999 don't know, one needs to make a benchmark with the various proposed methods (and likely others published elsewhere)
how do i generate the string cat /dev/urandom | tr -dc 'a-zA-Z0-9' | fold -w 32 | head -n 1 but have the first half as dedicated set characters
@UdaniWijesinghe just remove the
0-9