i’ve been working at the glass room as an “inGenious” and taught an hour-long workshop there on saturday about how the web works. everyone who does a workshop has been sending feedback to everyone else so we can all be more prepared next time we teach. here’s what i said about mine:
hey! here’s feedback from the workshop i did saturday at 3pm:
there were a whole bunch of people (30-40?), so we couldn’t go around and do names/intros. but we did write our names on tape as name tags, which i found helpful and i hope they did too since they had to do an activity together.
i started with an intro and then asked what folks were interested in. the responses were generally either ‘knowing more about infrastructure’ or ‘knowing specific things to do to protect my privacy’
then, i handed out the internet infrastructure cards- about one set per 6-7 people, which i think worked okay. the groups finished laying everything out very quickly, like less than 10 minutes. i asked groups to share out how this activity went for them and there were a few sentiments:
– ‘i thought i knew how this worked, but when i had to lay everything out, i realized there were some gaps in my knowledge’
– ‘what’s a national gateway?’
– ‘why are there two computers?’
in general, i think the cards were really helpful for people. on reflection, and after reading the feedback forms, i think i should have spent more time going over each element in the set of cards instead of only having groups explain their own layouts. i think i also should have done a better job explaining why there are multiple right answers and your configuration could have routers, servers, etc in a different place than other groups.
people were *really* into the submarine cable map!
i used that + infrastructure cards to say that the internet is physical and that there are different places along the line where info can be intercepted. then, i went into vpn vs. tor vs. https. i explained a little bit of the technical stuff and tried to just reiterate over and over again that people should def get ‘https everywhere’ (free!) and try a 2-week free trial of cloak vpn. people had fairly technical questions about vpn’s- how do they work? do i need one at home? does it encrypt everything? etc., so i’d be ready for that (many thx to sara for helping me navigate those!)
there were 2 kinda derailer/mansplainy guys. a way i tried to address them was listen for a little bit, nod my head, and then try to tie something they said back to something someone said earlier or a question someone else asked. then, i could shift the mic to the new person and we could eventually get back on track.
so yeah! it was fun! if you’re teaching this one and have q’s about any of this, let me know!
is the project i’ve been working on with surya. it’s a website that hosts a video and tool that lets users dig into network packets. we’re getting into crunch time, so i’ve started filing issues in the repo to help me keep track of stuff i need to do/write. surya made a little annotated map of the app structure to help me wrap my head around everything:
├── app <- contains all the src for the front end
│ ├── App.vue <-The main ‘app page’. Contains the Toolbar and Console components. Will also contain the viz stuff when i get to t.
│ ├── Stack.vue <- old stuff that ive just left here for ref. right now
│ ├── components <-All the components of the app
│ │ ├── Console.vue <- all css in _console.scss
│ │ ├── Sniffer.vue <- all css in _sniffer.scss
│ │ ├── Stack.vue <- old stuff that ive just left here for ref. right now
│ │ ├── ToolBar.vue <- all css in _nav.scss (meant to rename it but forgot!)
│ │ ├── third-party <- testing some libs not used yet
│ │ │ └── vue-drag-resize-rotate.vue
│ │ └── tools <- testing some stuff not used yet
│ ├── filters <- vue.js helper functions for formatting text
│ │ └── index.js
│ ├── main.js <-First thing to get loaded. This loads App.vue and has socket.io connections to the back end
repo for a silly iot group project that will read in an employee’s heart rate and use text-to-speech to read the communist manifesto back to the employee, with speed of speech correlated to heart rate. very much a WIP.
i’ve been testing the idea i described in my last post. in the vid below, i use james woolley’s python script to flood the ball drop game with syn packets. i execute the script to send 2000 packets consecutively to the ip and port that the server is listening on. while that’s going, i connect to the game with the ball drop client. the client seems to connect with no delay which is unfortunate since i want a delay. i’m not sure whether i’ve set something up wrong or whether 2000 packets just isn’t that many.
well, here we are, a thousand rabbit holes later. when i tried executing the syn flood script with 20,000 packets and the connection didn’t change, i decided i was doing something wrong. i looked into a few other kinds of attacks, but ultimately came back to this one. below are some characteristic screen shots of my wireshark readings.
in the first one, you see a SYN from assigned port to port 8080, SYN/ACK from 8080 to me, and RST from me to 8080. RST means to close the connection because something’s gone wrong, and the client started by the python script kept sending them out when the connections were (predictably) broken. sometimes, a message from the actual ball drop client would get through in the middle of all this SYN/ACK/RSTing, which suggested to me that maybe there was something multi-threaded about the connection? and if there are multiple threads, how do you know how many there are and what their capacities are? and how do you block them all? 😱
here’s another thing that happened: a bunch of SYN packets, with no RST packets (great!) with ball drop client messages in between (not great!). the ball drop client messages here are the two not-gray ones in the middle. the arrow is pointing to the payload, which is “L” for directing the paddle to go left.
so, like, wtf? i went back to where i’d originally gotten the syn flood python script. i realized that i’d totally skipped the first script, which blocks RST packets from being sent out. alas, the utility it relies on, iptables, is for linux and isn’t a thing on mac os x. i went hunting for alternatives and learned about pf.conf and tried to implement a block on RST flags using this solution. double alas. i could edit pf.conf, but couldn’t load the new file to be executed.
our last assignment was to “design a device that can connect to a server using a TCP socket connection to play a game.”
the game? “This is a multiplayer game in which players collaborate to keep a ball from hitting the ground. Each player has a paddle, and can bound the ball off her paddle. When the ball bounces off your paddle, you get a point. Only the first bounce counts, though; subsequent bounces don’t get you points. But if the ball bounces off another player’s paddle then back to yours, you score again. You can keep scoring forever by bouncing the ball back and forth.” you can learn more about it here.
in thinking about how to get the highest score, it’s helpful to have the server code available because it lets me know how the game works. tom gave us some examples of sanctioned ways to play: how to hook up a joystick or an arduino or whatever. but he also mentioned surya, allison burtch, and jon wasserman’s packet injection hack. i’m more interested in a hack than in making a controller, so i’ve been thinking about different options.
i think this part of the server code presents an interesting opportunity:
Get the paddle position of the last player on the list.
If it's on top, add the new player on the bottom, and vice versa.
If there are no other players, add the new player on the top.
// get the size of the list:
// if there are any other players:
// increment the position and add the next player:
// if there are no players, add to the top:
i imagined it would be possible for starting positions to look like this, in which case we would get a point for every new paddle the ball hit on the way down to the bottom:
i tested this by running the server on my computer and logging in from the game client and my phone:
this confirms to me that it’s possible to get a cascade thing happening if all clients log into the game in quick succession. so now i’m thinking about how to fill up the server’s buffer and only accept connections under certain conditions, like that there are 10 clients lined up to log into the game. i’m just starting to play with scapy, so we’ll see if i can execute this in time for tuesday.
there’s something called a SYN flooding attack that might work for filling up the buffer. and i found a script by james woolley that works with scapy to do it. the problem is that i’m not sure how to control the length of time the buffer stays full. i don’t want to totally break the server; i just want to block connections for a certain amount of time. i hope i don’t have to do resort to doing math 😱
wireshark and debookee already exist, so what’s the problem we’re trying to solve with this tool?
ours isn’t designed for engineers or netsec people. we think everyone should know how networks work, and we’re designing the experience and interface around this tool to be engaging and legible to people outside of tech bubbles. tl;dr: we’re creating a different context around the information in yr packets.
the tool is interesting and useful on its own, but we’re also eventually releasing it with short episodes that break down recent headlines about hacking (“iot botnet attack!”) so normal humans can understand them.
i mentioned many posts ago that i’m working with surya mattu on *stuff* about networks. what started out as *stuff* has narrowed in focus and we’ve started building. we have an ugly prototype of a web-based packet-sniffing tool that lets users on the same network explore how their computers are talking to each other. this has gone through many iterations, mostly riffing on the wireshark interface:
we’ve settled on a combination of these two, with a toggle that lets you switch between a visual view and hex view. i’ll post screen shots once that’s all built out.
version 5 above has an actual back end, which surya built and which lives here: https://github.com/samatt/it-packet-interactive
what’s happening here? this is an express server application that uses a node library called node pcap to capture network packets. right now, the server listens for packets on port 3000, parses them, and saves them out to a json file called test.json. separately, the express server serves a static file called packet.json so if you visit http://localhost:3000/data/packet.json you’ll see the json file that is used to create the front end visualization in the screen shot above. eventually, we want the server to serve up the packets it sniffs and saves, but for now we’re simulating that situation.
the front end, which lives here: https://github.com/samatt/packet-interactive-fe, is built with webpack, socket.io, and vue.js. the back listens to packets traveling over the network, saves and parses them into a json file, then serves that json file to the front via socket over port 7777.
part one: i was originally interested in the overlap i see between open source software projects and grassroots organizing. this now only seems like half of what i’m interested in. we don’t organize just for the hell of it, just like we don’t “build community” for the hell of it. organizing builds collective power. collective power is important to the extent that it results in material improvements to people’s lives. i’m curious about the extent to which the scalability and accessibility of a distributed open source model can be used to expand the reach of and participation in IRL social movements.
part two: everyone’s talking about digital literacy. but to what end? i’m interested in a digital literacy that empowers people as civic participants. i’m interested in a digital literacy that helps activists build tools to leverage power as workers and users of digital platforms. currently, these platforms benefit from intentional information asymmetries, but the reality is that they would not exist without us. how do we leverage this to demand accountability, fair wages, transparency? this looks different in different kinds of cases. in particular, i’m interested in two kinds of recent cases:
facebook collaboration with police to censor police killing of korryn gaines.
these are technical design challenges. maybe they look like apps or browser extensions or encrypted email lists or a combination of all the above or something else entirely.
so that’s it. those are the things. going forward, i need to work on elaborating what i see as the lay of the land, the problems, and the opportunities here. aside from that, there are some prototypes to be very sketchily sketched and design challenges to think through. everyone’s talking about algorithmic accountability lalala, but what if we never get access to proprietary algorithms? what if, instead, we hack our way around them the way instacart workers did? i’m interested in a digital literacy, a kind of thinking aided by a technical skill set, that makes this possible on a larger scale.
the overlap between grassroots organizing spaces and open source software
infrastructure for communities of contributors that enables them continue to grow and learn and build together
how to mitigate burnout & other problems
so. ramblings below.
“some things the open product dev piece brought up for me:
– it seems like your “generating and discussing…” section assumes that the test pilot community contains/is made up of people with skill sets that mirror staff mozilla product teams: roughly, ux/ur & dev. so my first question is: is that true? if not, an issue becomes how to improve the pipeline to the test pilot community so that it becomes true. another issue is what if the ratios are off? more ux than devs or vice versa? how can people plug in with different skill sets? or is the test pilot target audience people who can either do user research or dev?
– another thing i’ve seen play out in activist organizing spaces, which actually feel structurally similar to what i’ve seen in open source in some ways, is that people tend to fall into roles. one person always does logistics, one person always writes press releases, the rest of the people always wait to be assigned something, etc. in open source, i wonder if this would play out like: a few people always come up with new product ideas, a few other people always do research stuff, etc. how do you feel about this? should there be an effort for people to try out other roles and build other skill sets? i think there are pros and cons to trying new roles AND really building ONE skill set, so i’m just putting out the question. related: seems like another thing i’m getting at is a power law distribution of labor and credit for contributions. is that sustainable/how will that play out over time? will it lead to burnout in open source in the way it often leads to burnout in activist spaces? if so, is it important to mitigate in some way?
– one last thing! i am not really familiar with different ways mozilla volunteers plug in or how they build community, so take this next part with that grain of salt. in my experience building community IRL, it seems that different kinds of gathering/communicating structures bring different kinds of people together. so i guess i wonder whether discourse forums/forums in general being the primary mode of collaboration means that certain kinds of people will be drawn to or put off by participating? i think you, john, and/or wil actually already brought this up. maybe marketing can help with pitching the collaboration in different ways to different audiences and providing additional/alternative ways to plug in. for example, maybe IRL test pilot hackathons could be a way of reaching folks and bringing people together in a way that the forum wouldn’t.”