WEBVTT

1
00:00:00.080 --> 00:00:02.439
<v Speaker 1>Welcome to the deep dive. We're here to plunge headfirst

2
00:00:02.520 --> 00:00:05.639
<v Speaker 1>into complex topics, really pull out the most important insights,

3
00:00:05.639 --> 00:00:08.519
<v Speaker 1>maybe some surprising facts for you. And look, it's no

4
00:00:08.599 --> 00:00:11.880
<v Speaker 1>secret that real Internet privacy, well it's incredibly difficult these days,

5
00:00:11.919 --> 00:00:15.199
<v Speaker 1>really tough to maintain. If you're online, your data, your habits,

6
00:00:15.240 --> 00:00:17.679
<v Speaker 1>even where you are, it can all become a fair

7
00:00:17.719 --> 00:00:21.519
<v Speaker 1>game tracked by well everyone from governments to hackers. It's

8
00:00:21.640 --> 00:00:25.399
<v Speaker 1>just the reality. So today we're doing a deep dive

9
00:00:25.480 --> 00:00:29.199
<v Speaker 1>into some serious methods ways to try and maintain anonymity

10
00:00:29.239 --> 00:00:33.079
<v Speaker 1>and evade surveillance. Our main source for this is a

11
00:00:33.119 --> 00:00:36.039
<v Speaker 1>really detailed book tour and the Darknet Remain Anonymous and

12
00:00:36.119 --> 00:00:39.719
<v Speaker 1>Evade NSSAY Spying by James Smith. Our mission here is

13
00:00:39.719 --> 00:00:41.759
<v Speaker 1>to dig through this find those crucial bits of knowledge,

14
00:00:41.799 --> 00:00:44.399
<v Speaker 1>those surprising facts, to help you get truly well informed

15
00:00:44.439 --> 00:00:45.399
<v Speaker 1>on digital security.

16
00:00:45.479 --> 00:00:49.200
<v Speaker 2>Absolutely and you know, while hitting complete one hundred percent

17
00:00:49.280 --> 00:00:53.479
<v Speaker 2>anonymity online that's a huge challenge, maybe impossible, right, it's

18
00:00:53.520 --> 00:00:56.759
<v Speaker 2>constantly changing. But understanding these tools, these tactics that really

19
00:00:56.759 --> 00:00:59.759
<v Speaker 2>empowers you and let's you make informed decisions about your

20
00:00:59.759 --> 00:01:02.479
<v Speaker 2>digital footprint, your whole security setup and just to be

21
00:01:02.520 --> 00:01:07.439
<v Speaker 2>super clear upfront, this discussion is purely about understanding the

22
00:01:07.439 --> 00:01:11.560
<v Speaker 2>source material, exploring the tech, the concepts. We're not endorsing

23
00:01:11.599 --> 00:01:13.400
<v Speaker 2>any specific activities mentioned of the book.

24
00:01:13.480 --> 00:01:17.000
<v Speaker 1>Okay, great clarification, So let's dive in the core stuff.

25
00:01:17.040 --> 00:01:19.480
<v Speaker 1>The book really sets up Tour the Onion router as

26
00:01:19.519 --> 00:01:22.040
<v Speaker 1>like the foundation. If you want to protect your identity

27
00:01:22.040 --> 00:01:24.879
<v Speaker 1>online for listeners who might be new to this, can

28
00:01:24.920 --> 00:01:27.159
<v Speaker 1>you give us a quick rundown? How does Tour actually,

29
00:01:28.000 --> 00:01:31.079
<v Speaker 1>you know, work its magic keep us synonymous?

30
00:01:31.280 --> 00:01:34.599
<v Speaker 2>Sure? So, Tour works by bouncing your Internet traffic through

31
00:01:34.599 --> 00:01:37.640
<v Speaker 2>this global network of volunteer servers. It encrypts your data

32
00:01:37.680 --> 00:01:40.200
<v Speaker 2>in layers. That's the Onion part of the name. Your

33
00:01:40.239 --> 00:01:44.799
<v Speaker 2>request goes through usually three random relays. There's an entry node,

34
00:01:45.040 --> 00:01:47.400
<v Speaker 2>a middle one, the relay node, and then an exit node.

35
00:01:47.519 --> 00:01:50.159
<v Speaker 2>And the key is each note only knows the IP

36
00:01:50.280 --> 00:01:52.480
<v Speaker 2>address of the one immediately before it and the one

37
00:01:52.480 --> 00:01:55.680
<v Speaker 2>immediately after it. It never knows your original IP and

38
00:01:55.719 --> 00:01:58.799
<v Speaker 2>the final destination together. So by the time your traffic

39
00:01:58.840 --> 00:02:01.200
<v Speaker 2>actually leaves that exit node and hits the website you're

40
00:02:01.200 --> 00:02:04.120
<v Speaker 2>going to tracing it back to you is incredibly difficult.

41
00:02:04.239 --> 00:02:07.599
<v Speaker 2>The real genius of Tour isn't just the encryption layers, though,

42
00:02:07.640 --> 00:02:10.479
<v Speaker 2>That's crucial is how it turns your activity into this

43
00:02:10.560 --> 00:02:14.120
<v Speaker 2>kind of digital ghost, makes tracing you back really really hard.

44
00:02:14.319 --> 00:02:16.840
<v Speaker 1>A digital ghost. I like that metaphor, but even ghosts,

45
00:02:16.960 --> 00:02:19.360
<v Speaker 1>they can leave fink traces if you're not careful. Right,

46
00:02:19.639 --> 00:02:21.759
<v Speaker 1>why does the book say the key vulnerability is in

47
00:02:21.800 --> 00:02:22.680
<v Speaker 1>this tour network?

48
00:02:23.039 --> 00:02:26.319
<v Speaker 2>Exactly? Yeah, yeah, the big one, the significant vulnerability is

49
00:02:26.360 --> 00:02:29.639
<v Speaker 2>at that exit node. If the data you're sending through

50
00:02:29.639 --> 00:02:32.479
<v Speaker 2>tour is just plain text, meaning you know it wasn't

51
00:02:32.599 --> 00:02:35.599
<v Speaker 2>encrypted before it even went into the Tour network, well,

52
00:02:35.599 --> 00:02:38.039
<v Speaker 2>then that exit node operator can see it, they can

53
00:02:38.080 --> 00:02:40.719
<v Speaker 2>decrypt it. And this is critical because look, anyone can

54
00:02:40.759 --> 00:02:46.120
<v Speaker 2>set up an exit node, law enforcement, hackers, foreign intelligence, anyone.

55
00:02:46.639 --> 00:02:50.280
<v Speaker 2>So if you're sending sensitive stuff unencrypted, that exit node

56
00:02:50.400 --> 00:02:52.919
<v Speaker 2>is a major potential interception point.

57
00:02:53.080 --> 00:02:55.439
<v Speaker 1>Okay, so that exit node sounds pretty risky. How do

58
00:02:55.479 --> 00:02:58.319
<v Speaker 1>you get around that problem? Then the book brings up

59
00:02:58.319 --> 00:03:00.719
<v Speaker 1>something called hidden services. You reckon iognize them by the

60
00:03:00.759 --> 00:03:03.919
<v Speaker 1>onion addresses. It calls them a clever solution. What makes

61
00:03:03.919 --> 00:03:04.520
<v Speaker 1>them different?

62
00:03:04.879 --> 00:03:07.759
<v Speaker 2>Right? Hidden services are different because they basically bypass that

63
00:03:07.840 --> 00:03:10.800
<v Speaker 2>traditional exit node. For the last step, when you connect

64
00:03:10.800 --> 00:03:13.879
<v Speaker 2>to a dot onion address, your connection stays fully encrypted

65
00:03:14.159 --> 00:03:17.800
<v Speaker 2>and to end within the Tour network itself. The website

66
00:03:17.840 --> 00:03:20.879
<v Speaker 2>you're visiting, the dot Onion site is the one decrypting

67
00:03:20.919 --> 00:03:24.879
<v Speaker 2>your message, not some random, potentially snooping exit node. It

68
00:03:24.960 --> 00:03:27.199
<v Speaker 2>means both you and the site are operating inside tour

69
00:03:27.319 --> 00:03:28.520
<v Speaker 2>securing the whole chain.

70
00:03:28.439 --> 00:03:32.199
<v Speaker 1>Gotcha and okay, outside of the Tour network itself. Another

71
00:03:32.240 --> 00:03:35.879
<v Speaker 1>really critical layer is HTTP secure HTTPS. We see it

72
00:03:35.879 --> 00:03:38.560
<v Speaker 1>all the time, that HTTPS. How does that fit into

73
00:03:38.560 --> 00:03:40.000
<v Speaker 1>this whole security picture.

74
00:03:40.199 --> 00:03:44.159
<v Speaker 2>Well, HTTPS encrypts the traffic directly between your browser and

75
00:03:44.199 --> 00:03:47.000
<v Speaker 2>the server you're connecting to, so it stops eavesdroppers, maybe

76
00:03:47.000 --> 00:03:49.439
<v Speaker 2>someone running that malicious tour exit node we talked about,

77
00:03:49.439 --> 00:03:53.039
<v Speaker 2>from seeing what you're sending or even injecting malware. And

78
00:03:53.039 --> 00:03:55.360
<v Speaker 2>the source makes a good point here. The strength of

79
00:03:55.360 --> 00:03:58.919
<v Speaker 2>that encryption really matters. A lot of sites still use older,

80
00:03:58.960 --> 00:04:01.319
<v Speaker 2>weaker keys. You really want to see at least a

81
00:04:01.360 --> 00:04:04.479
<v Speaker 2>twenty forty eight bit key, ideally forty ninety six bit.

82
00:04:04.759 --> 00:04:07.400
<v Speaker 2>But even with strong HTTPS, there's still a risk, right

83
00:04:07.439 --> 00:04:10.759
<v Speaker 2>if the web server itself gets compromised, then your data,

84
00:04:10.919 --> 00:04:13.159
<v Speaker 2>no matter how well it was encrypted, getting there could

85
00:04:13.199 --> 00:04:16.000
<v Speaker 2>still be exposed. It just reminds you every single link

86
00:04:16.040 --> 00:04:17.279
<v Speaker 2>in that chain has to be strong.

87
00:04:17.480 --> 00:04:20.639
<v Speaker 1>That makes sense, every link. So given all these risks,

88
00:04:20.759 --> 00:04:23.800
<v Speaker 1>the book then shifts to something really fundamental, almost regardless

89
00:04:23.800 --> 00:04:26.360
<v Speaker 1>of the tech, it's this piece of advice, never ever

90
00:04:26.439 --> 00:04:29.639
<v Speaker 1>give up identifying details about yourself online. And this leads

91
00:04:29.720 --> 00:04:32.680
<v Speaker 1>us straight into a powerful tool for that. PGP encryption.

92
00:04:32.920 --> 00:04:36.519
<v Speaker 2>Pretty good privacy, right, PGP The core idea there is

93
00:04:36.600 --> 00:04:39.439
<v Speaker 2>public and private keys. Think of it maybe like this.

94
00:04:40.800 --> 00:04:43.279
<v Speaker 2>Your public key is like an open padlock. You can

95
00:04:43.319 --> 00:04:45.240
<v Speaker 2>give that pablock out to anyone. They can use it

96
00:04:45.240 --> 00:04:47.360
<v Speaker 2>to lock a box, encrypt a message, a file just

