- Code: Select all
% llh
total 832K
-rw-r--r-- 1 me users 413K Feb 27 2017 shattered-1.pdf
-rw-r--r-- 1 me users 413K Feb 27 2017 shattered-2.pdf
% ll
total 832
-rw-r--r-- 1 me users 422435 Feb 27 2017 shattered-1.pdf
-rw-r--r-- 1 me users 422435 Feb 27 2017 shattered-2.pdf
% sha1sum shattered-1.pdf shattered-2.pdf
38762cf7f55934b34d179ae6a4c80cadccbb7f0a shattered-1.pdf
38762cf7f55934b34d179ae6a4c80cadccbb7f0a shattered-2.pdf
% cmp shattered-1.pdf shattered-2.pdf
shattered-1.pdf shattered-2.pdf differ: byte 193, line 8
% sha256sum shattered-1.pdf shattered-2.pdf
2bb787a73e37352f92383abe7e2902936d1059ad9f1ba6daaa9c1e58ee6970d0 shattered-1.pdf
d4488775d29bdef7993367d541064dbdda50d383f89f0aa13a6ff2e0894ba5ff shattered-2.pdf
% sha512sum shattered-1.pdf shattered-2.pdf
3c19b2cbcf72f7f5b252ea31677b8f2323d6119e49bcc0fb55931d00132385f1e749bb24cbd68c04ac826ae8421802825d3587fe185abf709669bb9693f6b416 shattered-1.pdf
f39a04842e4b28e04558496beb7cb84654ded9c00b2f873c3ef64f9dfdbc760cd0273b816858ba5b203c0dd71af8b65d6a0c1032e00e48ace0b4705eedcc1bab shattered-2.pdf
%
The files are apparently valid PDF, the contents is well under control (nice presentation, the only striking change when looking at them with okular is a background color modification), they are reasonably small and even have the exact same size. According to the above the wikipedia page:
The attack required “the equivalent processing power as 6,500 years of single-CPU computations and 110 years of single-GPU computations”.
Granted, I don't have that at home, but I am not the bad guy, and time has passed since Feb 2017...
Besides, checking commit ids against the SF web site after every 'git pull' is... surely doable, but not great fun!
BTW, ISTR that the recurring problem encountered on the FG Jenkins installation when cloning FGData (see Torsten's messages on the ML) is the same, so unless I'm mistaken here, daweed is not alone with this.