Scribd
Upload
71 views3 pages

Cryptome: Correction On Cryptome Publication of State Department Cables

The exchange discusses a correction to a previous statement made by Cryptome regarding its publication of US State Department cables. Cryptome had stated it did not publish the files, but an investigation found it had published torrent files to access the decrypted cables. Cryptome acknowledges the earlier statement was mistaken and agrees to tweet a correction. The individual who uncovered the mistake is fine with or without credit, their main concern is clarifying the record to avoid accusations against Cryptome or Assange's legal defense. Cryptome then proposes publishing the email exchange for transparency around the issue.

Uploaded by

Yakov Zinoviev
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
71 views3 pages

Cryptome: Correction On Cryptome Publication of State Department Cables

The exchange discusses a correction to a previous statement made by Cryptome regarding its publication of US State Department cables. Cryptome had stated it did not publish the files, but an investigation found it had published torrent files to access the decrypted cables. Cryptome acknowledges the earlier statement was mistaken and agrees to tweet a correction. The individual who uncovered the mistake is fine with or without credit, their main concern is clarifying the record to avoid accusations against Cryptome or Assange's legal defense. Cryptome then proposes publishing the email exchange for transparency around the issue.

Uploaded by

Yakov Zinoviev
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

CRYPTOME

Correction on Cryptome Publication of State Department Cables

September 25, 2020

Date: Fri, 25 Sep 2020 08:01:32 -0700


From: "Mx. Yzptlk" <xxx@xxx>
To: John Young <[email protected]>
Subject: Re:
Date: Thu, 24 Sep 2020 18:37:48 -0700
From: "Mx. Yzptlk" <xxx@xxx>
To: [email protected]

You said before, on your site and in an email to me, that you didn't
publish those files. What's going on?
https://www.theguardian.com/media/2020/sep/24/us-never-asked-wikileaks-rival-
cryptome-remove-leaked-cables-court-told-assange

--
A narrow and tall one

Date: Fri, 25 Sep 2020 08:02 -0700


To: "Mx. Yzptlk" <xxx@xxx>
From: John Young <[email protected]>
Subject: Re:

Got a date for that?

Date: Fri, 25 Sep 2020 08:01:32 -0700


From: "Mx. Yzptlk" <xxx@xxx>
To: John Young <[email protected]>
Subject: Re:

March 9. "Assange's counsel mistated that Cryptome hosted, and still


hosts, the State Department cables. Cryptome posted, and still hosts,
the torrents for accessing the cable files after decrypting the torrents
with the book-published password. But did not publish the very large
files themselves." -
http://web.archive.org/web/20200309162730/http://cryptome.org/

Your statement to the court appears to be right that z.7z is the cables,
though.

FWIW, I'm not trying to cause trouble for anyone. I see nothing
inaccurate in your statement to the court. I don't think anyone did
anything wrong.

I'm just confused because the two statements look contradictory.

--
A narrow and tall one

Date: Fri, 25 Sep 2020 11:15 AM -0700


To: "Mx. Yzptlk" <xxx@xxx>
From: John Young <[email protected]>
Subject: Re:

You're right. Forgot that post, it's wrong. Thanks. I'll tweet a
correction. Somebody could find what you found and use it for
malign purpose. We don't mind malign purposes, BTW, do them
ourselves.

You want credit?

Date: Fri, 25 Sep 2020 09:17:32 -0700


From: "Mx. Yzptlk" <xxx@xxx>
To: John Young <[email protected]>
Subject: Re:

Sure, I guess? I don't care about credit for this either way, honestly.

The whole thing seems like an easy mistake to make since in that post I
think you referenced the xyz directory for the torrents, but the z.7z
was in a different subdirectory (just /z/ ?) and heavily compressed.

I think the main thing is just make it clear that the earlier post was a
mistake so no one attacks the defense or accuses y'all of perjury or
whatever the U.K. equivalent is. The whole thing should be easy to prove
since your statement and the current version of Cryptome both "show the
math" anyway and Wayback Machine confirms z.7z has consistently been
there for years... but you know how people grab onto initial headlines.
Plenty of folks would remember that and not a later correction.

--
A narrow and tall one

Date: Fri, 25 Sep 2020 01:20 PM -0700


To: "Mx. Yzptlk" <xxx@xxx>
From: John Young <[email protected]>
Subject: Re:

I tweeted a correction before getting this. Now I'm inspired to


publish our emails for your comments are quite relevant to the
Assange hearing charade.

Got an opinion on publishing the messages? If so, what ID for you?

Sure, this is entrapment of you, but that's what you have initiated
here and previously, not only for me. So the messages are going
up in the same way I kept tweeting information about the cables
different from what the defense wanted, that is the fucking of me
they wanted.

You might also like