97
00:04:47.399 --> 00:04:50.240
<v Speaker 2>for you, but only you have the matching private key

98
00:04:50.279 --> 00:04:53.800
<v Speaker 2>that can unlock that specific box, nobody else, not even

99
00:04:53.839 --> 00:04:55.800
<v Speaker 2>the person who locked it. And you can use this

100
00:04:55.879 --> 00:04:59.720
<v Speaker 2>for encrypting, decrypting, even digitally signing messages or files to

101
00:04:59.759 --> 00:05:02.040
<v Speaker 2>prove it came from you. You can encrypt whole disc

102
00:05:02.120 --> 00:05:05.800
<v Speaker 2>partitions with it. The really crucial thing to grasp with PGP, though,

103
00:05:06.079 --> 00:05:09.600
<v Speaker 2>is it gives you total control but also total responsibility.

104
00:05:09.839 --> 00:05:12.360
<v Speaker 2>If you lose your private key, there's no password reset,

105
00:05:12.399 --> 00:05:15.439
<v Speaker 2>there's no recovery that data is locked away forever.

106
00:05:15.639 --> 00:05:18.480
<v Speaker 1>That padlock analogy is great. Really makes the public private

107
00:05:18.519 --> 00:05:21.279
<v Speaker 1>key thing click. You're building this digital fortress and you

108
00:05:21.319 --> 00:05:24.079
<v Speaker 1>hold the only key. Really drives home how vital protecting

109
00:05:24.199 --> 00:05:26.759
<v Speaker 1>that private key is so? Okay? How do you actually

110
00:05:26.839 --> 00:05:29.879
<v Speaker 1>use something like PGP without it being super complex for

111
00:05:29.920 --> 00:05:33.360
<v Speaker 1>the average person? The book points to TAILS, this live

112
00:05:33.399 --> 00:05:36.360
<v Speaker 1>operating system as a practical way to make using PGP

113
00:05:36.519 --> 00:05:38.519
<v Speaker 1>and boosting anonymity much easier.

114
00:05:38.720 --> 00:05:42.519
<v Speaker 2>Yeah, TAILS is, it's a fantastic tool. It's designed specifically

115
00:05:42.519 --> 00:05:45.319
<v Speaker 2>for anonymity and privacy right from the start. It's a

116
00:05:45.360 --> 00:05:47.560
<v Speaker 2>live OS, which means you run it straight from a

117
00:05:47.600 --> 00:05:51.240
<v Speaker 2>DVD or more commonly now a USB drive. You don't

118
00:05:51.279 --> 00:05:54.920
<v Speaker 2>install it on your computer's main hard drive. For Windows users,

119
00:05:54.959 --> 00:05:57.560
<v Speaker 2>you can also run it inside something called a virtual box,

120
00:05:57.680 --> 00:06:00.199
<v Speaker 2>which is like running a computer within your computer on

121
00:06:00.240 --> 00:06:02.839
<v Speaker 2>top of your normal Windows. But the real beauty of

122
00:06:02.920 --> 00:06:06.160
<v Speaker 2>running TAILS from external media like that USB stick it

123
00:06:06.279 --> 00:06:09.439
<v Speaker 2>seriously reduces the risk. It isolates you from potential malware

124
00:06:09.560 --> 00:06:12.399
<v Speaker 2>keyloggers that might be hiding on your main Window system

125
00:06:12.480 --> 00:06:13.879
<v Speaker 2>exploding vulnerabilities there.

126
00:06:14.120 --> 00:06:18.040
<v Speaker 1>Right, so using the USB sounds much safer. What's the risk.

127
00:06:18.079 --> 00:06:20.839
<v Speaker 1>Then if you do run it using virtual box directly

128
00:06:20.879 --> 00:06:21.560
<v Speaker 1>on your hard drive.

129
00:06:21.839 --> 00:06:24.759
<v Speaker 2>Well, running virtual box and TAILS directly off your hard drive,

130
00:06:25.079 --> 00:06:27.720
<v Speaker 2>that carries a pretty big danger. Even if you delete

131
00:06:27.759 --> 00:06:31.000
<v Speaker 2>files within TAILS. Running that way, temporary files can often

132
00:06:31.040 --> 00:06:34.040
<v Speaker 2>get left behind on the host machine's hard drive, and

133
00:06:34.079 --> 00:06:37.399
<v Speaker 2>those temporary files can sometimes be recovered later using forensic tools,

134
00:06:37.600 --> 00:06:41.360
<v Speaker 2>potentially revealing stuff you thought was totally private. The source

135
00:06:41.439 --> 00:06:44.439
<v Speaker 2>really advises against this setup. It pushes hard for running

136
00:06:44.439 --> 00:06:47.160
<v Speaker 2>everything off a USB. In fact, it even suggests using

137
00:06:47.160 --> 00:06:50.399
<v Speaker 2>a separate USB drive just for storing your PGP private

138
00:06:50.480 --> 00:06:53.720
<v Speaker 2>keys and other super sensitive data. Keep it totally separate

139
00:06:53.759 --> 00:06:56.399
<v Speaker 2>from your main hard drive. Create more layers. Wow.

140
00:06:56.439 --> 00:07:01.959
<v Speaker 1>Okay, that's some serious compartmentalization, keeping things physical separate. Speaking

141
00:07:02.000 --> 00:07:04.920
<v Speaker 1>of encrypting data, the book also talks about full disc

142
00:07:05.079 --> 00:07:09.079
<v Speaker 1>encryption FDE. This seems to take the PGP idea beyond

143
00:07:09.079 --> 00:07:11.920
<v Speaker 1>just files and basically lock down your entire device. How

144
00:07:11.959 --> 00:07:13.240
<v Speaker 1>does that work FDE?

145
00:07:13.480 --> 00:07:17.199
<v Speaker 2>Yeah, it protects the whole drive by encrypting the entire filesystem,

146
00:07:17.680 --> 00:07:21.240
<v Speaker 2>all the data on it becomes inaccessible without the right passphrase.

147
00:07:21.959 --> 00:07:24.040
<v Speaker 2>Kal's actually has a built in feature for this, which

148
00:07:24.079 --> 00:07:27.120
<v Speaker 2>is another reason it's often recommended. It makes encrypting the

149
00:07:27.120 --> 00:07:31.480
<v Speaker 2>persistent storage on your tail's USB pretty straightforward. But just

150
00:07:31.519 --> 00:07:34.480
<v Speaker 2>like PGP private keys, the critical thing here's that passphrase.

151
00:07:34.879 --> 00:07:38.319
<v Speaker 2>If you lose your FDE passphrase, there's no getting back in,

152
00:07:38.480 --> 00:07:41.160
<v Speaker 2>no recovery option. Your only choice is to wipe the

153
00:07:41.199 --> 00:07:44.360
<v Speaker 2>drive completely and start over. So pick a strong one

154
00:07:44.560 --> 00:07:45.439
<v Speaker 2>and don't forget it.

155
00:07:45.399 --> 00:07:48.319
<v Speaker 1>Right another, don't lose the key situation and building on

156
00:07:48.360 --> 00:07:51.120
<v Speaker 1>that data protection, the book really hammers home the importance

157
00:07:51.120 --> 00:07:53.519
<v Speaker 1>of file shredding. Why isn't just hitting delete good enough?

158
00:07:53.839 --> 00:07:56.480
<v Speaker 2>Because when you delete a file, normally you're mostly just

159
00:07:56.519 --> 00:07:58.920
<v Speaker 2>telling the operating system, hey, the space's file used is

160
00:07:58.959 --> 00:08:02.399
<v Speaker 2>now available for something else. The actual data often just

161
00:08:02.399 --> 00:08:04.079
<v Speaker 2>sit there on the hard drive until it happens to

162
00:08:04.120 --> 00:08:06.519
<v Speaker 2>get overwritten by new data, which means it is often

163
00:08:06.560 --> 00:08:10.519
<v Speaker 2>easily recoverable with forensic software. Fileshredding actually overwrites the file's

164
00:08:10.560 --> 00:08:14.560
<v Speaker 2>location with random data, usually multiple times, to make recovery

165
00:08:14.600 --> 00:08:19.199
<v Speaker 2>practically impossible. The book mentions different standards NSA recommending three passes,

166
00:08:19.560 --> 00:08:22.759
<v Speaker 2>DoD seven, Gutman method thirty five, and even you know

167
00:08:22.800 --> 00:08:25.160
<v Speaker 2>three to seven passes is generally seen as pretty solid

168
00:08:25.160 --> 00:08:27.839
<v Speaker 2>for most people, and not doing this can have real consequences.

169
00:08:27.879 --> 00:08:31.800
<v Speaker 2>It mentions topiary from Leusek, who was actually banned from

170
00:08:31.920 --> 00:08:34.840
<v Speaker 2>using file shredders as part of his sentence, specifically so

171
00:08:34.919 --> 00:08:38.039
<v Speaker 2>the FBI could monitor his drive contents. So yeah, tools

172
00:08:38.039 --> 00:08:40.879
<v Speaker 2>like deband file shredder, even seacleaner has a shredding option,

173
00:08:41.039 --> 00:08:41.679
<v Speaker 2>they're important.

174
00:08:41.759 --> 00:08:44.840
<v Speaker 1>Okay, that makes sense. Deleting isn't really deleting. So let's

175
00:08:44.879 --> 00:08:47.279
<v Speaker 1>pull some of this together. What's the big takeaway here?

176
00:08:47.840 --> 00:08:51.320
<v Speaker 1>Our online actions they leave these digital breadcrumbs, and sometimes

177
00:08:51.360 --> 00:08:54.480
<v Speaker 1>those crumbs aren't just cookies or history. The book gets

178
00:08:54.480 --> 00:08:58.240
<v Speaker 1>into JavaScript vulnerabilities and it mentions the tour mailbust back

179
00:08:58.279 --> 00:09:00.480
<v Speaker 1>in mid twenty thirteen. What actually happen in there?

180
00:09:00.639 --> 00:09:02.480
<v Speaker 2>Right? That was a big one. In that case, federal

181
00:09:02.519 --> 00:09:05.840
<v Speaker 2>agents managed to inject some malicious JavaScript onto servers hosting

182
00:09:05.879 --> 00:09:09.039
<v Speaker 2>certain hidden services, including what was supposed to be a

183
00:09:09.039 --> 00:09:13.000
<v Speaker 2>secure email platform. So when users visited those sites, this

184
00:09:13.120 --> 00:09:17.120
<v Speaker 2>nasty code would run inside their own browser, and it

185
00:09:17.200 --> 00:09:20.639
<v Speaker 2>basically forced the browser to reveal their real IP address

186
00:09:20.679 --> 00:09:25.399
<v Speaker 2>and other identifying info completely bypassing tours protection for those users.

187
00:09:26.039 --> 00:09:28.399
<v Speaker 2>The key insight, right, is that even if you're using tour,

188
00:09:28.679 --> 00:09:31.120
<v Speaker 2>malicious code running in your browser can still unmask you.

189
00:09:31.559 --> 00:09:34.440
<v Speaker 2>It's a stark reminder way you might seriously consider disabling

190
00:09:34.519 --> 00:09:38.519
<v Speaker 2>JavaScript in browsers like Ice, Weasel or Firefox. You can

191
00:09:38.559 --> 00:09:40.840
<v Speaker 2>do that in the about dot config settings. Just got

192
00:09:40.879 --> 00:09:43.000
<v Speaker 2>to remember if you're using TAILS, that resets each time,

