No, it has /dev/urandom, but tr is not able to consume it without explicitly setting LC_CTYPE=C, otherwise it complains about invalid input. Once you get past that hurdle, the options do not behave the same way, and '-dc' ends up selecting the complement of the set rather than deleting it, so you end up with only unprintable characters.
No, it has /dev/urandom, but `tr` is not able to consume it without explicitly setting `LC_CTYPE=C`, otherwise it complains about invalid input. Once you get past that hurdle, the options do not behave the same way, and '-dc' ends up selecting the complement of the set rather than deleting it, so you end up with only unprintable characters.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
dboreham
telackey
Add instructions for deploying an action runner on macOS. Also fix a small script bug on macOS that prevents deployment with SO.
@@ -10,2 +10,3 @@secure_password() {cat /dev/urandom | tr -dc A-Za-z0-9~_- | head -c 10 && echo# extra bytes so that even if we delete some chars we will still have plentyopenssl rand -base64 32 | tr -d '\/+=' | head -c 10 && echoShould also change the comment in line 9 since it no longer pertains?
(but probably this change should be in a separate PR?)
Done
Was the change necessary because macos doesn't have
/dev/urandom?No, it has /dev/urandom, but
tris not able to consume it without explicitly settingLC_CTYPE=C, otherwise it complains about invalid input. Once you get past that hurdle, the options do not behave the same way, and '-dc' ends up selecting the complement of the set rather than deleting it, so you end up with only unprintable characters.Might be worthwhile adding a comment saying openssl used because it's available and works on both macos and Linux?
Added