TheCthulhu / CthulhuSec to Cryptome

[Steve Kinney]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/20/2015 08:21 PM, Michael Best wrote:
> I'm curious what everyone thinks. I personally agree with 
> TheCthulhu, but I'm not a tech or crypto expert.
> 
> Original: https://www.thecthulhu.com/a-response-to-cryptome/
> 
> So today (20th December) I posted a mirror of the Cryptome
> archive I received from a close associate of mine (of whom I
> trust greatly) and was met by a rather blunt response from the
> Cryptome administrators regarding the integrity of the data I
> host. As many know, I take the subject of tampering very
> seriously, and whenever I have leaked or shared data I strive
> to provide it with a SHA1 and SHA256 hash at a minimum and also
> provide torrents, HTTPS and onion download options.
> Furthermore, if ever asked, I would also sign files using my
> personal PGP key.

JYA is already performing above and beyond the call of duty in the
area of integrity assurance, by posting a disclaimer that disavows
the provenance, integrity, and fitness for use for any purpose of
anything found floating at Cryptome.

Using form and context to affect human behavior is an architect's
stock in trade. Decorating Cryptome with a veneer of truthiness
and trustability would be a very poor design choice.

:o)




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJWeFsgAAoJEDZ0Gg87KR0LZlIP/iHGAzFhPIaMFwQHjpwe7X13
3AHr0diVumy4XwzosySDlrkfEFlSqObCwHCB019P/clJ335GJVcZBqFZlqR+b0Xw
6hM77oT7GBW4zGL4ntQiSYiJS9sV/2gm/49pKQrqqnb6CXE5HwQfxjVSExvPag8v
iT9rXu2FaoQG6/nVDTioB1eSLLHgvlSwjtdruHLq6lexAMFXHfxtLjzbrjlaVJZR
BWzREo/JmR3HjLxBV0P9RCvpfs0knoRwV6cyqWMXSk5AgAoY07EZvk00lA6vZjOP
lvq2n9auRpR8/exPtbVmXWNFfji0b5QVFPbjve4TQ3BBPuGIKXpHbVKTE29B5Rvj
tw3RFFF9f6pes08d0QLlqWNfw5JVPIRUKBpvUJpWyILC03hW785a5cEdYUAI3Onv
93GVOMVY7BOCdD3/0g5vL7MiiBeeVMz68p7mvNPAg3ulCJgkECofxpP1Q6N/AigZ
xuzbGtkMv9NmVRHMNf84Zc7z3I2urC2RaQaHFNPL/gUO357xlJuWxxc/4+TidKr1
LuEnM3LMXFouDOqkXJFSmw2NAmlPB9yK1pnWK28aXuITrIH5AvnUeoVbBAWSVACa
VNdDqZyWt1P0GJnAc5qbk5i0bCZVCCGBHytYQkNM0UZstpdsVRv/02H2iJ9XeM2S
fla8yccPO4GMpjvPM3Qz
=hvM3
-----END PGP SIGNATURE-----