-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathCONCEPT
163 lines (107 loc) · 8.46 KB
/
CONCEPT
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
Michael Guidry
April 8, 2017
Building a system to force distrust of worldwide mass surveillance, or ISP web history platforms
I will outline some ideas which can be crowdsourced, or funded that would cause critical damage to mass surveillance programs worldwide. It doesn’t matter whether it is government sponsored, or Internet Service Provider (ISP) platforms. The end result is overall privacy for every citizen using the Internet. It seems that rights to privacy has taken a turn with the recent repeal by President Donald Trump regarding the Federal Communications Commission (FCC) regulations which ensured our privacy.
The overall concept behind destroying these programs is to cause so many false positives, or fake information where it will take more resources to distinguish the difference than it would the information value, or sale of the data. If this distrust generating platform is created once then it should work for the entire lifetime of the Internet regardless of where these privacy invasive platforms exist.
#1 create network for replaying connection worldwide to inject into mass surveillance databases
need two types of nodes
‘webserver’ or ‘server’
and ‘client’ or ‘spoofed client’
it should be a p2p, or multi-hub linked network with ability to distribute packets to nodes which are needed…
structures of instructions
int tcp_connection_side; // server or client
struct _pkts {
// is this server or client
int connection_side;
// pointer to data
char *data;
// length of data
int len;
// the packet id
int id;
// id of the packet which initiates the replaying of this packet
int activate_id;
int source_port;
int dest_port;
char *source_ip;
char *dest_ip;
} *packets;
// how many packets exists
int packet_count;
// how many total bytes in the packets
int packet_length_total;
it should allow both server and client to communicate to each other, or the network as whole
this will allow them to automatically message whenever they are done replaying a message to their internet connection
which can trigger the other side to replay the next packet…
it will work perfectly just like any other regular tcp/ip connection by the operating system
iptables* can be setup to automatically block the operating systems from sending ICMP information about ports not available
#2 require module for each web site (social media, ie facebook, etc) for generating the types of messages, such as.. WebSockets, messages, email, etc
the modules are used to build the packets from either MACRO-fied tcpdump of other connections, or similar
it needs to be able to handle tcp/ip checksumming and be able to build packets on the fly
sometimes it might not be smart to use complete packets from tcp dumps.. just building tcp/ip packets and then handling the rest as ‘connection sides’ with their activation ids might work out well enough
—-
#3 grab lists of wanted people, and top names that are investigated worldwide..
#4 have various citizens worldwide information for use.. such as e-mails, passwords, etc… possibly using leaked information, and stolen email addresses as well
——
#3 can generate mass “web traffic” which is to screw up ISP history sales, and is alternative to first #3
#4 use various logins, etc..or directives for creating false web traffic which would seem like inflated log files thus ISP selling the information would lose any secondary purchase of logs again
——-
#5 determine algorithms on how often to use, and ip addresse, etc to use within these messages… it should relate to targets, or smear campaigns
——
right here is a good time to make the program public, and allow crowdsourcing for people who have issues with todays privacy restrictions.. a group can come together and determine assets, and amount of time required to destroy these programs.. or create enough distrust to where they are not a viable option anymore
—-
#6 analysis of BGP routes, and possibly nodes at ISPs which are more than likely monitored
telecommunication routes, etc should be analyzed to attempt to get boxes within those networks
it is critical because it plays a role in having both sides on the surveillance tap
they cover so many IP ranges that it is really impossible for the major taps to mitigate this
this is only used to determine whether a surveillance tap is justifiable going to analyze the packets as they are replayed..
if you consider how far ranging GCHQ taps are.. it's not an issue there..
and generally this might not even need to be developed in the first few versions of the application
#7 use analysis of surveillance nodes to then buy dedicated machines, or access to machines which can be used as one side of the injection
this is no longer an issue for a few versions either.. its generally a part of #6
#8 execute, and setup timeframe … possibly using AI/neural networks, or other systems of chat logs to begin to inject messages… possibly having real human assets develop information for distribution
this isn't a problem as long as the nodes connect to each other, or use a hub
a hub with an entire network of servers, and clients allows them to automatically distribute new tasks to each other from some group of servers who are coordinating the attacks
#8 cyber sensors
need voip phone numbers
dns
Whois servers (registrar)
web servers
etc… everything required to find ‘cyber investigative connections’ regarding the campaigns being launched
#9 physical sensors
need to choose correct identities, email addresses, wording, etc
Web cameras in city that are available should be chosen, and monitored for a few days to train neural networks
so once injected into particular campaigns the surveillance, or police arriving for questing or other factors is easily caught automatically so the results can be applied into a database for processing
timing is of importance, especially paired with multiple keywords, and #8
EarthCam - Webcam Network
https://www.earthcam.com/
EarthCam is the leading network of live webcams and offers the most comprehensive search engine of internet cameras from around the world. EarthCam also creates and produces live ... Big Apple Cam. Big Apple Cam. New York City, NY.
SkylineWebcams | Live Cams around the World!
https://www.skylinewebcams.com/en.html
SkylineWebcams - Live Cam in the most beautiful tourist attractions of the world! ... Webcam Madrid - Puerta del Sol Madrid - Puerta del ... Explore the Webcams.
Ok an example of generating a 'sensor' to be used in a mass survellance injection campaign:
1) I used one of the webcam network sites above to find this site. I picked a random camera on here, and ensured a house
was within the cameras view. You can view this all day long as a 'traffic camera' but if you choose a window around the house,
then you can process that into a neural network. You can use activity over a few days to create a 'normal' category..
Anything else that changes within this picture should be detected as anominally. This means that you can use
many random web cams, traffic cameras, or other resources online which have plain view of homes, business, etc.
http://vancouver.ca/streets-transportation/traffic-cameras.aspx - Intersection:Clark Dr & E 12th Av
2) I found this address on google maps by using the intersection. I found the Super Save Gas Station afterwards..
https://www.google.com/maps/@49.2596846,-123.0771283,3a,75y,357.59h,91.59t/data=!3m6!1e1!3m4!1slSs21-81uJB-hKlWxF3MRw!2e0!7i13312!8i6656!6m1!1e1
Gas Station in view:
Super Save
1317 E 12th Ave
Clark Dr
Vancouver, BC V5N 2A1
Phone: 604-875-6481
The house next to the gas station:
1329 E 12th Ave
Vancouver, BC V5N 2A1
If you use this image to create a window (pixel window) then you can export only those select pixels to go into your
neural network to categorize whether it is normal for that address, or an anominally.. The anominally may be police
showing up, different cars in drive way, etc... It depends on your neural network
It may be possible to have a neural network of various surveillance being done and then you could just use that on
every camera without initially monitoring it for awhile. This would allow you to detect police uniforms, and other factors.
Afterwords you would find the name of individuals working, or living at the addresses you choose. You can then begin to
pair them with keywords in mass surveillance campaigns that relate to current activities, wanted associates, crimes, etc..
It is up to you to figure out that side of things.. I'm just giving a generalization of how its possible.