193
00:09:43.159 --> 00:09:45.240
<v Speaker 2>so you have to redisable JavaScript every time you boot

194
00:09:45.279 --> 00:09:46.559
<v Speaker 2>up TAILS. If that's your strategy.

195
00:09:46.679 --> 00:09:48.960
<v Speaker 1>Wow, okay, So the browser itself can betray you, and

196
00:09:49.000 --> 00:09:53.440
<v Speaker 1>it's not just code, right, metadata, particularly this EXIF data

197
00:09:53.480 --> 00:09:55.919
<v Speaker 1>hidden in photos. That's another silent betrayer.

198
00:09:56.039 --> 00:09:59.039
<v Speaker 2>Oh. Absolutely. The insight there is that even your innocent

199
00:09:59.080 --> 00:10:02.039
<v Speaker 2>looking photos can carry hidden data like GPS coordinates, the

200
00:10:02.039 --> 00:10:04.480
<v Speaker 2>type of camera use, sometimes even the date and time.

201
00:10:04.559 --> 00:10:07.279
<v Speaker 2>There's that infamous case of the hacker rumor. He apparently

202
00:10:07.320 --> 00:10:10.279
<v Speaker 2>posted pictures of his girlfriend online and embedded in the

203
00:10:10.320 --> 00:10:14.440
<v Speaker 2>EXIF data where iPhone GPS coordinates that led the authorities

204
00:10:14.519 --> 00:10:17.559
<v Speaker 2>right to his location. And another big example was John

205
00:10:17.600 --> 00:10:21.360
<v Speaker 2>McAfee's arrest in Guatemala. A photo published by Vice magazine

206
00:10:21.399 --> 00:10:25.399
<v Speaker 2>supposedly contained EXIF data that pinpointed where he was hiding.

207
00:10:25.600 --> 00:10:28.440
<v Speaker 2>So the advice is generally maybe used PNG images instead

208
00:10:28.440 --> 00:10:32.759
<v Speaker 2>of JPEGs as PNGs usually don't store exif, and always

209
00:10:32.879 --> 00:10:36.279
<v Speaker 2>always check your images with an online tool like viexfdata

210
00:10:36.320 --> 00:10:38.559
<v Speaker 2>dot com before you upload them anywhere sensitive.

211
00:10:38.240 --> 00:10:41.840
<v Speaker 1>Good tip check your photos. Okay, beyond deliberate exploits like

212
00:10:41.919 --> 00:10:45.279
<v Speaker 1>JavaScript or hidden data like exif, what about just plan

213
00:10:45.360 --> 00:10:48.159
<v Speaker 1>old tracking cookies. The book talks about how companies like

214
00:10:48.200 --> 00:10:51.200
<v Speaker 1>Google use these to build up detailed profiles of our browsing.

215
00:10:51.360 --> 00:10:53.799
<v Speaker 1>What's the danger there for someone trying to stay anonymous?

216
00:10:54.120 --> 00:10:57.720
<v Speaker 2>The danger the implication is that even if you're using

217
00:10:57.759 --> 00:11:01.919
<v Speaker 2>tour to hide your IP, goverment agencies or others can

218
00:11:01.960 --> 00:11:06.000
<v Speaker 2>potentially leverage these tracking profiles. They can correlate your activity.

219
00:11:06.600 --> 00:11:09.519
<v Speaker 2>If you use tour for some let's say freedom fighting activity,

220
00:11:09.840 --> 00:11:11.759
<v Speaker 2>and then in the same tour session you log into

221
00:11:11.799 --> 00:11:14.759
<v Speaker 2>your personal Facebook or Google something specific to your local area.

222
00:11:15.200 --> 00:11:18.480
<v Speaker 2>While those patterns create connections, they link those different activities

223
00:11:18.519 --> 00:11:22.480
<v Speaker 2>back to potentially one person. That's why the book strongly

224
00:11:22.559 --> 00:11:25.960
<v Speaker 2>warns against mixing your online identities or activities within the

225
00:11:25.960 --> 00:11:26.840
<v Speaker 2>same tour session.

226
00:11:26.960 --> 00:11:29.279
<v Speaker 1>Keep things separate, right, don't cross the streams and the tracking.

227
00:11:29.320 --> 00:11:31.519
<v Speaker 1>It goes beyond just standard cookies, doesn't it. There are

228
00:11:31.559 --> 00:11:34.679
<v Speaker 1>things like flash cookies, local stored objects, and DOM storage.

229
00:11:34.840 --> 00:11:37.919
<v Speaker 2>Yeah, those are like super cookies. They can be much

230
00:11:37.960 --> 00:11:41.000
<v Speaker 2>more persistent and harder to clear than regular browser cookies.

231
00:11:41.279 --> 00:11:44.120
<v Speaker 2>They can also track your activity across different websites, often

232
00:11:44.240 --> 00:11:46.960
<v Speaker 2>quite aggressively. Now you can usually manage or disable these.

233
00:11:46.960 --> 00:11:50.039
<v Speaker 2>There are settings in Adobe Flash player itself and in

234
00:11:50.159 --> 00:11:53.519
<v Speaker 2>firefoxes about dot canfig You can toggle dom dot storage

235
00:11:53.559 --> 00:11:56.519
<v Speaker 2>dot enable to falls. But it's worth noting one of

236
00:11:56.519 --> 00:11:59.039
<v Speaker 2>the nice things about tails is that it automatically clears

237
00:11:59.200 --> 00:12:02.480
<v Speaker 2>standard cookies every session. And importantly, it doesn't even come

238
00:12:02.519 --> 00:12:05.279
<v Speaker 2>with Flash installed by default, so that offers some built

239
00:12:05.320 --> 00:12:07.559
<v Speaker 2>in protection against those specific tracking methods.

240
00:12:07.799 --> 00:12:10.519
<v Speaker 1>Okay, so tails helps there. But all these little data

241
00:12:10.519 --> 00:12:14.360
<v Speaker 1>points cookies exif JavaScript settings, they can apparently add up

242
00:12:14.360 --> 00:12:18.600
<v Speaker 1>to something even more insidious, browser fingerprinting. What exactly is

243
00:12:18.600 --> 00:12:20.159
<v Speaker 1>that and why should we worry about it?

244
00:12:20.399 --> 00:12:24.799
<v Speaker 2>Browser fingerprinting is basically creating a unique digital signature, a

245
00:12:24.799 --> 00:12:28.320
<v Speaker 2>fingerprint for your specific browser setup. It collects a whole

246
00:12:28.360 --> 00:12:31.039
<v Speaker 2>bunch of data points, things like which browser plugins you

247
00:12:31.080 --> 00:12:35.039
<v Speaker 2>have installed, your screen resolution, your system fonts, your time zone,

248
00:12:35.200 --> 00:12:38.679
<v Speaker 2>the exact browser version or user agent, and the combination

249
00:12:38.759 --> 00:12:41.559
<v Speaker 2>of all these things can often be surprisingly unique to you.

250
00:12:42.159 --> 00:12:44.559
<v Speaker 2>So even if you're using tour or VPN to hide

251
00:12:44.600 --> 00:12:48.000
<v Speaker 2>your IP address, this unique fingerprint might remain consistent across

252
00:12:48.039 --> 00:12:51.360
<v Speaker 2>different sessions or websites. That makes it easier for sophisticated

253
00:12:51.399 --> 00:12:54.559
<v Speaker 2>trackers to correlate your activity. They might not know who

254
00:12:54.600 --> 00:12:56.759
<v Speaker 2>you are, but they know it's the same browsers showing

255
00:12:56.799 --> 00:12:59.840
<v Speaker 2>up again and again. The core insight here is yeah,

256
00:13:00.000 --> 00:13:03.720
<v Speaker 2>even without cookies, you might still be uniquely identifiable just

257
00:13:03.720 --> 00:13:06.559
<v Speaker 2>by how your browser looks to a website. That's another

258
00:13:06.600 --> 00:13:09.480
<v Speaker 2>reason the book recommends using TAILS and disabling JavaScript. Tails

259
00:13:09.720 --> 00:13:12.840
<v Speaker 2>tries to standardize many of these fingerprinting characteristics to make

260
00:13:12.919 --> 00:13:13.879
<v Speaker 2>users look more alike.

261
00:13:14.039 --> 00:13:17.600
<v Speaker 1>Okay, wow, that's a lot. On the technical side. We've

262
00:13:17.639 --> 00:13:22.639
<v Speaker 1>covered tour encryption, file shredding, JavaScript metadata fingerprinting, but the

263
00:13:22.639 --> 00:13:26.159
<v Speaker 1>book makes a really crucial point. The best tech setup

264
00:13:26.159 --> 00:13:29.679
<v Speaker 1>in the world can be completely undermined by simple human error.

265
00:13:30.200 --> 00:13:32.120
<v Speaker 1>This brings us to the human factor in all this.

266
00:13:32.840 --> 00:13:35.559
<v Speaker 1>What are some of the general precautions the book advises

267
00:13:35.600 --> 00:13:37.799
<v Speaker 1>when posting or interacting online?

268
00:13:38.039 --> 00:13:41.080
<v Speaker 2>Right, the human element, It's huge. The book really pushes

269
00:13:41.080 --> 00:13:44.879
<v Speaker 2>for using multiple online identities compartmentalization. Maybe you have one

270
00:13:44.919 --> 00:13:47.840
<v Speaker 2>persona for buying things, a totally separate one for selling,

271
00:13:48.039 --> 00:13:50.759
<v Speaker 2>another one just for posting on forums. This makes it

272
00:13:50.879 --> 00:13:53.399
<v Speaker 2>much much harder for anyone watching to link all your

273
00:13:53.440 --> 00:13:57.240
<v Speaker 2>different activities together and to manage all the different, complex,

274
00:13:57.440 --> 00:14:00.159
<v Speaker 2>unique passwords you absolutely should be using. For you to

275
00:14:00.200 --> 00:14:03.840
<v Speaker 2>these identities, a password manager is key. The book suggests

276
00:14:03.919 --> 00:14:06.759
<v Speaker 2>key pass x, which is conveniently included in TAILS. The

277
00:14:06.799 --> 00:14:09.399
<v Speaker 2>insight is really that consistency using the same user name,

278
00:14:09.440 --> 00:14:12.360
<v Speaker 2>same password, same style across different platforms. That can be

279
00:14:12.399 --> 00:14:14.159
<v Speaker 2>your biggest vulnerability. Mix it up.

280
00:14:14.200 --> 00:14:17.519
<v Speaker 1>That makes total sense, separate identities, but it's fascinating. It's

281
00:14:17.559 --> 00:14:21.720
<v Speaker 1>not just technical consistency, right. The book talks about behavioral

282
00:14:21.720 --> 00:14:23.159
<v Speaker 1>patterns being identifiers too.

283
00:14:23.240 --> 00:14:27.639
<v Speaker 2>Oh, absolutely, this is critical. Things like unique grammar mistakes

284
00:14:27.639 --> 00:14:31.600
<v Speaker 2>you always make, consistent spelling errors, using specific slang terms,

285
00:14:31.639 --> 00:14:35.159
<v Speaker 2>even the times a day you're predictably online. All of

286
00:14:35.159 --> 00:14:38.320
<v Speaker 2>these can be used to build a profile and potentially

287
00:14:38.320 --> 00:14:41.600
<v Speaker 2>identify you, even across different user names. The source really

