Author Topic: Why Google is Hurrying the Web to Kill SHA-1 (Read 1022 times)

Axon · « **on:** September 09, 2014, 11:19:03 pm »

Most of the secure web is using an insecure algorithm, and Google's just declared it to be a slow-motion emergency.
https://konklone.com/post/why-google-is-hurrying-the-web-to-kill-sha-1
Interesting article.

Phage · « **Reply #1 on:** September 09, 2014, 11:38:03 pm »

This is quite interesting, and a fair move by Google imo.

Pak_Track · « **Reply #2 on:** September 10, 2014, 12:07:08 pm »

Doesn't SMF use sha1?

Stackprotector · « **Reply #3 on:** September 10, 2014, 12:54:52 pm »

Doesn't SMF use sha1?

I think we can easily replace that

Pak_Track · « **Reply #4 on:** September 10, 2014, 03:46:15 pm »

I think we can easily replace that

Well then, another entry into aplha's bucket list?

Stackprotector · « **Reply #5 on:** September 10, 2014, 04:25:41 pm »

We could implement it into SMF. Just wrap another hashing algo around sha1 and hash all passwords

Pak_Track · « **Reply #6 on:** September 10, 2014, 04:33:53 pm »

We could implement it into SMF. Just wrap another hashing algo around sha1 and hash all passwords

And what hash would that be?
I suggest sha1, covered with double md5 [emoji1]

kenjoe41 · « **Reply #7 on:** September 10, 2014, 05:02:31 pm »

There is already sha-2

flowjob · « **Reply #8 on:** September 10, 2014, 05:55:36 pm »

There is already a sha-3 too

Axon · « **Reply #9 on:** September 11, 2014, 11:55:53 pm »

EvilZone