Sort:  

Run the ruby code. Author of the gist says it fails ~1 in 100 runs.

That is... BIZARRE. Since encryption should be rock-solid-consistent.

OMG! Sounds like a deliberately planted exploit for the software author to come back later.

This is exactly the type of thing I believe keeps happening in open source code. Contributors (we don't know everyone's motives) can purposely implant inconsistencies and milk them later anonymously without people knowing who exploited the code.

(..and since a lot of projects borrow existing code, it means an exploit can turn up in multiple projects....)

The amount of SSL related updates in the last 3 years drives me crazy.

Coin Marketplace

STEEM 0.09
TRX 0.31
JST 0.031
BTC 107864.55
ETH 3867.17
USDT 1.00
SBD 0.60