288
00:14:41.600 --> 00:14:45.399
<v Speaker 2>emphasizes look, law enforcement assumes they're reading everything they expect to.

289
00:14:45.679 --> 00:14:48.000
<v Speaker 2>They have people whose job it is to sit there

290
00:14:48.159 --> 00:14:51.960
<v Speaker 2>sift through forum posts chat logs, everything, actively looking for

291
00:14:52.000 --> 00:14:55.600
<v Speaker 2>these correlations, these little behavioral tics that link an anonymous

292
00:14:55.600 --> 00:14:58.759
<v Speaker 2>persona back to a real person. They don't underestimate your

293
00:14:58.799 --> 00:15:01.279
<v Speaker 2>online persona, so you shouldn't to estimate their dedication to

294
00:15:01.320 --> 00:15:04.559
<v Speaker 2>finding those links. Your unique digital voice can give you away.

295
00:15:04.720 --> 00:15:08.240
<v Speaker 1>That's sobering. They're actively looking for your quirks, which raises

296
00:15:08.279 --> 00:15:11.639
<v Speaker 1>a big question just how far law enforcement go to

297
00:15:11.759 --> 00:15:14.759
<v Speaker 1>catch someone online. The Sorts gives some pretty eye opening

298
00:15:14.879 --> 00:15:16.000
<v Speaker 1>real world examples.

299
00:15:16.159 --> 00:15:21.080
<v Speaker 2>Yeah, they will go to frankly incredible lengths. The book

300
00:15:21.240 --> 00:15:24.480
<v Speaker 2>cites the DEA's sting in the Silk Road case, an

301
00:15:24.600 --> 00:15:29.120
<v Speaker 2>undercover agent literally shipped a kilogram of cocaine to Curtis

302
00:15:29.159 --> 00:15:32.279
<v Speaker 2>Green his online name was Flush, basically setting him up

303
00:15:32.279 --> 00:15:35.399
<v Speaker 2>for a major bust. Then there was Operation Open Market.

304
00:15:35.679 --> 00:15:38.240
<v Speaker 2>This was the secret service running a fake online ID

305
00:15:38.480 --> 00:15:42.200
<v Speaker 2>vendor site for five years. They posed as criminals selling

306
00:15:42.279 --> 00:15:46.039
<v Speaker 2>fake IDs, ship them out, gathered evidence, and eventually brought

307
00:15:46.039 --> 00:15:50.000
<v Speaker 2>down fifty five different defendants using Ricodact charges. That's the

308
00:15:50.039 --> 00:15:52.240
<v Speaker 2>kind of law I usually used against the mob. Shows

309
00:15:52.279 --> 00:15:54.440
<v Speaker 2>how seriously they take this stuff, and it's not just

310
00:15:54.480 --> 00:15:57.000
<v Speaker 2>for huge cases. It even mentions a local police department

311
00:15:57.080 --> 00:15:59.840
<v Speaker 2>running a fake sweepstakes like something out of The Simpsons,

312
00:15:59.840 --> 00:16:03.360
<v Speaker 2>just to lure in people with outstanding warrants by promising prizes.

313
00:16:03.600 --> 00:16:05.159
<v Speaker 2>They arrested quite a few people that way.

314
00:16:05.279 --> 00:16:08.919
<v Speaker 1>Wow, a fake sweepstakes. That's incredible commitment or maybe deception,

315
00:16:09.080 --> 00:16:10.919
<v Speaker 1>depending on how you look at it. It really shows the

316
00:16:10.919 --> 00:16:14.519
<v Speaker 1>resources they'll deploy. What were the actual consequences for people

317
00:16:14.559 --> 00:16:17.399
<v Speaker 1>caught in operations like the Silk Road sting or Operation

318
00:16:17.480 --> 00:16:18.480
<v Speaker 1>Open Market.

319
00:16:18.320 --> 00:16:21.559
<v Speaker 2>Well, they're incredibly severe. Curtis Green, the guy who received

320
00:16:21.559 --> 00:16:24.559
<v Speaker 2>the cocaine shipment, he was reportedly facing up to forty

321
00:16:24.639 --> 00:16:27.399
<v Speaker 2>years in prison, and those fifty five people charged under

322
00:16:27.399 --> 00:16:30.559
<v Speaker 2>the IICO Act and Operation Open Market, they were potentially

323
00:16:30.600 --> 00:16:33.559
<v Speaker 2>looking at twenty years each. The clear takeaway, the insight

324
00:16:33.600 --> 00:16:35.559
<v Speaker 2>the book drives home is that it really only takes

325
00:16:35.559 --> 00:16:38.759
<v Speaker 2>one mistake, one slip up, and once law enforcement is

326
00:16:38.799 --> 00:16:42.559
<v Speaker 2>on to you, they will pursue you relentlessly. Often the

327
00:16:42.600 --> 00:16:45.159
<v Speaker 2>resources you just can't match. The consequences are very real.

328
00:16:45.120 --> 00:16:48.480
<v Speaker 1>Very heavy, definitely a sobering reality check. So learning from

329
00:16:48.559 --> 00:16:51.600
<v Speaker 1>other's mistakes becomes absolutely crucial. The case of Sabu, the

330
00:16:51.679 --> 00:16:54.320
<v Speaker 1>leader of LOSK, is a really stark example he had

331
00:16:54.320 --> 00:16:58.039
<v Speaker 1>this invincibility mindset, but it crumbled. What were his key mistakes?

332
00:16:58.399 --> 00:17:02.960
<v Speaker 2>Sabu, Yeah, hector. Despite his online persona, he made at

333
00:17:03.039 --> 00:17:06.839
<v Speaker 2>least two critical errors that ultimately exposed him. First, apparently,

334
00:17:06.880 --> 00:17:10.160
<v Speaker 2>he once logged into an IRC chat that's Internet Relay Chat,

335
00:17:10.519 --> 00:17:13.400
<v Speaker 2>an older chat system, using his real home IP address.

336
00:17:13.720 --> 00:17:16.599
<v Speaker 2>He forgot to connect through his usual anonymizing proxy first.

337
00:17:17.119 --> 00:17:19.799
<v Speaker 2>That single log in was reportedly enough for federal agents

338
00:17:19.839 --> 00:17:23.720
<v Speaker 2>to Pinpoor in his location. One mistake. But even before that,

339
00:17:23.920 --> 00:17:27.160
<v Speaker 2>another hacking group had apparently dosed him released his personal

340
00:17:27.160 --> 00:17:30.039
<v Speaker 2>info because of an error with his domain registration. His

341
00:17:30.119 --> 00:17:33.119
<v Speaker 2>proxy service used for the registration expired and the domain

342
00:17:33.160 --> 00:17:36.160
<v Speaker 2>registrar GoDaddy apparently used his real name and address when

343
00:17:36.160 --> 00:17:39.880
<v Speaker 2>it renewed. Another slip up. The insight here is just

344
00:17:39.960 --> 00:17:43.480
<v Speaker 2>how fragile anonymity can be. One moment of carelessness, what

345
00:17:43.559 --> 00:17:47.759
<v Speaker 2>expired service, one configuration error, and years of effort can unravel.

346
00:17:47.799 --> 00:17:50.279
<v Speaker 1>And how did the FBI end up leveraging Zabou once

347
00:17:50.319 --> 00:17:53.119
<v Speaker 1>they had him. That must have been an intense situation, yet, yeah,

348
00:17:53.160 --> 00:17:53.599
<v Speaker 1>intense is.

349
00:17:53.559 --> 00:17:57.480
<v Speaker 2>Probably an understatement. They used the human element again, his children.

350
00:17:57.680 --> 00:17:59.640
<v Speaker 2>He was facing something like one hundred and twelve years

351
00:17:59.680 --> 00:18:03.160
<v Speaker 2>in prison. The FBI reportedly used his desire to stay

352
00:18:03.160 --> 00:18:06.240
<v Speaker 2>with his kids his biggest vulnerability to turn him. He

353
00:18:06.279 --> 00:18:09.319
<v Speaker 2>became an informant, working against his former associates, people he

354
00:18:09.400 --> 00:18:12.559
<v Speaker 2>called friends, like Jeremy Hammond, and the FBI's investigation into

355
00:18:12.640 --> 00:18:16.319
<v Speaker 2>Hammond is detailed in the source, was just meticulous. It

356
00:18:16.359 --> 00:18:20.599
<v Speaker 2>shows their persistence. They connected his different online aliases subdigging

357
00:18:20.640 --> 00:18:23.359
<v Speaker 2>and archaos to his real life. They found links to

358
00:18:23.400 --> 00:18:26.200
<v Speaker 2>protests he attended, like one in Saint Louis, his arrest

359
00:18:26.200 --> 00:18:29.119
<v Speaker 2>at the two thousand and four RNC, even minor details

360
00:18:29.160 --> 00:18:31.640
<v Speaker 2>like marijuana arrests or a comment he made about being

361
00:18:31.680 --> 00:18:34.839
<v Speaker 2>a freaking goddess related to dumpster diving. They even tracked

362
00:18:34.839 --> 00:18:37.759
<v Speaker 2>his specific MacBooks m Mooxya address, connecting to tour notes

363
00:18:37.880 --> 00:18:40.039
<v Speaker 2>and correlated times he left his house with his activity

364
00:18:40.039 --> 00:18:43.039
<v Speaker 2>on irc. It's a really chilling illustration of how deep

365
00:18:43.079 --> 00:18:46.519
<v Speaker 2>these investigations go. They connect every tiny digital breadcrumb to

366
00:18:46.559 --> 00:18:47.880
<v Speaker 2>physical world actions.

367
00:18:48.079 --> 00:18:51.640
<v Speaker 1>That is chilling and a powerful reminder of the pressure involved,

368
00:18:51.680 --> 00:18:54.799
<v Speaker 1>the human cost. It really underscores that idea we touched

369
00:18:54.839 --> 00:18:58.039
<v Speaker 1>on nobody goes to jail for you, so knowing that

370
00:18:58.160 --> 00:19:01.200
<v Speaker 1>level of pressure exists. The book offers advice if you

371
00:19:01.279 --> 00:19:05.359
<v Speaker 1>do find yourself facing an interrogation, what's the recommended protocol?

372
00:19:05.559 --> 00:19:09.720
<v Speaker 2>Right if the worst happens first and absolutely foremost, retain

373
00:19:09.759 --> 00:19:12.680
<v Speaker 2>a lawyer beforehand, get one on retainer. The source even

374
00:19:12.720 --> 00:19:16.440
<v Speaker 2>suggests a figure around fifty thousand dollars, because the logic is,

375
00:19:16.519 --> 00:19:20.119
<v Speaker 2>if you're arrested, the authorities might seize all your assets immediately.

376
00:19:20.400 --> 00:19:22.720
<v Speaker 2>If your money is frozen, you might not be able

377
00:19:22.720 --> 00:19:24.559
<v Speaker 2>to hire a lawyer when you need one. Most a

378
00:19:24.599 --> 00:19:28.359
<v Speaker 2>prepaid retainer avoids that. Then during questioning, keep your mouth

379
00:19:28.400 --> 00:19:31.319
<v Speaker 2>shut immediately and clearly demand a lawyer. And the book

380
00:19:31.359 --> 00:19:35.720
<v Speaker 2>advice is dropping any kind of attitude or denial, act scared, anxious, confused,

381
00:19:35.720 --> 00:19:39.039
<v Speaker 2>maybe not defiant, and truly speak honestly only with your lawyer.

