My local cafe is serviced by a rickety and unreliable wireless network, generously sponsored with ratepayers' money by our city council. After connecting, you are redirected to an SSL-protected page that prompts you for a username and password. Once you've entered your details, you are free to enjoy the intermittent dropouts, treacle-like speeds and incorrectly configured transparent proxy. I tend to automate this kind of thing at the first opportunity, on the theory that time spent now will be more than made up in the long run. In this case, I might use [Firebug](http://getfirebug.com/) to ferret out the form post parameters and target URL, then fire up an editor to write a little script using Python's [urllib](http://docs.python.org/library/urllib.html) to simulate a submission. That's a lot of futzing about. With mitmproxy we can do the job in literally 30 seconds, without having to worry about any of the details. Here's how. ## 1. Run mitmdump to record our HTTP conversation to a file. 
> mitmdump -w wireless-login
## 2. Point your browser at the mitmdump instance. I use a tiny Firefox addon called [Toggle Proxy](https://addons.mozilla.org/en-us/firefox/addon/toggle-proxy-51740/) to switch quickly to and from mitmproxy. I'm assuming you've already [configured your browser with mitmproxy's SSL certificate authority](http://mitmproxy.org/doc/ssl.html). ## 3. Log in as usual. And that's it! You now have a serialized version of the login process in the file wireless-login, and you can replay it at any time like this: 
> mitmdump -c wireless-login
## Embellishments We're really done at this point, but there are a couple of embellishments we could make if we wanted. I use [wicd](http://wicd.sourceforge.net/) to automatically join wireless networks I frequent, and it lets me specify a command to run after connecting. I used the client replay command above and voila! - totally hands-free wireless network startup. We might also want to prune requests that download CSS, JS, images and so forth. These add only a few moments to the time it takes to replay, but they're not really needed and I somehow feel compelled to trim them anyway. So, we fire up the mitmproxy console tool on our serialized conversation, like so: 
> mitmproxy -r wireless-login
We can now go through and manually delete (using the __d__ keyboard shortcut) everything we want to trim. When we're done, we use __w__ to save the conversation back to the file. log/target/sdk/Makefile'>
path: root/target/sdk/Makefile
blob: 6d818347204a3cce0aecaa5fda55ac0f97b83cc9 (plain) 
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
163
164
165
166
167
168