SHA-512 hashing support in glib

Posted by elima on November 21, 2012

Always feels good to close old bugs, even if done unintentionally. In one of the projects I’m working on, I ran into the lack of SHA-512 support in glib and decided to step in. It turned out that such support was requested in a bug reported 3 years ago.

Whatever the reasons, the good news is that the next release of glib will ship with support for SHA-512 hashing in GChecksum. The implementation strictly follows the FIPS-180-2 standard.

Thanks to Emmanuele Bassi for reviewing my patch, Julian Andres Klode for merging it, and Igalia for sponsoring my dedication.

Trackbacks

Use this link to trackback from your own site.

Comments

Leave a response

  1. Julian Andres Klode Wed, 21 Nov 2012 23:58:19 CET

    It also was the first time I pushed something to glib. Given that I reported the bug, it seemed like the right thing for me to push the fix. Thanks for your work on this.

  2. Mathias Thu, 22 Nov 2012 04:27:16 CET

    Rationale for using 384 instead of 512 or 256:
    https://plus.google.com/114471118004229223857/posts/hzoUxXhhkBf

  3. foo Thu, 22 Nov 2012 06:05:54 CET

    What about SHA-3?

  4. elima Thu, 22 Nov 2012 08:49:43 CET

    Mathias, thanks for the link. Thing is that in practice, SHA-512 is far more commonly used than SHA-384, at least from my experience. In fact, I don’t know any piece of software using the truncated version right now. I won’t argue about the reasons, since I’m not an expert.
    So I would say that when people start coming with use cases for SHA-384 support, it will get into glib. (as you know from the bug report, the algorithm is already implemented).

    foo: SHA-3 will be supported when we have real world glib apps needing it, I guess.

Comments

What is 12 + 6 ?
Please leave these two fields as-is:
IMPORTANT! To be able to proceed, you need to solve the following simple math (so we know that you are a human) :-)