382
00:19:39.319 --> 00:19:42.720
<v Speaker 2>That conversation is protected by attorney client privilege. Anything you

383
00:19:42.720 --> 00:19:45.400
<v Speaker 2>say to law enforcement is fair game. The core insight

384
00:19:45.480 --> 00:19:48.519
<v Speaker 2>is simple. Silence and legal counsel are your strongest shield

385
00:19:48.559 --> 00:19:49.359
<v Speaker 2>in that situation.

386
00:19:49.599 --> 00:19:53.480
<v Speaker 1>Get a lawyer, keep quiet. Got it? This invincibility mindset

387
00:19:53.519 --> 00:19:56.960
<v Speaker 1>you mentioned with Sabu, it's clearly dangerous when facing government

388
00:19:57.000 --> 00:19:59.559
<v Speaker 1>power and what the book calls their bullying tactics. And

389
00:19:59.599 --> 00:20:02.200
<v Speaker 1>it's not just this individual's rate. Companies get forced to

390
00:20:02.240 --> 00:20:02.839
<v Speaker 1>comply too.

391
00:20:03.119 --> 00:20:07.400
<v Speaker 2>Oh. Absolutely, companies, even ones that champion privacy, often find

392
00:20:07.440 --> 00:20:11.160
<v Speaker 2>themselves compelled by court orders. There's no real choice sometimes.

393
00:20:11.559 --> 00:20:13.920
<v Speaker 2>Hush Mail is a famous example. They were forced to

394
00:20:13.920 --> 00:20:16.759
<v Speaker 2>hand over something like twelve CDs worth of emails from

395
00:20:16.839 --> 00:20:20.200
<v Speaker 2>three accounts under court order, laugh of them. The email

396
00:20:20.240 --> 00:20:23.119
<v Speaker 2>service Edward Snowden Use is another one. The owner tried

397
00:20:23.160 --> 00:20:25.519
<v Speaker 2>to resist a court order demanding his encryption keys. He

398
00:20:25.599 --> 00:20:28.400
<v Speaker 2>was fined five thousand dollars a day until he finally

399
00:20:28.440 --> 00:20:30.680
<v Speaker 2>gave them up, which ultimately led him to shut down

400
00:20:30.680 --> 00:20:33.599
<v Speaker 2>the entire service rather than compromise all his users. It

401
00:20:33.640 --> 00:20:36.839
<v Speaker 2>perfectly illustrates that quote the book uses from the groog

402
00:20:37.519 --> 00:20:40.359
<v Speaker 2>Nobody is going to go to jail for you, and

403
00:20:40.400 --> 00:20:44.279
<v Speaker 2>that includes VPN providers. Hide My Ass another VPN service

404
00:20:44.640 --> 00:20:47.079
<v Speaker 2>handed over user logs related to the law Set case

405
00:20:47.119 --> 00:20:49.640
<v Speaker 2>when they were faced with the UK court order. The

406
00:20:49.720 --> 00:20:52.400
<v Speaker 2>insight is stark. When push comes a shove, under enough

407
00:20:52.480 --> 00:20:55.559
<v Speaker 2>legal or financial pressure, almost any third party service will

408
00:20:55.599 --> 00:20:58.400
<v Speaker 2>likely comply with authorities. Can't really rely on them to

409
00:20:58.400 --> 00:21:00.000
<v Speaker 2>protect you if they themselves are threatened.

410
00:21:00.200 --> 00:21:02.480
<v Speaker 1>It really does feel like a stack deck sometimes, but

411
00:21:02.880 --> 00:21:06.880
<v Speaker 1>okay for someone facing truly dire circumstances. The book does

412
00:21:07.079 --> 00:21:10.680
<v Speaker 1>mention potential locations for fleeing. What are the caveats there?

413
00:21:10.759 --> 00:21:13.599
<v Speaker 2>Yeah, it lists some countries that historically haven't had US

414
00:21:13.759 --> 00:21:16.799
<v Speaker 2>extradition treaties. But and this is a huge but it's

415
00:21:16.799 --> 00:21:19.519
<v Speaker 2>not a guaranteed safe haven at all. It mentions Cambodia,

416
00:21:19.559 --> 00:21:22.400
<v Speaker 2>for example, which actually extradited one of the Pirate Bay

417
00:21:22.400 --> 00:21:26.319
<v Speaker 2>founders despite not having a formal treaty. Political pressure is real.

418
00:21:26.599 --> 00:21:29.799
<v Speaker 2>Edward Snowden obviously ended up in Russia. Another Pirate Bay guy,

419
00:21:29.839 --> 00:21:33.599
<v Speaker 2>Frederic Niege, fled to Laos and as of the book's writing,

420
00:21:33.680 --> 00:21:37.799
<v Speaker 2>hadn't been extradited. A Sattishakora found refuge in Cuba despite

421
00:21:37.799 --> 00:21:41.240
<v Speaker 2>a treaty existing due to the unique US Cuba political situation.

422
00:21:42.000 --> 00:21:45.039
<v Speaker 2>But the book specifically warns against thinking Canada is safe.

423
00:21:45.279 --> 00:21:47.359
<v Speaker 2>It uses the Mark Emery case as an example. He

424
00:21:47.400 --> 00:21:50.079
<v Speaker 2>was a Canadian citizen extradited to the US for selling

425
00:21:50.160 --> 00:21:53.200
<v Speaker 2>marijuana seats online to Americans. So the insight is, yeah,

426
00:21:53.279 --> 00:21:55.960
<v Speaker 2>lack of a treaty hubs, but it's no guarantee. Politics

427
00:21:55.960 --> 00:21:58.799
<v Speaker 2>international agreements or just pressure can override it. Fleeing is

428
00:21:58.799 --> 00:21:59.960
<v Speaker 2>a desperate, uncertain measure.

429
00:22:00.160 --> 00:22:03.599
<v Speaker 1>Okay, let's shift back to tech slightly and explore combining

430
00:22:03.640 --> 00:22:06.799
<v Speaker 1>tour with a VPN. This is always a big debate online.

431
00:22:07.000 --> 00:22:10.279
<v Speaker 1>VPN over tour or tour over VPN sounds like they

432
00:22:10.319 --> 00:22:12.160
<v Speaker 1>are pretty significant trade offs either.

433
00:22:11.920 --> 00:22:14.759
<v Speaker 2>Way, There definitely are, and the right choice really depends

434
00:22:14.799 --> 00:22:17.279
<v Speaker 2>on what you're trying to protect against your threat model.

435
00:22:17.359 --> 00:22:20.079
<v Speaker 2>As they say. Okay, so if you do VPN over tour,

436
00:22:20.559 --> 00:22:23.720
<v Speaker 2>that means your connection path is UOA type of VPN

437
00:22:23.839 --> 00:22:27.799
<v Speaker 2>dash tour desh internet. The main advantage here is you

438
00:22:27.880 --> 00:22:30.559
<v Speaker 2>hide the factor you're using tour from your own Internet

439
00:22:30.559 --> 00:22:33.640
<v Speaker 2>service provider, your ISP. They just see encrypted traffic going

440
00:22:33.720 --> 00:22:37.000
<v Speaker 2>to a VPN server. Your VPN provider in this setup

441
00:22:37.160 --> 00:22:41.799
<v Speaker 2>only sees encrypted tour traffic. They don't see your final destination. Downsides, well,

442
00:22:41.839 --> 00:22:44.559
<v Speaker 2>the VPN provider could still be logging your connection times

443
00:22:44.640 --> 00:22:47.279
<v Speaker 2>or other metadata, and this setup isn't useful if you

444
00:22:47.319 --> 00:22:50.920
<v Speaker 2>want to access tour hidden services those dot onion sits. Now.

445
00:22:50.920 --> 00:22:53.839
<v Speaker 2>The other way around tour over VPN, that's U guide

446
00:22:53.880 --> 00:22:57.640
<v Speaker 2>tour desh VPN dash Internet. Here you get more anonymity

447
00:22:57.640 --> 00:23:00.279
<v Speaker 2>from your VPN provider because they only see traffic coming

448
00:23:00.319 --> 00:23:02.720
<v Speaker 2>from a Tour exit node IP, not your real IP.

449
00:23:03.359 --> 00:23:06.039
<v Speaker 2>This setup can also help bypass any censorship or blocks

450
00:23:06.079 --> 00:23:09.119
<v Speaker 2>your ISP might have on connecting to tour directly. Plus,

451
00:23:09.119 --> 00:23:11.559
<v Speaker 2>if your VPN connection suddenly drops, your traffic would then

452
00:23:11.599 --> 00:23:13.920
<v Speaker 2>just fall back to coming directly from Tour, not exposure

453
00:23:13.920 --> 00:23:16.880
<v Speaker 2>real IP. The downsides here though, your ISP will see

454
00:23:16.880 --> 00:23:19.599
<v Speaker 2>that you're connecting to the Tour network and crucially you

455
00:23:19.640 --> 00:23:23.559
<v Speaker 2>cannot visit hidden dot onion services with this configuration. Why

456
00:23:23.920 --> 00:23:26.440
<v Speaker 2>because the final node making the connection to the Internet

457
00:23:26.759 --> 00:23:29.200
<v Speaker 2>is your VPN server and it's not part of the

458
00:23:29.200 --> 00:23:33.440
<v Speaker 2>Tour network needed to resolve dot onion addresses. So yeah,

459
00:23:33.440 --> 00:23:35.880
<v Speaker 2>the core insight is that each setup changes who sees

460
00:23:35.880 --> 00:23:38.079
<v Speaker 2>what part of your connection and affects what parts of

461
00:23:38.079 --> 00:23:39.400
<v Speaker 2>the Internet you can actually reach.

462
00:23:39.640 --> 00:23:42.400
<v Speaker 1>It's definitely a complex choice, and like the source says,

463
00:23:42.559 --> 00:23:44.720
<v Speaker 1>it depends on your specific needs and who you trust

464
00:23:44.799 --> 00:23:49.279
<v Speaker 1>less basically, but regardless, the core advice remains never enter

465
00:23:49.359 --> 00:23:52.880
<v Speaker 1>identifying info. It also strongly recommends using search engines that

466
00:23:52.920 --> 00:23:55.319
<v Speaker 1>don't track you, like duck dot Go, which works on

467
00:23:55.359 --> 00:23:57.680
<v Speaker 1>the regular Clearnet and also have a dot onion eddressor

468
00:23:57.720 --> 00:24:01.559
<v Speaker 1>start page advising strongly against us in Google for anything sensitive.

469
00:24:01.839 --> 00:24:04.160
<v Speaker 1>And when you're choosing a VPN, the protocol it uses

470
00:24:04.200 --> 00:24:06.400
<v Speaker 1>matters too, right, what's the gold standard there?

471
00:24:06.559 --> 00:24:10.160
<v Speaker 2>Yes, protocol choice is huge. OpenVPN is widely considered the

472
00:24:10.200 --> 00:24:14.000
<v Speaker 2>best choice currently. It uses strong modern encryption, typically one

473
00:24:14.039 --> 00:24:16.359
<v Speaker 2>hundred sixty to two hundred and fifty six bit, and

474
00:24:16.440 --> 00:24:20.440
<v Speaker 2>relies on digital certificates for authentication. It's open source, which

475
00:24:20.480 --> 00:24:24.200
<v Speaker 2>means it's been heavily scrutinized by security experts. Definitely preferred

