[cryptome] Re: Cryptome has been leaking its user logs for over a year

  • From: Shelley <shelley@xxxxxxxxxxxxxxxx>
  • To: <cryptome@xxxxxxxxxxxxx>
  • Date: Thu, 08 Oct 2015 22:59:48 -0700

Mike,

While you're updating the post, you might want to change the urls to be all lowercase (there are still DNS issues with caps; links aren't working.)

This whole thing has been so odd. I apologize on behalf of the rude replies, but it's not uncharacteristic of the list. Ignoring data is, though. Doesn't matter that it was info sent over the clearnet; I don't understand how they are missing the bigger picture. I don't want to believe it is willful because there is enough craziness in this world as it is, but I'm beginning to wonder...

Remember to get some rest :)
-Shelley


----------
On October 8, 2015 10:49:08 PM Michael Best <themikebest@xxxxxxxxx> wrote:

Text has been updated to reflect that bandmon is not coderman and that the
torrent is a re-upload. Sorry about that. I, and I'm sure many others,
would appreciate sha-256 hashes or something similar to help verify that
nothing was changed.

I also changed the website's entry from coderman[at]gmail.com to
coderman@xxxxxxxxx.

--Mike


> i'm not sure who bandmon is, but they're not coderman@xxxxxxxxx. i
> would however be amenable to uploading a list of sha-256 digests to
> verify components of similarity between the torrent and origin.


On Fri, Oct 9, 2015 at 1:25 AM, Michael Best <themikebest@xxxxxxxxx> wrote:

> Writing this at 01:23 AM, please forgive any typos or editing errors.
>
> I'm updating the page to clarify that coderman is not bandmon. Thank you
> for clarifying, coderman. The piratebay torrent is, I believe, made from
> the zoinks torrent listed in places like
>
> https://mailman.stanford.edu/pipermail/liberationtech/2014-September/014344.html
>
>
> http://liberationtech.stanford.narkive.com/arhyVT9j/data-mine-the-snowden-files-was-open-the-snowden-files#post14
> and
>
> https://www.reddit.com/r/onions/comments/2afpmi/how_to_obtain_a_cryptome_archive_courtesy_coderman/
>
> If that torrent isn't based on your release, with a hash of
> F5763EB5C5FFD8B40B9047CF72350D320A59BDAC
> <https://zoink.it/torrent/F5763EB5C5FFD8B40B9047CF72350D320A59BDAC.torrent>,
> then it may be a different release from yours. If you can check that and
> let me know, I'll update the post to make sure that it's accurate as far as
> involving you. (If possible, please check for the files in your own copy of
> the Cryptome archive. /USB-1.rar/Disk
> 2/07-Cryptome-org-13-0702-cartome-directory.zip/awstats)
>
> Thanks for correcting my mistake, coderman - sorry for incorrectly
> assuming that you were bandmon.
>
> *coderman* coderman@xxxxxxxxx
> <coderman%40gmail.com?Subject=Re%3A%20%5Bcryptome%5D%20Cryptome%20has%20been%20leaking%20its%20user%20logs%20for%20over%20a%20year&In-Reply-To=%3CCAJVRA1TAeEfByH4n%3DOUyBVQZJT%2BgBK4yENjjtTBwmxGN_wbH4A%40mail.gmail.com%3E>
> *Thu Oct 8 21:42:07 EDT 2015*
>
> >* It's important to note that the logs were not just found in the USBs
>> John *>* Young/Cryptome sent to me, but in the ones sent to "bandmon",
>> who unless *>* I'm mistaken is coderman@xxxxxxxxx <coderman@xxxxxxxxx> *
>> i'm not sure who bandmon is, but they're not coderman@xxxxxxxxx. i
>> would however be amenable to uploading a list of sha-256 digests to
>> verify components of similarity between the torrent and origin. >*
>> https://thepiratebay.mn/torrent/11113511/Cryptome_archive_2014-06-02
>> <https://thepiratebay.mn/torrent/11113511/Cryptome_archive_2014-06-02> *
>> >* It was my strong preference **not** to post this, but since Cryptome
>> has *>* refused to validate the data, there is no other way to
>> authenticate it than *>* to release it to the public along with how to
>> find that information in the *>* Cryptome USBs/CDs and their various
>> mirrors. * actually one may cross reference with their own requests and
>> circuits,
>> for high confidence of legitimacy. i find it apropos to now quote the
>> original disclaimer in full:
>> '''
>> This is a trap, witting and unwitting.
>> Do not use it or use at own risk.
>> Source and this host is out to pwon and phuck you in complicity
>> with global Internet authorities.
>> ...
>> Signed Batshit Cryptome and Host, 9 July 2014, 12:16ET."
>> - cypherpunks/2014-July/005020.html, and true for FY-2014, too.
>> ''' best regards,
>
>
>



Other related posts: