News for hackers. Stuff that matters.

A comment on SHA-1 Collision Detection on GitHub.com.

Re:SHA-1 Collision Detection on GitHub.com by homakov on Monday March 20, 2017 @07:02PM (#13918394)
Consider detecting this too https://gist.github.com/homakov/c11f1e3b8b35300ffa07abf95a64...
[ Parent | on HN ]
Re:SHA-1 Collision Detection on GitHub.com by uwu on Monday March 20, 2017 @07:39PM (#13918586)
what is it?
[ Parent | on HN ]
Re:SHA-1 Collision Detection on GitHub.com by fny on Monday March 20, 2017 @07:45PM (#13918622)
Looks like a bug with Cyrillic character highlighting. I'm guessing this is probably an issue with Rogue/Pygments[0][1] since I doubt Github is rolling their own syntax highlighter.

[0]: https://github.com/jneen/rouge

[1]: http://rouge.jneen.net/pastes/6nDQ

[ Parent | on HN ]
Re:SHA-1 Collision Detection on GitHub.com by antons_ghost on Monday March 20, 2017 @07:54PM (#13918660)
>>> "params[:sandboх] = true".decode('ascii')

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd1 in position 14: ordinal not in range(128)
[ Parent | on HN ]