476
00:24:24.200 --> 00:24:26.599
<v Speaker 2>over older protocols like PPTP, which is known to be

477
00:24:26.599 --> 00:24:29.039
<v Speaker 2>weak only one hundred and twenty eight bit, or even

478
00:24:29.200 --> 00:24:32.319
<v Speaker 2>l two tpip sec. The source raises concerns that lttpi

479
00:24:32.400 --> 00:24:35.440
<v Speaker 2>sec might have been deliberately weakened or compromised by agencies

480
00:24:35.480 --> 00:24:38.359
<v Speaker 2>like the NSA, although that's debated. The key is choosing

481
00:24:38.400 --> 00:24:42.480
<v Speaker 2>protocols known for strong cryptography, transparency, open source helps, and

482
00:24:42.519 --> 00:24:43.400
<v Speaker 2>a good track record.

483
00:24:43.599 --> 00:24:48.480
<v Speaker 1>Okay, Open VPN preferred now for Windows users. Specifically, the

484
00:24:48.559 --> 00:24:51.960
<v Speaker 1>source gets into a really complex setup. It involves virtual box,

485
00:24:52.160 --> 00:24:55.440
<v Speaker 1>something called tour Expert, and a Windows only program called

486
00:24:55.480 --> 00:24:58.599
<v Speaker 1>Tortilla can you give us just the high level idea

487
00:24:58.599 --> 00:25:01.400
<v Speaker 1>of what this complex stance is. It sounds pretty involved.

488
00:25:01.440 --> 00:25:03.960
<v Speaker 2>It is involved, Yeah, definitely an advanced technique. At a

489
00:25:04.039 --> 00:25:07.000
<v Speaker 2>high level, this kind of setup is about creating multiple

490
00:25:07.400 --> 00:25:11.519
<v Speaker 2>nested layers of anonymity. You're essentially running tor and potentially

491
00:25:11.559 --> 00:25:15.240
<v Speaker 2>a VPN inside a virtual machine environment on your Windows PC.

492
00:25:15.759 --> 00:25:18.400
<v Speaker 2>Tools like Tortilla help force all Internet traffic from that

493
00:25:18.480 --> 00:25:21.759
<v Speaker 2>virtual machine through the tour network, preventing leaks. You can

494
00:25:21.799 --> 00:25:24.519
<v Speaker 2>even stack them, like the book mentions, maybe VPN toor

495
00:25:24.599 --> 00:25:27.920
<v Speaker 2>netwur and another VPN torgan creating layer upon layer. The

496
00:25:27.960 --> 00:25:32.359
<v Speaker 2>goal is extreme compartmentalization and making traffic analysis incredibly difficult.

497
00:25:32.640 --> 00:25:35.200
<v Speaker 2>The inside is that for really high stake situations, some

498
00:25:35.400 --> 00:25:38.680
<v Speaker 2>users are willing to sacrifice significant speed and simplicity for

499
00:25:38.759 --> 00:25:40.440
<v Speaker 2>these extra layers of obfuscation.

500
00:25:40.680 --> 00:25:45.559
<v Speaker 1>Wow, layers upon layers sounds slow, but potentially very secure

501
00:25:45.559 --> 00:25:49.160
<v Speaker 1>if done right. Shifting slightly again, the book covers a

502
00:25:49.200 --> 00:25:52.960
<v Speaker 1>more subtle security measure, simply disabling the show online status

503
00:25:53.000 --> 00:25:56.319
<v Speaker 1>feature on forums or chat platforms. Why is that recommended?

504
00:25:56.839 --> 00:25:59.599
<v Speaker 2>It seems small, right, Yeah, But the inside is that

505
00:25:59.720 --> 00:26:02.640
<v Speaker 2>even tiny bits of information can be pieced together if

506
00:26:02.680 --> 00:26:06.920
<v Speaker 2>you disable your online indicator. It prevents observers, maybe law

507
00:26:07.000 --> 00:26:10.920
<v Speaker 2>enforcement monitoring a forum, from easily correlating your login and

508
00:26:11.000 --> 00:26:13.799
<v Speaker 2>logout times with other potential data points like, oh, this

509
00:26:13.920 --> 00:26:16.079
<v Speaker 2>user logged off right after we saw their car leave

510
00:26:16.119 --> 00:26:19.559
<v Speaker 2>the house, or they're always online between these specific hours.

511
00:26:19.960 --> 00:26:23.079
<v Speaker 2>These patterns, even seemingly harmless ones, can become pieces of

512
00:26:23.119 --> 00:26:26.799
<v Speaker 2>circumstantial evidence in a larger investigation. It removes one small

513
00:26:26.880 --> 00:26:27.920
<v Speaker 2>data point they can track.

514
00:26:28.039 --> 00:26:30.359
<v Speaker 1>Okay, it makes sense deny them any data you can

515
00:26:30.799 --> 00:26:33.599
<v Speaker 1>now beyond your online activity. What about the files you

516
00:26:33.640 --> 00:26:37.319
<v Speaker 1>download getting software like tour itself or Tails. The source

517
00:26:37.319 --> 00:26:40.880
<v Speaker 1>stresses downloading only from the official homepages tourproject dot org,

518
00:26:40.920 --> 00:26:43.640
<v Speaker 1>tails dot Boom dot org because mirrors can be malicious

519
00:26:44.000 --> 00:26:45.920
<v Speaker 1>and there are risks of man in the middle attacks

520
00:26:45.920 --> 00:26:48.319
<v Speaker 1>intercepting downloads. But how do you actually verify that the

521
00:26:48.359 --> 00:26:50.359
<v Speaker 1>file you download it is the real deal, that it

522
00:26:50.400 --> 00:26:51.319
<v Speaker 1>hasn't been tampered with.

523
00:26:51.559 --> 00:26:54.839
<v Speaker 2>That's a really critical step. Yeah, verification. The core idea

524
00:26:54.920 --> 00:26:57.880
<v Speaker 2>is to mathematically check that the file you have is

525
00:26:57.960 --> 00:27:00.599
<v Speaker 2>exactly the same one that developers intend you to have,

526
00:27:01.200 --> 00:27:05.039
<v Speaker 2>like checking a digital tamper proof seal. The book explains

527
00:27:05.039 --> 00:27:08.799
<v Speaker 2>the process using gin OPG no Privacy Guard, which is

528
00:27:08.799 --> 00:27:12.720
<v Speaker 2>an implementation of PGP. Essentially, you download the software file itself,

529
00:27:12.759 --> 00:27:16.680
<v Speaker 2>but you also download a separate small signature file dot

530
00:27:16.720 --> 00:27:19.640
<v Speaker 2>ASS or dot SIG provided by the developers, and you

531
00:27:19.680 --> 00:27:24.000
<v Speaker 2>need the developer's public pgpkey. You then use GENOPG along

532
00:27:24.000 --> 00:27:26.279
<v Speaker 2>with the developer's public key to check if the signature

533
00:27:26.279 --> 00:27:28.920
<v Speaker 2>file correctly matches the main software file you download it.

534
00:27:29.039 --> 00:27:31.519
<v Speaker 2>If the check passes, GENOPG will tell you the signature

535
00:27:31.640 --> 00:27:34.319
<v Speaker 2>is good. That confirms the files authentic and hasn't been

536
00:27:34.319 --> 00:27:36.880
<v Speaker 2>modified since the developer signed it. If it fails to

537
00:27:36.960 --> 00:27:40.480
<v Speaker 2>lead the download immediately, something's wrong. It's crucial for ensuring

538
00:27:40.519 --> 00:27:43.319
<v Speaker 2>you're not installing malware disguised as legitimate software.

539
00:27:43.400 --> 00:27:46.640
<v Speaker 1>Right checking the digital seal, got it? Okay? Let's talk

540
00:27:46.680 --> 00:27:49.960
<v Speaker 1>anonymous communication. The bill brings up Torchat. What is that

541
00:27:50.079 --> 00:27:51.680
<v Speaker 1>and how does it boost privacy?

542
00:27:52.039 --> 00:27:56.519
<v Speaker 2>Torchat is pretty interesting. It's a decentralized instant messenger. Decentralized

543
00:27:56.519 --> 00:27:59.720
<v Speaker 2>means there's no central server controlling everything. It works by

544
00:27:59.759 --> 00:28:04.079
<v Speaker 2>using tour hidden services. Those service any addresses again for

545
00:28:04.079 --> 00:28:07.319
<v Speaker 2>all its communication. Each tor Chat user gets a unique

546
00:28:07.440 --> 00:28:11.240
<v Speaker 2>sixteen character ID, which is basically their dot onion address

547
00:28:11.279 --> 00:28:14.680
<v Speaker 2>on the Tour network. When you chat or send files,

548
00:28:15.000 --> 00:28:18.440
<v Speaker 2>it's all done peer to peer, encrypted directly between users

549
00:28:18.519 --> 00:28:21.920
<v Speaker 2>hidden services within Tour. The key insight is that because

550
00:28:21.920 --> 00:28:25.319
<v Speaker 2>it operates entirely within tours Hidden Service framework, it offers

551
00:28:25.319 --> 00:28:28.160
<v Speaker 2>a pretty high level of anonymity for messaging, much more

552
00:28:28.160 --> 00:28:30.680
<v Speaker 2>so than traditional messengers that rely on central servers and

553
00:28:30.759 --> 00:28:34.759
<v Speaker 2>might log data. It's available for Windows, Linux, Mac, though

554
00:28:34.799 --> 00:28:37.039
<v Speaker 2>the book notes it might not work correctly inside TAILS

555
00:28:37.039 --> 00:28:39.400
<v Speaker 2>itself currently, so you typically run it on your main

556
00:28:39.480 --> 00:28:40.920
<v Speaker 2>os if secured.

557
00:28:40.519 --> 00:28:43.319
<v Speaker 1>Properly interesting peer to peer over hidden services. What about

558
00:28:43.400 --> 00:28:46.559
<v Speaker 1>anonymous money? The book talks about bitcoin, specifically getting it

559
00:28:46.640 --> 00:28:50.119
<v Speaker 1>and transferring it anonymously. How can you even acquire bitcoin

560
00:28:50.160 --> 00:28:53.200
<v Speaker 1>without leaving a trace back to your real identity? That

561
00:28:53.240 --> 00:28:54.359
<v Speaker 1>seems like the first hurdle.

562
00:28:54.599 --> 00:28:57.720
<v Speaker 2>It is a major hurdle. Getting truly anonymous bitcoin is

563
00:28:57.759 --> 00:29:01.480
<v Speaker 2>tough these days. Most big online and exchanges require extensive

564
00:29:01.480 --> 00:29:05.240
<v Speaker 2>ID verification, so that's usually out for anonymity. The book

565
00:29:05.279 --> 00:29:08.400
<v Speaker 2>suggests alternatives like local bitcoins, where you might be able

566
00:29:08.480 --> 00:29:11.839
<v Speaker 2>to arrange cash in person trades or maybe cash deposits

567
00:29:11.839 --> 00:29:15.680
<v Speaker 2>at a bank, though even that carries risks. Bitcoin ATMs

568
00:29:15.720 --> 00:29:17.880
<v Speaker 2>exist where you can feed in cash, but you have

569
00:29:17.960 --> 00:29:20.920
<v Speaker 2>to watch out for surveillance cameras around the atm itself.

570
00:29:21.480 --> 00:29:24.240
<v Speaker 2>Some ATMs can generate a paper wallet for you right there.

