Guest User

TWITTER @LZR9 Legal Process RESPONSE to ATTORNEY GENERAL

a guest
May 3rd, 2013
1,573
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. This collection of text includes the response by TWITTER LEGAL to a subpoena from Attorney General
  2.  
  3. (see also):
  4. ~╔͎═͓═͙╗ 💬  #Subpoenas
  5. ~╚̨̈́═̈́═̨̈́﴾ ̥̂˖̫˖̥  ̂ )  http://cdn.anonfiles.com/1366854274297.pdf …
  6. ~╔͎═͓═͙╗ 💬  http://pastebin.com/MfJ9Dzqs
  7. ~╚̨̈́═̨̈́﴾ ̥̂˖̫˖̥  ̂ )  @lzr9
  8.  
  9. Included here are 3 sets of information, the first two, are the TXT files provided by Twitter to the State of Hawaii Attorney General on April 30, 2013CE, I have purged some specific information while a legal contractor further investigates, one of these is the "ACCOUNT CREATION" record, the next is the set of "logins" between 3/24 and 4/24, when they isolated the data to generate the report. Notable in this, is that 20% of the "logins" are NOT related to communications from @LZR9's ship, which uses a TOR PROJECT relay bonding multiple satellite and unconventional communication modes, where the TOR exit node is apparently behind a cluster of PEPLINK load balancing devices, listed below in the sample set. Both text files are wrapped with PGP checksum, however this does NOT correlate with session starts, has no associated information (internal IP, MAC, etc), and has a notable inclusion of multiple "login" events that are not likely associated to the communications from SS Independence and are now under investigation by numerous international authorities.
  10.  
  11. Specific Questions to LZR9@INTERPOL.IT or via twitter @lzr9.
  12. Additional mirrors can be found with web search, or via Cryptome.org for review.
  13.  
  14. ---------------------------------------------------
  15. ACCOUNT CREATION RECORDS:
  16.  
  17. The IP resolves to: [XXX]
  18.  
  19. *.*!*.mrt.starband.net 148.63.128.0/18
  20. starband_mrt_vsat
  21. AS16811
  22. ---------------------------------------------------
  23.  
  24.  
  25. -----BEGIN PGP SIGNED MESSAGE-----
  26. Hash: SHA1
  27.  
  28. id: 520827325
  29. created_at: 2012-03-10 23:31:05 +0000
  30. updated_at: 2013-03-13 23:52:33 +0000
  31. email: lzr9@interpol.it
  32. created_via: web
  33. screen_name: lzr9
  34. creation_ip: 148.63.XXX.XXX
  35. time_zone:
  36. ********************
  37. -----BEGIN PGP SIGNATURE-----
  38. Version: GnuPG v1.4.5 (GNU/Linux)
  39.  
  40. iD8DBQFReHfDWJwPIge+SvERAgXXAJ9GIf5wjBNdLm1CHB8agFlzH+h3gQCeOnkV
  41. eCVUhi1PtNNKjG63o/ZyBH0=
  42. =eFY/
  43. -----END PGP SIGNATURE-----
  44.  
  45. ---------------------------------------------------
  46. LOGIN RECORDS:
  47.  
  48. The login records are inconsistent, but here is a sample set clipped from around the target date among the 75 records listed in .txt from TWITTER LEGAL:
  49.  
  50. (Notice the UTC centered session reset, clusters of Peplink http://www.peplink.com/balance/tech-spec/ , and two additional IPs which I have removed from the list for investigation. Automated reports from the communication infrastructure indicate the TOR box is among thousands of clients behind a cluster of at least a dozen of these Peplink devices.)
  51. ---------------------------------------------------
  52.  
  53. -----BEGIN PGP SIGNED MESSAGE-----
  54. Hash: SHA1
  55.  
  56. ********************
  57. user_id: 520827325
  58. created_at: 2013-04-22 00:18:16 +0000
  59. last_login_ip: 24.43.201.210
  60. ********************
  61. user_id: 520827325
  62. created_at: 2013-04-21 23:58:23 +0000
  63. last_login_ip: 24.43.201.210
  64. ********************
  65. user_id: 520827325
  66. created_at: 2013-04-20 23:52:57 +0000
  67. last_login_ip: 24.43.201.210
  68. ********************
  69. user_id: 520827325
  70. created_at: 2013-04-19 23:46:20 +0000
  71. last_login_ip: 24.43.201.210
  72. ********************
  73. user_id: 520827325
  74. created_at: 2013-04-18 23:56:20 +0000
  75. last_login_ip: 24.43.201.210
  76. ********************
  77. -----BEGIN PGP SIGNATURE-----
  78. Version: GnuPG v1.4.5 (GNU/Linux)
  79.  
  80. iD8DBQFReHfDWJwPIge+SvERAqVwAJ9SWcT7pgB6SrqjrKs3EblhWBWARQCguXIG
  81. mRWuqW1dcv2ooLPQzj3QnCU=
  82. =rpH9
  83. -----END PGP SIGNATURE-----
  84.  
  85.  
  86.  
  87. ---------------------------------------------------
  88. Email Log:
  89.  
  90. The first email, at the bottom, from Twitter-Legal, included the automatic fax-to-PDF of the Attorney General Request. http://cdn.anonfiles.com/1366854274297.pdf
  91. ---------------------------------------------------
  92.  
  93. Twitter:
  94.  
  95. Again, this is one of many recipients of the emails you send to a distributed email list, we appreciate your response and I will attempt to forward this information to the ship. We must express concern that the request was namely for April 21st, yet you provided a month of "login" information which may not have been appropriate, and more importantly that 20% of the "login" sources are NOT from the primary party using the TOR node apparently connected to the Peplink clusters. Please help us isolate these additional logins as they are NOT in the wire transit log from their ship. Respond only to lzr9@interpol.it please.
  96.  
  97.  
  98.  
  99.  
  100.  
  101. On Fri, May 3, 2013 at 2:34 PM, Twitter Legal <twitter-legal@twitter.com> wrote:
  102. Dear Twitter User:
  103.  
  104. Per your request, we are providing a copy of the records we disclosed regarding your Twitter account @lzr9. Included in the attached files:
  105.  
  106. -[USER]-account.txt: Basic subscriber information, including: screen name, email address (as given by Subject User), and account creation date.
  107. -[USER]-ipaudit.txt: Logins and related IP addresses.
  108.  
  109. All our records are maintained in UTC, which is the same as GMT for time zone purposes. Any fields that are blank or any files that have no content between the PGP header and signature block indicate that there are no responsive records.
  110.  
  111. Sincerely,
  112.  
  113. Twitter Legal
  114. Legal Policy | Twitter, Inc.
  115.  
  116.  
  117. On Wed, May 1, 2013 at 9:48 AM, wrote:
  118. Please send @lzr9 a copy of the filings you delivered to the State of Hawaii Attorney General and any related information.
  119.  
  120.  
  121. On Tue, Apr 30, 2013 at 6:57 AM, Twitter Legal <twitter-legal@twitter.com> wrote:
  122. Dear Twitter User:
  123.  
  124. Thank you for your email. As previously communicated, we were notifying you of this information request per our Privacy Policy. We have not yet disclosed any information regarding your account, however, Twitter is obligated to respond to lawful process and will do so absent the filing of a motion to quash.
  125.  
  126. We cannot provide any legal advice.
  127. If you think you have been contacted in error, you may wish to contact an attorney.
  128.  
  129. If you need assistance seeking counsel in the United States, you may consider contacting the Electronic Frontier Foundation (https://www.eff.org/pages/legal-assistance, info@eff.org, +1 415-436-9333) or the ACLU (http://www.aclu.org/affiliates, +1 212-549-2500).
  130.  
  131. Sincerely,
  132.  
  133. Twitter Legal
  134.  
  135.  
  136. On Wed, Apr 24, 2013 at 6:50 PM, wrote:
  137. This email, unrelated, finds it relevant to notify you that the "account name" on @lulzer is █▃ █▃█ █▃▀█▃ █▒▒ █▀▙ ‏, and the "account name" of @lzr9 is "lulzer آلجور ‏" which is not correctly documented in that invalid fax. To our knowledge, @lzr9 and @lulzer are unrelated entities. Explain your error, I will try to pass the issue on?
  138.  
  139.  
  140.  
  141. On Wed, Apr 24, 2013 at 2:25 PM, Twitter Legal <twitter-legal@twitter.com> wrote:
  142. Dear Twitter User:
  143.  
  144. We are writing to inform you that Twitter has received the attached legal process, dated April 23, 2013, regarding your Twitter account, @lzr9. This legal process obligates Twitter to produce information related to your account.
  145.  
  146. One of our core values is to defend and respect the user's voice. Accordingly, it is our policy to notify users of requests for their account information prior to disclosure unless we're prohibited from doing so by law. We are notifying you of this legal process in order to allow you to decide whether or not you will oppose the production of the requested information, either by filing a motion with the court where the legal process was issued or contacting the requesting party directly.
  147.  
  148. Please be advised that Twitter is required to respond to this request by May 1, 2013. If we do not receive notice from you that a motion to quash the legal process will or has been filed, or that this matter has been otherwise resolved, we may produce some or all of the requested information. Please let us know as soon as possible if you intend to file a motion with the court, and send us a copy of what has been filed. If you have resolved the matter with the requesting party, please have them send us confirmation that the legal process is withdrawn.
  149.  
  150. We cannot give you any legal advice, but suggest that you may wish to seek your own legal counsel in this matter. If you need assistance seeking counsel in the United States, you may consider contacting the Electronic Frontier Foundation (https://www.eff.org/pages/legal-assistance, info@eff.org, +1 415-436-9333) or the ACLU (http://www.aclu.org/affiliates, +1 212-549-2500).
  151.  
  152. To respond to this notice, please reply directly to this email or email us at twitter-legal@twitter.com.
  153.  
  154. Sincerely,
  155.  
  156. Twitter Legal
RAW Paste Data