> The archives should prominently display this disavowal and name the > archive "Cryptome-Disavows-This-Corrupt-Archive."
Is that how you'll label and name the files when you send them out? Seriously, John, this is getting a little ridiculous. Is it really that easy to fake a hash and sig while making thousands of files appear to be what it's supposed to be and still add up and hash correctly? Sent from my iPhone > On Nov 28, 2015, at 5:49 PM, John Young <[email protected]> wrote: > > Cryptome disavows mirrors of its archive, all of them, due to ease > and evidence of tampering with files, hashes, signatures and insertion > of implants by the host, platform, route, service or all. > > The archives should prominently display this disavowal and name the > archive "Cryptome-Disavows-This-Corrupt-Archive." > > > > At 05:10 PM 11/28/2015, you wrote: >> cryptome-nov2015.tar.bz 76GByte Nov 28 05:58 sha256 >> 22572573c0538e09bf554f475f3113fbbd33920e2bf6691f65450ea8e2333edb >> >> [ seeding... plz wait... ] >> >> Content-Type: image/png; name="cryptome-nov2015.png" >> Content-Disposition: attachment; filename="cryptome-nov2015.png" >> X-Attachment-Id: f_ihjnir3o0 > > >