571
00:29:24.839 --> 00:29:27.400
<v Speaker 2>You might also find sellers on places like Craigslist for

572
00:29:27.480 --> 00:29:30.759
<v Speaker 2>in person cash trades. And then there's mining your own bitcoins,

573
00:29:30.799 --> 00:29:35.240
<v Speaker 2>which creates completely new, untated coins, but that requires significant

574
00:29:35.279 --> 00:29:38.599
<v Speaker 2>technical know how and resources. Now, the insight really is

575
00:29:38.640 --> 00:29:41.680
<v Speaker 2>that the initial acquisition point is often the weakest link

576
00:29:41.680 --> 00:29:44.000
<v Speaker 2>in the chain for maintaining anonymity with bitcoin.

577
00:29:44.519 --> 00:29:46.640
<v Speaker 1>Okay, so getting them anonymously as hard. Let's say you

578
00:29:46.640 --> 00:29:49.160
<v Speaker 1>manage it. How do you then transfer those bitcoins in

579
00:29:49.160 --> 00:29:52.000
<v Speaker 1>a way that obscures the trail. Bitcoin transactions are public

580
00:29:52.000 --> 00:29:53.720
<v Speaker 1>on the blockchain, right they are public?

581
00:29:53.880 --> 00:29:57.319
<v Speaker 2>Yes, that's the challenge. The book outlines a few methods

582
00:29:57.319 --> 00:29:59.400
<v Speaker 2>people use to try and break that traceable link on

583
00:29:59.440 --> 00:30:03.279
<v Speaker 2>the blockchain. One common method is using mixers or tumblers,

584
00:30:03.319 --> 00:30:07.000
<v Speaker 2>like the service bitcoin Fog mentioned. These services take your bitcoins,

585
00:30:07.279 --> 00:30:09.319
<v Speaker 2>mix them up in a large pool with bitcoins from

586
00:30:09.319 --> 00:30:11.960
<v Speaker 2>many other users, and then send out the equivalent amount

587
00:30:12.440 --> 00:30:14.839
<v Speaker 2>minus a small fee usually one three percent, to a

588
00:30:14.880 --> 00:30:17.480
<v Speaker 2>new address You specify. The idea is to break the

589
00:30:17.519 --> 00:30:19.839
<v Speaker 2>direct connection between the coins you sent in and the

590
00:30:19.839 --> 00:30:22.319
<v Speaker 2>coins that come out. The book stress is sending the

591
00:30:22.359 --> 00:30:25.279
<v Speaker 2>mixed coins to a brand new wallet address afterwards, or

592
00:30:25.319 --> 00:30:28.400
<v Speaker 2>directly to the final recipient, not back to your original wallet.

593
00:30:28.720 --> 00:30:32.359
<v Speaker 2>Another method mentioned was blockchain dot info's old send shared feature,

594
00:30:32.880 --> 00:30:36.039
<v Speaker 2>which try to match up users making equal value transactions

595
00:30:36.079 --> 00:30:39.279
<v Speaker 2>and essentially swap the destinations. A intends to send to B,

596
00:30:39.720 --> 00:30:41.960
<v Speaker 2>X intends to send to Y, but the service makes

597
00:30:42.079 --> 00:30:44.359
<v Speaker 2>a send to Y and X send to B. This

598
00:30:44.480 --> 00:30:47.400
<v Speaker 2>also aimed to break the chain. And then there's shared

599
00:30:47.480 --> 00:30:51.119
<v Speaker 2>coin or coin join protocols. These involve multiple users pooling

600
00:30:51.160 --> 00:30:53.839
<v Speaker 2>their inputs and outputs into a single larger transaction. This

601
00:30:53.960 --> 00:30:57.240
<v Speaker 2>makes it much harder for outside observers to definitively link

602
00:30:57.279 --> 00:31:01.559
<v Speaker 2>specific inputs to specific outputs within that transaction. The server

603
00:31:01.680 --> 00:31:04.920
<v Speaker 2>facilitating it supposedly can't steal the coins, but some link

604
00:31:04.960 --> 00:31:08.880
<v Speaker 2>between input and destination might still remain. The core insight

605
00:31:09.000 --> 00:31:10.880
<v Speaker 2>for all these is that you're trying to add noise

606
00:31:10.920 --> 00:31:14.640
<v Speaker 2>and complexity to the public blockchain record, making it harder,

607
00:31:14.680 --> 00:31:18.279
<v Speaker 2>though perhaps not impossible, to follow the money. Each method

608
00:31:18.319 --> 00:31:22.279
<v Speaker 2>has trade offs in terms of trust, fees and effectiveness.

609
00:31:21.839 --> 00:31:25.359
<v Speaker 1>Mixing, swapping, joining lots of techniques to try and muddy

610
00:31:25.400 --> 00:31:28.519
<v Speaker 1>the waters. Okay, we've covered a ton of software, networking,

611
00:31:28.559 --> 00:31:31.160
<v Speaker 1>even crypto. You might start feeling pretty secure with all that,

612
00:31:31.519 --> 00:31:34.319
<v Speaker 1>but then the book hits you with physical vulnerabilities, and

613
00:31:34.359 --> 00:31:37.759
<v Speaker 1>this stuff is unsettling. It mentions the US government being

614
00:31:37.759 --> 00:31:41.240
<v Speaker 1>the largest buyer of malware, funding hackers for zero day exploits.

615
00:31:41.480 --> 00:31:44.079
<v Speaker 1>Those are flaws nobody else knows about yet, right, making

616
00:31:44.119 --> 00:31:46.599
<v Speaker 1>them super effective exactly.

617
00:31:46.880 --> 00:31:49.839
<v Speaker 2>Zero days are vulnerabilities that the software vendor themselves doesn't

618
00:31:49.839 --> 00:31:52.799
<v Speaker 2>even know about yet, so there's no patch available. They're

619
00:31:52.839 --> 00:31:57.519
<v Speaker 2>incredibly valuable and potent for attackers, including governments, and this

620
00:31:57.599 --> 00:32:00.720
<v Speaker 2>leads into some really sobering truths about the fiss devices

621
00:32:00.720 --> 00:32:03.759
<v Speaker 2>we use every day. The insight here is profound. Your

622
00:32:03.799 --> 00:32:06.640
<v Speaker 2>privacy fight isn't just online, it's in the physical world,

623
00:32:06.839 --> 00:32:09.759
<v Speaker 2>with the hardware itself, things like the built in microphone

624
00:32:09.799 --> 00:32:13.079
<v Speaker 2>and camera on your laptop. The book echoes warnings like

625
00:32:13.160 --> 00:32:17.359
<v Speaker 2>John McAfee's famous advice to physically cover your webcams. Why

626
00:32:17.880 --> 00:32:21.160
<v Speaker 2>because it can potentially be activated remotely by sophisticated malware

627
00:32:21.200 --> 00:32:24.839
<v Speaker 2>without the indicator light, even turning on unplug external webcams

628
00:32:24.839 --> 00:32:28.799
<v Speaker 2>when not in use. Then there's the FBI's keystroke logging software,

629
00:32:29.000 --> 00:32:32.960
<v Speaker 2>reportedly called Magic Lantern. Described as a trojan horse, it

630
00:32:33.000 --> 00:32:36.880
<v Speaker 2>could potentially capture everything you type, including crucially your PGP

631
00:32:37.119 --> 00:32:40.119
<v Speaker 2>pass phrases or disc encryption passwords as you type them.

632
00:32:40.119 --> 00:32:42.319
<v Speaker 2>It may be the most chilling cell phones. The book

633
00:32:42.359 --> 00:32:45.000
<v Speaker 2>describes them as potential roving bugs that can be remotely

634
00:32:45.039 --> 00:32:47.359
<v Speaker 2>activated to listen into their microphone even when the phone

635
00:32:47.359 --> 00:32:48.839
<v Speaker 2>appears to be completely turned off.

636
00:32:49.160 --> 00:32:53.359
<v Speaker 1>Wow, roving bugs cover the camera. Magic Lantern. That really

637
00:32:53.400 --> 00:32:55.880
<v Speaker 1>shatters the illusion that turning something off means is truly

638
00:32:55.920 --> 00:32:58.519
<v Speaker 1>off or safe. And it gets even wilder. The book

639
00:32:58.559 --> 00:33:01.519
<v Speaker 1>talks about monitoring using an antenna. How does that even work?

640
00:33:01.680 --> 00:33:03.240
<v Speaker 1>And what about smart meters?

641
00:33:03.559 --> 00:33:07.920
<v Speaker 2>Yeah, this is deep stuff. Electromagnetic ease dropping turns out

642
00:33:08.000 --> 00:33:12.680
<v Speaker 2>electronic devices emit faint electromagnetic waves as they operate. Specialized

643
00:33:12.680 --> 00:33:15.559
<v Speaker 2>equipment can potentially pick up these faint signals from things

644
00:33:15.599 --> 00:33:18.799
<v Speaker 2>like your wired or wireless keyboard, your mouse, even your

645
00:33:18.839 --> 00:33:22.279
<v Speaker 2>monitor screen from a distance, and by analyzing these signals,

646
00:33:22.480 --> 00:33:25.440
<v Speaker 2>it might be possible to reconstruct your keystrokes or even

647
00:33:25.440 --> 00:33:27.759
<v Speaker 2>get a fuzzy image of what's on your screen. It's

648
00:33:27.799 --> 00:33:31.319
<v Speaker 2>often called tempest monitoring and smart meters, the ones replacing

649
00:33:31.319 --> 00:33:35.039
<v Speaker 2>older electrical meters on houses. Many of them apparently broadcast

650
00:33:35.119 --> 00:33:38.880
<v Speaker 2>your detailed power consumption data, sometimes patterns of usage in

651
00:33:38.960 --> 00:33:42.720
<v Speaker 2>plaintext wirelessly. The book claims this signal can sometimes be

652
00:33:42.759 --> 00:33:45.240
<v Speaker 2>picked up from up to three hundred meters away, potentially

653
00:33:45.240 --> 00:33:48.119
<v Speaker 2>revealing when you're home, when you sleep, what appliances you're using.

654
00:33:48.440 --> 00:33:52.039
<v Speaker 2>The insight is just staggering. Virtually everything digital creates some

655
00:33:52.119 --> 00:33:55.559
<v Speaker 2>kind of signal and emission, and those emissions can potentially

656
00:33:55.599 --> 00:33:57.119
<v Speaker 2>be intercepted and interpreted.

657
00:33:57.480 --> 00:34:01.839
<v Speaker 1>Okay, reading keyboards from AFAR, smart meters, broadcasting habits. How

658
00:34:01.839 --> 00:34:04.200
<v Speaker 1>do you even begin to defend against that level of

659
00:34:04.200 --> 00:34:05.400
<v Speaker 1>physical eavesdropping?

660
00:34:05.640 --> 00:34:09.360
<v Speaker 2>Well, the defenses get pretty specialized too. For the software side,

661
00:34:09.440 --> 00:34:14.199
<v Speaker 2>the general advice holds keep disabling JavaScript, maybe move away

662
00:34:14.199 --> 00:34:17.599
<v Speaker 2>from closed source operating systems like Windows or Mac towards

663
00:34:17.599 --> 00:34:22.320
<v Speaker 2>open source Linux distributions. Running your OS inside virtual machines

664
00:34:22.400 --> 00:34:26.000
<v Speaker 2>adds another layer. Regular hard dry formatting. Even flashing your

