@denysvitali Thank you! I guess this is OK, but could you add a spec to show that it compiles and works correctly?

Oh, wait... actually, we have OpenSSL::Digest which allows all of these algorithms. Maybe OpenSSL::Sha1 is a remanent and should be removed.

@asterite Looks like sha1/md5 use a more direct/simple call than Digest though. I'll try benchmarking them to see if there's any difference.

Benchmark results here: https://gist.github.com/RX14/c031d230346cc7d0b78b453c65c0a6a7

However the man page states:

Applications should use the higher level functions EVP_DigestInit(3) etc. instead of calling the hash functions directly.

I think we should eventually (before 1.0) provide more high-level interfaces to crypto functions like SHA1 which we could optimise behind the scenes as we wish.

I suppose that it should be closed and stay unmerged.