>>131
Sigh, Example 93:
Act I: The malware had been planted
JS file says to client:
"Give me all the info and settings I can get from my client/browser, make a user and session ID as a handle, with a time stamp I believe is true, and start making a timer. I shall call myself:
User-IDx:Checksum-hashX:Time-X:Duration-X:Session-ID
If I find cookies and other shit in the cache that I can get my hands on, compress them if I can, and make the metadata message. If can't read anything, prepare a message with my
User-IDx:Checksum-hashX:nothing-read. Message-x:Metadata-x:Metadata-HashX
complete, time to talk to a API on a DoD server."
JS client:
"Sending compressed what I could, and made packets sizable to send anywhere. If I can do multicast or anycast, awesome. Let me break my packets with my handle ID and my handle for the metadata and pass it around."
ProdServer1:
"Thank you for the packet exploit JS, User-IDx. It took you this amount of time(Duration-Y) to contact us since we sent this, and you say your timestamp is UTC-X, when our time is UTC-Y (Time-Y).
Here is our Session-IDxyhash and your new Temporary User-IDXYhash. Lets do some test with each other about our times to see if we have a reliable communication."
JS client: "Ok. I got all you messages, and your hashes matched. What would you lime me to do?"
ProdServer1:
"Please go to the Prodservers G, H, and J at your convenience (care not to overload your client and randomly stop at intervals) and tell them the same thing you told me, and your Temporary User-IDXY and Session-IDxyhash, and wait further instructions from the first one that tells you:
Communication-session_prod1_list_of_GUID_xy:Metadata-prod1_list_of_GUID_xy:Hash_message-
_prod1_list_of_GUID_xy:Time-UTC_master_prod1_list_of_GUID_xy_as_hash:Duration-GUID_xy
"
Act II: The NSA exploit network
ProdServer1 to MasterServers:
"I told User-IDx:Checksum-hashX:Time-X:Duration-X:Session-ID
to call servers G, H, and J with Temporary User-IDXY and Session-IDxyhash and
Communication-session_prod1_list_of_GUID_xy:Metadata-prod1_list_of_GUID_xy:Hash_message-prod1_list_of_GUID_xy:Time-UTC_master_prod1_list_of_GUID_xy_as_hash:Duration-GUID_xy.
Our session should be called
case-GUID_xy:session-GUID_xy:Mesh-xy:Time-GUID_xy:Duration-GUID_xy.Awaiting orders."
MasterServer U:
"I have that one already. Make it
GUID_xy2:session-GUID_xy2:Mesh-xy2:Time-GUID_xy2:Duration-GUID_xy2
And wait further instructions on."
ProdServer1:
"Copy that."
Anycast receiver server D to Server network:
"User-IDx:checksum-hashX:Time-X:Duration-X
shouted and said: 'Message-x:Metadata-x:Metadata-HashX'. No further actions done, would you like me to do some?"
ProdServer1:
"I got him as well. No need to do any further at the moment I told MasterServer U and gave me
GUID_xy2:session-GUID_xy2:Mesh-xy2:Time-GUID_xy2:Duration-GUID_xy2
He will contact servers G, H, and J, and we will inform you if we need you. Here is our session ID and checksum."
MasterServerU:
"Anycast receiver server D, no need to do anything further. The case is:
GUID_xy2:session-GUID_xy2:Mesh-xy2:Time-GUID_xy2:Duration-GUID_xy2
ProdServer1 got him perfectly. Did he talk to you?"
Anycast receiver server D:
"Yes, and here is our conversation: session-ID:checksum. Here is our session-ID:checksum"
MasterServerU:
"ProdServer1, Anycast receiver server D got your message an told me. Is that coorect?"
ProdServer1:
"Correct. Any new orders?"
MasterServerU:
"Thank you. I will pass this allong the network"
*MasterServerU responds to network, server G says its busy, and H do not respond. *
*MasterServerU informs everyone else about Servers G and H failings, and tells sys admins*
Act III: The communication
JS Client:
"Still looking at what I have, and compressing what I can with my limited knowledge. In case we find a duplicate like me, let me call myself
User-IDx2:Checksum-hashX2:Time-X:Duration-X2:Session-ID2
and append that I met Session-IDxyhash and was given Temporary User-IDXYhash just in case I fail talking to Servers G, H, and J. How here is server G"
Server G:
"Thank you for your message. But we are busy. Go to the Next server on your list"
JS client: "Ok, appending my new message to server H that Server G was busy and told me to go on my list."
* Server H never responces *
JS client: "Server H took too long to responded. Ok, appending my new message to server H took too long to responce. Going to server J."
Server J: "Oh thank you. I was waiting for you. That information you are giving me checks out. Your new handle is this:
GUID_xy2:session-GUID_xy2:Mesh-xy2:Time-GUID_xy2:Duration-GUID_xy2.
There are issue with Server G and H at the moment. Here is our session ID. Now go to reliable servers R, T, F, M, K, I, S, and § (which are geo-location timed, well informed of this case, and have access to your assumed Local ISP) and update them with you new case number and our summarized messages."
* JS client goes along and talks to various distributed networks and identify the local ISP that JS client has been talking wo the servers with the presumed times*
* The Prod and Analysis server update the information to the Master Serves, which in turn compare the case to others with all the new information gathered and stored in B trees. If they find a match from a previous client/ISP user, then wind down and inform the JSclient. If not, the a DoD agent office needs to investigate the area and tap the local network from the ISP. The dumb user is raided when enough evidence is acquired to convict with something, even lame copyright infringement *
Act Epilogue:
* Everyone lives happily ever after *
* The DoD got commition for another arrest in his quota. *
* The Stupid user gets affordable hospitality for years to come, and re educated that he is chattel. Hopefully gets to become the prison bitch, and gain fame and acceptance. *
* The artist that provided the data get no recompense, and probable jail time too. Sucks to be the providers, if you do not work for the Multinational banks. *
* Multinational banks win,
win,
WIN! *