665
00:34:26.000 --> 00:34:29.840
<v Speaker 2>computer's bios chip firmware can help against persistent malware. For

666
00:34:29.920 --> 00:34:34.079
<v Speaker 2>the electromagnetic eaves dropping, though, that requires physical shielding. The

667
00:34:34.119 --> 00:34:37.360
<v Speaker 2>book mentions things like special paints like y shield paint

668
00:34:37.599 --> 00:34:41.840
<v Speaker 2>that contain conductive materials to block electromagnetic waves, or using

669
00:34:41.840 --> 00:34:45.519
<v Speaker 2>fabrics woven with metallic threads to create shielded enclosures or clothing.

670
00:34:45.960 --> 00:34:48.440
<v Speaker 2>It's definitely entering the realm of serious paranoia for most,

671
00:34:48.719 --> 00:34:50.239
<v Speaker 2>but the thread is technically.

672
00:34:49.920 --> 00:34:52.559
<v Speaker 1>Real shielding paint. Okay, so taking it down a notch

673
00:34:52.559 --> 00:34:56.119
<v Speaker 1>from antennas, but still pretty physical and scary. Cold boot

674
00:34:56.159 --> 00:35:00.280
<v Speaker 1>attacks and extracting data from unencrypted wham, what's the deal

675
00:35:00.280 --> 00:35:00.559
<v Speaker 1>with that?

676
00:35:00.960 --> 00:35:04.679
<v Speaker 2>Right? Cold boot attacks This exploits a property of random

677
00:35:04.679 --> 00:35:08.519
<v Speaker 2>access memory, where your computer temporarily stores data it's actively

678
00:35:08.559 --> 00:35:12.239
<v Speaker 2>working on. Normally, RAM is volatile, meaning the data disappears

679
00:35:12.239 --> 00:35:16.079
<v Speaker 2>almost instantly when the powers cut. However, the key insight

680
00:35:16.119 --> 00:35:18.719
<v Speaker 2>from research like a famous two thousand and eight Princeton

681
00:35:18.800 --> 00:35:21.519
<v Speaker 2>study is that if you cut the power abruptly, like

682
00:35:21.599 --> 00:35:24.079
<v Speaker 2>pulling the plug or battery, that data in the RAM

683
00:35:24.159 --> 00:35:28.440
<v Speaker 2>chips doesn't vanish instantly. It decays over seconds or even minutes,

684
00:35:28.800 --> 00:35:31.760
<v Speaker 2>especially if the RAM chips are cooled down rapidly. Hence

685
00:35:31.960 --> 00:35:36.000
<v Speaker 2>cold boot. That Princeton study show they could successfully reboot

686
00:35:36.000 --> 00:35:39.039
<v Speaker 2>a machine quickly or physically remove the ramsticks and put

687
00:35:39.039 --> 00:35:41.920
<v Speaker 2>them in another machine and still recover sensitive data that

688
00:35:42.000 --> 00:35:45.199
<v Speaker 2>was lingering in RAM before it completely faded. This included

689
00:35:45.280 --> 00:35:49.280
<v Speaker 2>encryption keys for full disc encryption systems like BitLocker, file Vault,

690
00:35:49.480 --> 00:35:50.679
<v Speaker 2>and the older two CRYPT.

691
00:35:50.920 --> 00:35:52.840
<v Speaker 1>So even if my hard drive is fully encrypted, the

692
00:35:52.920 --> 00:35:55.639
<v Speaker 1>keys needed to unlock it might be sitting temporarily exposed

693
00:35:55.639 --> 00:35:57.800
<v Speaker 1>in RAM while the computer is on, and someone could

694
00:35:57.800 --> 00:35:59.760
<v Speaker 1>potentially grab them right after shutdown.

695
00:36:00.079 --> 00:36:03.639
<v Speaker 2>Exactly that's the vulnerability. The encryption protects the data at

696
00:36:03.679 --> 00:36:06.400
<v Speaker 2>rest on the drive, but the key has to be

697
00:36:06.440 --> 00:36:08.960
<v Speaker 2>loaded into RAM for the system to function while it's running.

698
00:36:09.679 --> 00:36:13.920
<v Speaker 2>True Crypt's own documentation acknowledges this vulnerability, especially for encrypting

699
00:36:13.920 --> 00:36:16.840
<v Speaker 2>the main system volume where the operating system lives. Because

700
00:36:16.840 --> 00:36:19.159
<v Speaker 2>of the master encryption keys might not be reliably white

701
00:36:19.199 --> 00:36:22.760
<v Speaker 2>from RAM during a normal shutdown process. Now there's some

702
00:36:22.800 --> 00:36:25.360
<v Speaker 2>debate whether newer types of RAM like DDR three and

703
00:36:25.440 --> 00:36:29.119
<v Speaker 2>later have faster decay times, making these attacks harder, but

704
00:36:29.159 --> 00:36:34.199
<v Speaker 2>the risk isn't zero, so practical mitigation first, always try

705
00:36:34.199 --> 00:36:36.519
<v Speaker 2>to shut down your computer properly through the operating system,

706
00:36:36.559 --> 00:36:38.119
<v Speaker 2>don't just pull the plug. If you can avoid it

707
00:36:38.599 --> 00:36:42.400
<v Speaker 2>use newer RAM DDR three or later if possible. Maybe

708
00:36:42.400 --> 00:36:45.639
<v Speaker 2>you avoid storing extremely sensitive unencrypted data directly on an

709
00:36:45.719 --> 00:36:49.280
<v Speaker 2>encrypted system volume, uses separate encrypted container or partition for

710
00:36:49.360 --> 00:36:52.320
<v Speaker 2>that for laptops. If there's an immediate physical threat, pulling

711
00:36:52.320 --> 00:36:55.320
<v Speaker 2>the battery can help cut power instantly, potentially reducing the

712
00:36:55.320 --> 00:36:57.559
<v Speaker 2>window for RAM recovery compared to a slow shut down.

713
00:36:57.840 --> 00:37:01.000
<v Speaker 2>And then there's basic physical security using computer case locks.

714
00:37:01.039 --> 00:37:03.599
<v Speaker 2>Even physically bolting the computer case to a desk or

715
00:37:03.679 --> 00:37:06.639
<v Speaker 2>floor can slow down an attacker trying to quickly access

716
00:37:06.639 --> 00:37:11.599
<v Speaker 2>the ramsticks. The overall insight remains. Data protection isn't just software.

717
00:37:11.880 --> 00:37:16.039
<v Speaker 2>It's understanding and controlling every potential access point digital, physical,

718
00:37:16.039 --> 00:37:17.360
<v Speaker 2>and even electromagnetic.

719
00:37:17.559 --> 00:37:20.159
<v Speaker 1>It is absolutely clear that while many of these threats

720
00:37:20.239 --> 00:37:23.079
<v Speaker 1>might seem extreme, just understanding that they exist is the

721
00:37:23.119 --> 00:37:28.199
<v Speaker 1>crucial first step towards actually protecting yourself. It's about awareness. Okay,

722
00:37:28.280 --> 00:37:30.480
<v Speaker 1>So let's try and wrap this up to summarize our

723
00:37:30.519 --> 00:37:34.800
<v Speaker 1>deep dive today. Getting to true online anonymity, real robust security.

724
00:37:35.199 --> 00:37:39.239
<v Speaker 1>It demands this relentless, multi layered, incredibly vigilant approach. You

725
00:37:39.239 --> 00:37:43.280
<v Speaker 1>have to consider software, hardware, physical security, and the human factor.

726
00:37:43.320 --> 00:37:45.760
<v Speaker 1>It's really a full spectrum defense posture.

727
00:37:45.880 --> 00:37:49.159
<v Speaker 2>It really is. But the flip side is this vigilance.

728
00:37:49.800 --> 00:37:53.000
<v Speaker 2>When you combine it with properly implemented strong cryptography and

729
00:37:53.000 --> 00:37:56.360
<v Speaker 2>anonymity tools, it can be remarkably powerful. Think about the

730
00:37:56.360 --> 00:37:59.480
<v Speaker 2>example of cryptolock or ransomware mentioned in the source you

731
00:37:59.559 --> 00:38:04.000
<v Speaker 2>strong twenty forty eight bit RSA encryption. Effectively, its operators

732
00:38:04.000 --> 00:38:07.559
<v Speaker 2>managed to hold countless computer systems hostage, collecting millions of

733
00:38:07.599 --> 00:38:10.199
<v Speaker 2>dollars in bitcoin that was very difficult to trace. They

734
00:38:10.239 --> 00:38:12.760
<v Speaker 2>even forced police departments and major companies to pay their

735
00:38:12.840 --> 00:38:15.880
<v Speaker 2>ransom because the encryption is just too strong to break. Realistically,

736
00:38:16.480 --> 00:38:19.119
<v Speaker 2>it demonstrates that when these tools are used correctly, they

737
00:38:19.159 --> 00:38:23.400
<v Speaker 2>do work. They provide real security, real anonymity, even against

738
00:38:23.400 --> 00:38:26.760
<v Speaker 2>determined adversaries. The key insight is that if applied correctly,

739
00:38:26.800 --> 00:38:28.599
<v Speaker 2>these technologies are not easily defeated.

740
00:38:28.719 --> 00:38:32.440
<v Speaker 1>That's a powerful point. The tools work if used right. Okay.

741
00:38:32.599 --> 00:38:35.639
<v Speaker 1>To leave our listeners with a few final practical recommendations

742
00:38:35.719 --> 00:38:38.800
<v Speaker 1>drawn from the source. Never ever leave computers used for

743
00:38:38.920 --> 00:38:43.320
<v Speaker 1>sensitive activities unattended, even for a moment. Physical access is king.

744
00:38:43.920 --> 00:38:47.559
<v Speaker 1>Don't tell family members unnecessary details about your online activities.

745
00:38:47.599 --> 00:38:50.400
<v Speaker 1>It protects them from potential questioning or pressure if something

746
00:38:50.440 --> 00:38:53.960
<v Speaker 1>goes wrong. Ignorance can be bliss and safety for them.

747
00:38:54.239 --> 00:38:57.280
<v Speaker 1>Regularly check that your security layers are actually working. VPNs

748
00:38:57.320 --> 00:39:01.639
<v Speaker 1>can drop, configurations, can change, verify, And finally, a mantra

749
00:39:01.679 --> 00:39:06.599
<v Speaker 1>we've heard before but bears repeating, always always use unique, strong,

750
00:39:06.639 --> 00:39:10.519
<v Speaker 1>and ideally non identifiable passwords for every single online account.

751
00:39:10.719 --> 00:39:12.079
<v Speaker 1>Password managers are your friend.

752
00:39:12.079 --> 00:39:15.559
<v Speaker 2>Here absolutely all great points. So maybe the final thought

753
00:39:15.559 --> 00:39:18.280
<v Speaker 2>to leave everyone mulling over is this, in a world

754
00:39:18.320 --> 00:39:21.440
<v Speaker 2>where our digital traces seem almost unavoidable, where convenience often

755
00:39:21.480 --> 00:39:25.119
<v Speaker 2>clashes with privacy, how do you truly balance that relentless

756
00:39:25.119 --> 00:39:29.480
<v Speaker 2>pursuit of absolute privacy with just the practicalities and conveniences

757
00:39:29.519 --> 00:39:31.960
<v Speaker 2>of living a modern digital life. Where do you draw

758
00:39:32.000 --> 00:39:32.480
<v Speaker 2>the line