Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: Accelerating SHA256 by 100x in Golang on ARM

blog.minio.io

Post reply on HN
Print view View original

11–20 of 93 posts

Re: Show HN: Accelerating SHA256 by 100x in Golang on ARM

#14

Post by fwessels »

anonymous7777 wrote: post #8

ok mentioning Go here is a bit pointless. How did Go help compared to any other language when Arm has hardware instructions for SHA1&2?

Go didn't help specifically, it is just that this package makes support for the ARM SHA instructions available for Golang.

Re: Show HN: Accelerating SHA256 by 100x in Golang on ARM

#16

Post by fwessels »

wyldfire wrote: post #3

... by moving from a software implementation to a mostly hardware one. ;) Still a worthwhile article but the title seemed to make me think of implementation/algorithm changes.

No, there are no algorithm changes (otherwise the results would be different), it is just taking advantage of the ARM SHA accelerations when they are available.

Re: Show HN: Accelerating SHA256 by 100x in Golang on ARM

#17

Post by jerf »

niftich wrote: post #5
loeg wrote: post #4

Earlier quoted context omitted.

AES and SHA2 are completely different algorithms. > Also, this is another really good reason never to use a sha2 as your hashing algo for password storage. I don't know what you mean by this. I understand that SHA2 is poor for some things, but I'm not sure how this illustrates that.

> but I'm not sure how this illustrates that SHA2 just got even faster, so it illustrates rather well that you wouldn't want to use it for password storage -- of course that was always true, but the improvement drives that point home.

Even if the ARM processor on a cycle-by-cycle basis keeps up with already-existing GPU SHA2 crackers (which I do not know), it will not keep up with the parallelism in the GPUs, which is easy for anybody to get through hashcat: https://hashcat.net/wiki/

SHA2 has not gotten faster. It was already blisteringly, unbelievably fast.

Re: Show HN: Accelerating SHA256 by 100x in Golang on ARM

#18

Post by WhitneyLand »

niftich wrote: post #5
loeg wrote: post #4

Earlier quoted context omitted.

AES and SHA2 are completely different algorithms. > Also, this is another really good reason never to use a sha2 as your hashing algo for password storage. I don't know what you mean by this. I understand that SHA2 is poor for some things, but I'm not sure how this illustrates that.

> but I'm not sure how this illustrates that SHA2 just got even faster, so it illustrates rather well that you wouldn't want to use it for password storage -- of course that was always true, but the improvement drives that point home.

My understanding is that SHA2 is fine for password storage, given a prudent number of hashing rounds.

Re: Show HN: Accelerating SHA256 by 100x in Golang on ARM

#19

Post by creshal »

niftich wrote: post #5
loeg wrote: post #4

Earlier quoted context omitted.

AES and SHA2 are completely different algorithms. > Also, this is another really good reason never to use a sha2 as your hashing algo for password storage. I don't know what you mean by this. I understand that SHA2 is poor for some things, but I'm not sure how this illustrates that.

> but I'm not sure how this illustrates that SHA2 just got even faster, so it illustrates rather well that you wouldn't want to use it for password storage -- of course that was always true, but the improvement drives that point home.

If you're using any hash directly for password storage you're doing it wrong, regardless of the specifics.

PBKDF2-SHA2 with a reasonably high amount of rounds (>100000) is still okay-ish, although you should have transited to bcrypt years ago. And hopefully we'll see argon2 stabilizing and getting adoption soon™.

Post reply on HN