Is this expected behaviour? For me this looks like nothing, the crypt(3)
function of glibc even supports. Do I have to use an external gem to
generate sha512-crypt hashes?
Can you put this in the form of a bug report on Github with some code
to reproduce the effect?
We certainly don’t use the libc crypt but we should produce the same
result as MRI.
An alternative that you (or we) could potentially use would be to FFI
bind the actual crypt function. I’ve done a prototype here: https://gist.github.com/headius/6625851
Could this be some gem which is monkey-patching this method?
This output has been what I have expected from crypt for the last 25+
years
(2char salt prepended to front), but I agree this version of crypt is
getting outdated and probably should be a much more robust one-way hash
Perhaps this is just a difference as Charlie mentioned that glibc#crypt
is
different on different OSes now (I am running on MacOS)? If so then we
will for sure need to use FFI to hook into this…