OM DETTA AVSNITT
A federal case involving a GrapheneOS phone wipe during an airport search raises a bigger question for privacy-minded users: can using strong mobile security features be treated as evidence of criminal intent? Tom and Scott break down what happened, why border searches are different, and what this could mean for secure phones and everyday privacy.
Tom and Scott also discuss duress codes, realistic travel threat models, and Scott’s Digital Legacy Tree update.
** Links mentioned on the show **
TechSpot — US prosecutors charge Atlanta man after GrapheneOS phone wipes itself during airport search https://www.techspot.com/news/113236-us-prosecutors-charge-atlanta-man-after-grapheneos-phone.html
GrapheneOS project https://grapheneos.org/
EFF — Border searches https://www.eff.org/issues/border-searches
Help Review The Digital Legacy Tree (upcoming book by Scott Wright)
To volunteer, share your story, or suggest ideas that may help others facing digital legacy challenges, visit:
https://securityperspectives.com/digital-legacy-tools
** Watch this episode on YouTube **
** Become a Shared Security Supporter **
Get exclusive access to bonus episodes, listen to new episodes before they are released, receive a monthly shout-out on the show, and get a discount code for 15% off merch at the Shared Security store. Become a supporter today by going to our YouTube channel's membership section: https://www.youtube.com/channel/UCg9CCDIYkDDqwEZ3UYaxjnA/join
** Thank you to our sponsors! **
Guardsquare
Special thanks to Guardsquare for sponsoring this episode! Guardsquare is the leader in mobile application security, with multi-layered protection for your Android and iOS apps. Learn more at Guardsquare.com.
SLNT
Visit https://slnt.com to check out SLNT's amazing line of Faraday bags and other products built to protect your privacy. As a listener of this podcast you receive 10% off your order at checkout using discount code "sharedsecurity".
** Subscribe and follow the podcast **
Subscribe on YouTube: https://www.youtube.com/c/SharedSecurityPodcast
Follow us on Bluesky: https://bsky.app/profile/sharedsecurity.bsky.social
Follow us on Mastodon: https://infosec.exchange/@sharedsecurity
Join us on Reddit: https://www.reddit.com/r/SharedSecurityShow/
Visit our website: https://sharedsecurity.net
Subscribe on your favorite podcast app: https://sharedsecurity.net/subscribe
Sign-up for our email newsletter to receive updates about the podcast, contest announcements, and special offers from our sponsors: https://shared-security.beehiiv.com/subscribe
Leave us a rating and review: https://ratethispodcast.com/sharedsecurity
Contact us: https://sharedsecurity.net/contact
Special thanks to Guardsquare for sponsoring this episode! Guardsquare is the leader in mobile application security, with multi-layered protection for your Android and iOS apps. Learn more at Guardsquare.com.
VISA ANMÄRKNINGAR 🔗
UTSKRIFT 🔗
00:00:02,800 --> 00:00:08,260
Welcome to the Shared Security podcast, the longest running cybersecurity and privacy
2
00:00:08,260 --> 00:00:11,020
show for actual humans.
3
00:00:11,020 --> 00:00:17,680
No jargon, no hype, just honest analysis from industry veterans who've seen everything
4
00:00:17,680 --> 00:00:19,080
and survived it.
5
00:00:19,080 --> 00:00:24,500
Each week we break down the stories that matter, expose the nonsense that doesn't, and give
6
00:00:24,500 --> 00:00:30,120
you the tools to stay safe in a world where everything is connected and nothing
7
00:00:30,120 --> 00:00:31,760
is guaranteed.
8
00:00:31,760 --> 00:00:36,920
This is Shared Security.
9
00:00:36,920 --> 00:00:42,320
Today on Shared Security, we're talking about a federal case that turns a privacy feature
10
00:00:42,320 --> 00:00:46,120
into the center of a criminal prosecution.
11
00:00:46,120 --> 00:00:52,260
Prosecutors charged an Atlanta man after agents says his Graphene OS phone wiped itself during
12
00:00:52,260 --> 00:00:54,120
an airport search.
13
00:00:54,120 --> 00:00:57,880
The legal question is bigger than one phone, though.
14
00:00:57,880 --> 00:01:05,640
When does using strong privacy tooling become treated as suspicious or even as evidence or
15
00:01:05,640 --> 00:01:06,640
wrongdoing?
16
00:01:06,640 --> 00:01:12,440
And joining me to discuss this timely topic is my co-host, Mr. Scott Wright.
17
00:01:12,440 --> 00:01:14,560
Yep, I'm here again.
18
00:01:14,560 --> 00:01:15,560
Here you are.
19
00:01:15,560 --> 00:01:16,560
Here you are.
20
00:01:16,560 --> 00:01:17,560
Can't get rid of me.
21
00:01:17,560 --> 00:01:19,060
No, I can't.
22
00:01:19,060 --> 00:01:22,360
We keep trying, but you keep coming back.
23
00:01:22,360 --> 00:01:24,200
What's happening here?
24
00:01:24,200 --> 00:01:26,760
So yeah, no good topic for today.
25
00:01:26,760 --> 00:01:27,760
It is.
26
00:01:28,640 --> 00:01:30,640
Hopefully we get some good viewer feedback, too.
27
00:01:30,640 --> 00:01:31,640
That'd be fun.
28
00:01:31,640 --> 00:01:32,640
Yeah, definitely.
29
00:01:32,640 --> 00:01:39,480
It reminded me of, and we'll actually right up here on the YouTube video, we will link
30
00:01:39,480 --> 00:01:45,480
another episode that we did a while back on Border Searches, which actually was one
31
00:01:45,480 --> 00:01:48,280
of our most popular episodes.
32
00:01:48,280 --> 00:01:54,320
So this is somewhat related to that topic, but this is a little bit different.
33
00:01:54,360 --> 00:01:59,280
So Scott, would you want to talk a little bit about why this came up as a story to talk
34
00:01:59,280 --> 00:02:00,280
about?
35
00:02:00,280 --> 00:02:07,080
Yeah, I mean, I just grabbed my attention that first of all, it was talked about a person
36
00:02:07,080 --> 00:02:11,240
with a phone that had the ability to just wipe itself when you use what's called a
37
00:02:11,240 --> 00:02:14,040
duress password, which is interesting.
38
00:02:14,040 --> 00:02:19,440
I've learned about that doing some work in high security organizations, and they have
39
00:02:19,440 --> 00:02:25,000
that situation sometimes where if you're at gunpoint to your head and they ask you to
40
00:02:25,000 --> 00:02:30,600
open the safe or unlock a door, you can put in a code and in some systems, the
41
00:02:30,600 --> 00:02:35,320
code will actually work, but it alerts people with a silent alarm and a response
42
00:02:35,320 --> 00:02:36,720
can be initiated.
43
00:02:36,720 --> 00:02:43,080
But in this case, the duress code in the phone is sort of highly integrated
44
00:02:43,080 --> 00:02:44,680
with the OS, and I didn't know that.
45
00:02:44,680 --> 00:02:48,160
So I thought that was really interesting that you can have this
46
00:02:48,160 --> 00:02:53,240
mobile operating system that takes a password and says, oh, this is a password
47
00:02:53,240 --> 00:02:57,720
that tells me not to let the person in, just wipe the whole device.
48
00:02:57,720 --> 00:02:59,320
Yeah, that was pretty cool.
49
00:02:59,320 --> 00:03:00,280
Yeah, exactly.
50
00:03:00,280 --> 00:03:03,800
And for our listeners that may not know about this story.
51
00:03:03,800 --> 00:03:11,280
So this gentleman, Sam Turnick, was apparently under federal investigation
52
00:03:11,280 --> 00:03:18,840
or still is by the FBI for apparent terrorism, something to do with a group
53
00:03:18,840 --> 00:03:23,720
that he's part of in his hometown, something that, you know, he was him
54
00:03:23,720 --> 00:03:28,560
and some other protesters or something were going against some type of center
55
00:03:28,560 --> 00:03:33,800
for police, I'm not really sure exactly what exactly it is.
56
00:03:33,800 --> 00:03:35,560
But it was outside the U.S.
57
00:03:35,560 --> 00:03:39,280
So I somewhere in he was returning from somewhere outside the U.S.
58
00:03:39,280 --> 00:03:44,440
Well, he was coming from Dominican Republic back into the United States,
59
00:03:44,440 --> 00:03:49,040
into Atlanta, which was not where he's from, but it was like the first airport
60
00:03:49,040 --> 00:03:51,840
that probably had a connection or what have you.
61
00:03:51,840 --> 00:03:58,120
And the FBI actually sent the airport an alert that this gentleman was going
62
00:03:58,120 --> 00:03:59,600
to be landing there.
63
00:03:59,600 --> 00:04:05,160
And so they essentially started questioning him, took him into a room.
64
00:04:05,160 --> 00:04:09,680
He had asked for a lawyer like four times and was denied a lawyer.
65
00:04:09,680 --> 00:04:13,840
And, you know, maybe before we get into more of the details, you and I have
66
00:04:13,840 --> 00:04:21,040
talked about this before that airports are kind of this gray area in terms
67
00:04:21,040 --> 00:04:23,880
of what rights do you actually have?
68
00:04:23,880 --> 00:04:25,720
And this is not just a U.S. thing.
69
00:04:25,720 --> 00:04:27,720
This is an international thing, right?
70
00:04:27,720 --> 00:04:32,040
Like, you don't have all the rights that you do as a citizen of your country
71
00:04:32,040 --> 00:04:36,280
when you are in an airport because it's this it's just this gray area
72
00:04:36,280 --> 00:04:38,720
because you're you're at the border.
73
00:04:38,720 --> 00:04:40,240
They can do certain things.
74
00:04:40,240 --> 00:04:46,120
And so there are debates of do you actually have all of your rights?
75
00:04:46,120 --> 00:04:49,960
Yeah, I guess it comes down to where the laws have jurisdiction, right?
76
00:04:49,960 --> 00:04:55,720
And the territory inside an airport security space could have a different
77
00:04:55,720 --> 00:04:57,800
legal status, right?
78
00:04:57,800 --> 00:04:58,600
Yeah, yeah.
79
00:04:58,600 --> 00:05:00,240
So so more about the story.
80
00:05:00,280 --> 00:05:05,920
So obviously he was asked that if they could search his phone, he said no at
81
00:05:05,920 --> 00:05:12,240
first and then he it looked like he was putting in his passcode or I think he
82
00:05:12,240 --> 00:05:18,800
gave his passcode a passcode to the law enforcement people at the airport.
83
00:05:19,280 --> 00:05:22,760
And it was actually that duress code that you mentioned, Scott.
84
00:05:23,200 --> 00:05:25,720
And so it started wiping the device.
85
00:05:26,240 --> 00:05:26,560
Thank you.
86
00:05:27,560 --> 00:05:29,600
Restarted the device and that gave them the first clue.
87
00:05:30,160 --> 00:05:31,200
Hey, it's not letting us in.
88
00:05:31,560 --> 00:05:32,000
Right.
89
00:05:32,000 --> 00:05:37,960
And I guess it showed a screenshot or it showed Graphene OS when it rebooted.
90
00:05:38,440 --> 00:05:43,920
And for those of you that don't know, Graphene OS is a mobile operating
91
00:05:43,920 --> 00:05:49,760
system that will replace your Android operating system with this operating
92
00:05:49,760 --> 00:05:51,760
system that is more private and secure.
93
00:05:51,760 --> 00:05:56,640
So this operating system has certain things that can lock down your data.
94
00:05:57,000 --> 00:06:01,600
It can only use certain types of wireless networks or, you know, for
95
00:06:01,600 --> 00:06:06,200
example, two G networks are famously infamous.
96
00:06:06,200 --> 00:06:09,360
Let's say they're infamous for being insecure, right?
97
00:06:09,360 --> 00:06:12,640
So the phone basically disables that.
98
00:06:12,640 --> 00:06:16,920
So it only uses, you know, more modern wireless technology.
99
00:06:16,920 --> 00:06:20,400
So that's one of many things that this operating system can do.
100
00:06:20,560 --> 00:06:27,800
And so the big debate is because this person was using Graphene OS from
101
00:06:27,800 --> 00:06:32,240
a privacy perspective, the government is considering this evidence.
102
00:06:32,520 --> 00:06:38,120
And because he gave the duress code to wipe the device, this person
103
00:06:38,120 --> 00:06:40,520
is essentially destroying evidence.
104
00:06:40,520 --> 00:06:44,920
And I think that's what they are prosecuting him with, which is
105
00:06:44,920 --> 00:06:47,880
pretty unprecedented that this has happened.
106
00:06:49,890 --> 00:06:52,490
Mobile apps are just part of everyday life now.
107
00:06:52,810 --> 00:06:55,970
Banking, healthcare, shopping, entertainment, you name it.
108
00:06:55,970 --> 00:06:59,730
And with that comes a lot of trust because users are putting
109
00:06:59,730 --> 00:07:02,490
their personal data directly into your app.
110
00:07:02,730 --> 00:07:03,810
But here's the reality.
111
00:07:03,850 --> 00:07:05,730
Mobile apps are a growing target.
112
00:07:06,050 --> 00:07:10,010
A recent survey found that 72% of organizations experienced
113
00:07:10,010 --> 00:07:14,850
a mobile app security incident last year and 92% say threats
114
00:07:14,850 --> 00:07:16,370
are only increasing.
115
00:07:16,530 --> 00:07:20,010
And the way attackers are going after apps is pretty sophisticated.
116
00:07:20,130 --> 00:07:23,970
They're reverse engineering them, modifying them and redistributing
117
00:07:23,970 --> 00:07:27,890
fake versions through phishing campaigns, side loading and even
118
00:07:27,890 --> 00:07:29,370
third party app stores.
119
00:07:29,770 --> 00:07:34,170
So from a user's perspective, everything can look completely legitimate.
120
00:07:34,410 --> 00:07:37,370
That's why taking a proactive approach to mobile app security
121
00:07:37,370 --> 00:07:38,450
really matters.
122
00:07:38,570 --> 00:07:42,570
You want to stay ahead of these threats, not react after the damage is done.
123
00:07:42,850 --> 00:07:44,690
This is where Guard Square comes in.
124
00:07:44,810 --> 00:07:49,050
They provide advanced protection for both Android and iOS apps along
125
00:07:49,050 --> 00:07:53,450
with automated security testing to catch vulnerabilities early and
126
00:07:53,450 --> 00:07:54,930
real-time threat monitoring.
127
00:07:55,130 --> 00:07:57,690
So you can actually see what's happening out there.
128
00:07:57,770 --> 00:08:01,530
If your mobile app is critical to your business, and it probably is,
129
00:08:01,770 --> 00:08:04,010
this is something worth paying attention to.
130
00:08:04,170 --> 00:08:06,890
You can learn more at GuardSquare.com.
131
00:08:06,970 --> 00:08:09,050
That's GuardSquare.com.
132
00:08:11,280 --> 00:08:12,080
Yeah, yeah.
133
00:08:12,080 --> 00:08:16,040
I guess in my mind, I'm questioning like, did he actually
134
00:08:16,040 --> 00:08:20,240
have some, was he charged with anything before that?
135
00:08:21,280 --> 00:08:22,640
Maybe they were investigating him.
136
00:08:22,640 --> 00:08:26,000
But I guess the question is, if you wipe your browser history,
137
00:08:26,120 --> 00:08:27,200
is that destroying evidence?
138
00:08:27,200 --> 00:08:28,200
Right.
139
00:08:28,400 --> 00:08:30,240
Yeah, how far do you take this?
140
00:08:30,360 --> 00:08:31,880
Exactly, because you're right.
141
00:08:31,960 --> 00:08:32,560
You're right, Scott.
142
00:08:32,560 --> 00:08:35,760
I mean, you could think of all the things that is considered
143
00:08:36,160 --> 00:08:37,320
destroying evidence.
144
00:08:37,360 --> 00:08:40,240
You know, I think in a traffic stop, I always think of the most
145
00:08:40,240 --> 00:08:41,400
simple things, right?
146
00:08:41,440 --> 00:08:44,680
Or your house is being raided and you see in the movies,
147
00:08:44,680 --> 00:08:47,400
like the drug dealer, you know, putting all the drugs down
148
00:08:47,400 --> 00:08:48,800
the toilet, right?
149
00:08:49,040 --> 00:08:53,320
Like that is technically destroying evidence because,
150
00:08:53,360 --> 00:08:56,360
but in those cases, the police are raiding the house because
151
00:08:56,360 --> 00:09:00,600
they have a warrant and they have evidence that this person
152
00:09:00,600 --> 00:09:01,800
is a drug dealer, right?
153
00:09:02,160 --> 00:09:07,160
So hence, they're most likely going to find drugs in the house.
154
00:09:07,800 --> 00:09:09,400
So how do you apply that to this?
155
00:09:09,480 --> 00:09:12,400
Yeah, it is certainly based on the information we have in the
156
00:09:12,400 --> 00:09:15,920
story. It's probably unclear as to whether it was a privacy
157
00:09:16,080 --> 00:09:19,080
issue or not, because if they had already had an extensive
158
00:09:19,080 --> 00:09:22,960
investigation, they had a whole bunch of probable cause for,
159
00:09:23,200 --> 00:09:26,920
you know, looking at his stuff, then maybe I guess it could
160
00:09:26,920 --> 00:09:30,080
be potentially valid to say that it's destroying evidence to
161
00:09:30,080 --> 00:09:30,800
do what he did.
162
00:09:30,920 --> 00:09:33,600
But there was no warrants issued.
163
00:09:33,600 --> 00:09:34,280
Right, right.
164
00:09:34,280 --> 00:09:36,960
There was no warrant for his arrest either.
165
00:09:37,280 --> 00:09:40,880
This was a, you know, they just wanted to question him.
166
00:09:41,760 --> 00:09:45,760
But then questioning led to, let's see your device.
167
00:09:46,040 --> 00:09:51,280
He said, no, and that's where this kind of got a little worse.
168
00:09:51,720 --> 00:09:53,000
Yep, yep, yep.
169
00:09:53,000 --> 00:09:55,880
I'm curious as to like what percentage of people use the
170
00:09:55,880 --> 00:09:59,800
Graphene OS and and of those people, how many use it for
171
00:09:59,800 --> 00:10:02,480
this purpose or this kind of situation?
172
00:10:02,920 --> 00:10:04,040
It's a good question.
173
00:10:04,120 --> 00:10:09,520
I think I always look at this as people that install these
174
00:10:09,880 --> 00:10:12,880
operating systems, these privacy focused operating systems.
175
00:10:13,240 --> 00:10:16,160
I don't say they don't have anything to hide, right?
176
00:10:16,160 --> 00:10:18,920
So they're, you know, these are people that I would say are
177
00:10:18,920 --> 00:10:22,360
more on the extreme side of protecting their privacy for
178
00:10:22,360 --> 00:10:23,920
whatever reason, right?
179
00:10:23,960 --> 00:10:25,560
Yeah, there are lots of valid reasons.
180
00:10:25,560 --> 00:10:28,320
I mean, you know, there can be reporters trying to
181
00:10:28,320 --> 00:10:29,760
protect their sources, et cetera.
182
00:10:29,760 --> 00:10:29,960
Right.
183
00:10:30,120 --> 00:10:31,240
Yeah, all those things.
184
00:10:31,240 --> 00:10:35,800
And so I think there is this with law enforcement,
185
00:10:36,480 --> 00:10:40,160
probably because of previous cases where drug dealers and
186
00:10:40,160 --> 00:10:43,720
known criminals have used things like Graphene OS and
187
00:10:43,720 --> 00:10:46,480
there's, you know, there's actually, I was listening
188
00:10:46,480 --> 00:10:49,000
to the 404 media podcast that kind of went into this
189
00:10:49,000 --> 00:10:51,000
a little bit more in a little more detail.
190
00:10:51,440 --> 00:10:54,480
And they talked about there are phones that criminals
191
00:10:54,480 --> 00:10:57,760
buy that are preloaded with things similar to
192
00:10:57,760 --> 00:11:01,200
Graphene OS or they copy Graphene OS onto these
193
00:11:01,200 --> 00:11:01,720
phones.
194
00:11:01,720 --> 00:11:04,160
And then, of course, law enforcement knows that
195
00:11:04,160 --> 00:11:07,720
these phones are used by drug dealers and criminals.
196
00:11:08,240 --> 00:11:12,520
So there is a underlying, oh, if you're using Graphene
197
00:11:12,520 --> 00:11:15,160
OS, you must be, therefore, you must be a criminal.
198
00:11:15,760 --> 00:11:19,880
And that is the dangerous slippery slope that I
199
00:11:19,880 --> 00:11:22,400
think we want to talk about on this show is
200
00:11:22,400 --> 00:11:24,680
because that's not always the case, right?
201
00:11:24,680 --> 00:11:27,480
You may just want more privacy for whatever reason.
202
00:11:27,480 --> 00:11:29,840
Like you said, Scott, a journalist, a human
203
00:11:29,840 --> 00:11:35,000
rights activist or a politician or, I mean, it goes on
204
00:11:35,000 --> 00:11:38,360
and on and on or you just really care about your privacy.
205
00:11:38,480 --> 00:11:41,120
It doesn't mean that you are a criminal because
206
00:11:41,120 --> 00:11:41,880
you're using this.
207
00:11:42,240 --> 00:11:46,520
So yeah, it's it's a great example of situations
208
00:11:46,520 --> 00:11:49,560
where people need to think a little more, because
209
00:11:49,560 --> 00:11:53,360
clearly now that this has become a big story, there
210
00:11:53,360 --> 00:11:56,920
will be more attention from authorities on this kind
211
00:11:56,920 --> 00:11:57,920
of situation, right?
212
00:11:58,480 --> 00:11:59,680
They'll be looking for it more.
213
00:11:59,840 --> 00:12:03,160
Yeah, and I think it's a reminder about, you know, when
214
00:12:03,160 --> 00:12:06,400
you cross a border or you're at an airport, you're
215
00:12:06,400 --> 00:12:10,040
flying back or you're flying into a country, just be
216
00:12:10,040 --> 00:12:14,560
aware that the normal laws and the normal rules don't
217
00:12:14,560 --> 00:12:16,200
necessarily apply.
218
00:12:16,640 --> 00:12:19,400
And if your threat model says, you know, that you
219
00:12:19,400 --> 00:12:22,680
are in a high risk position, like I mentioned,
220
00:12:22,680 --> 00:12:26,320
journalist or politician or someone that is being
221
00:12:26,320 --> 00:12:28,640
actively targeted by either the government or a
222
00:12:28,640 --> 00:12:32,520
nation state or some type of threat actor, you need
223
00:12:32,520 --> 00:12:34,360
to be aware of these situations.
224
00:12:34,360 --> 00:12:36,520
And it might be a good idea, right?
225
00:12:36,520 --> 00:12:39,120
For you to use something like Graphene OS, depending
226
00:12:39,120 --> 00:12:41,720
on your situation, but I think be aware that this
227
00:12:41,720 --> 00:12:45,000
is a risk of working in that mode too, right?
228
00:12:45,040 --> 00:12:45,960
It definitely is.
229
00:12:45,960 --> 00:12:46,880
It definitely is.
230
00:12:46,880 --> 00:12:50,480
So this court case doesn't happen until October.
231
00:12:50,520 --> 00:12:53,760
So we won't know until then what happens to
232
00:12:53,760 --> 00:12:56,520
this gentleman or if he's going to be prosecuted
233
00:12:56,520 --> 00:12:59,840
is his lawyers, I think, have a good case because,
234
00:12:59,840 --> 00:13:02,360
by the way, this is an American citizen we're talking
235
00:13:02,360 --> 00:13:03,480
about too.
236
00:13:03,480 --> 00:13:06,280
So, you know, Americans do have certain rights,
237
00:13:06,960 --> 00:13:10,040
whether those rights are allowed or not, because
238
00:13:10,040 --> 00:13:13,400
he was at an airport, I think is also one of the
239
00:13:13,400 --> 00:13:16,440
big debates, because he did ask for a lawyer several
240
00:13:16,440 --> 00:13:18,240
times and was denied.
241
00:13:18,240 --> 00:13:18,640
Yeah.
242
00:13:18,640 --> 00:13:21,320
And so I think that's the big thing that his
243
00:13:21,320 --> 00:13:23,160
lawyers are probably going to be betting on.
244
00:13:23,520 --> 00:13:26,400
So, so, yeah, so let us know if you're
245
00:13:26,760 --> 00:13:28,200
listening or watching this podcast.
246
00:13:28,200 --> 00:13:29,320
We'd love to hear your feedback.
247
00:13:29,320 --> 00:13:32,480
Is this is this something that is concerning to you
248
00:13:32,480 --> 00:13:33,760
when you cross the border?
249
00:13:33,760 --> 00:13:36,080
Do you feel that people running something like
250
00:13:36,080 --> 00:13:39,280
Graphene OS have something to hide or is this just
251
00:13:39,280 --> 00:13:42,440
yet another privacy tool that people can just
252
00:13:42,440 --> 00:13:45,240
install and it's not necessarily something that
253
00:13:45,240 --> 00:13:46,600
shows guilt, right?
254
00:13:46,640 --> 00:13:48,200
Yeah, yeah, absolutely.
255
00:13:48,360 --> 00:13:50,440
And Scott, I think you had an update about
256
00:13:50,440 --> 00:13:52,200
your digital legacy tree.
257
00:13:52,400 --> 00:13:52,920
Yeah.
258
00:13:52,920 --> 00:13:56,240
So I've reached the stage now where the
259
00:13:56,280 --> 00:14:00,600
digital legacy tree book is in its final stages
260
00:14:00,600 --> 00:14:03,120
as a manuscript, almost ready for publication,
261
00:14:03,120 --> 00:14:06,040
which is exciting, and I'm looking for a small
262
00:14:06,040 --> 00:14:09,000
group of thoughtful reviewers who are interested
263
00:14:09,000 --> 00:14:11,920
in this idea of ensuring that your loved
264
00:14:11,920 --> 00:14:14,000
ones can have access to the digital accounts
265
00:14:14,000 --> 00:14:16,760
that you may want to have them take over if
266
00:14:16,760 --> 00:14:19,520
you die, kind of a sad situation, but a lot
267
00:14:19,520 --> 00:14:21,200
of people don't think about it that much.
268
00:14:21,240 --> 00:14:25,040
And as I mentioned in the past, I've been
269
00:14:25,040 --> 00:14:26,520
working on this for a little while.
270
00:14:26,520 --> 00:14:28,960
My goal is actually to release the book in
271
00:14:29,000 --> 00:14:32,440
around September and, you know, it's not a long
272
00:14:32,440 --> 00:14:36,600
book. It's actually quite full of value, I think
273
00:14:36,600 --> 00:14:40,120
through every chapter, just in terms of doing
274
00:14:40,480 --> 00:14:42,720
little exercises or things that you can record,
275
00:14:42,720 --> 00:14:45,160
create your own digital legacy file, I call it.
276
00:14:45,640 --> 00:14:49,360
And so just like to get people's viewpoints,
277
00:14:49,360 --> 00:14:51,120
you don't have to be a security or privacy
278
00:14:51,120 --> 00:14:54,160
expert just to get your own real life
279
00:14:54,560 --> 00:14:57,440
experience and concerns around this issue of
280
00:14:57,440 --> 00:14:59,440
what happens to your accounts when you die.
281
00:14:59,800 --> 00:15:02,840
So if you actually are able to do a review
282
00:15:02,840 --> 00:15:04,680
and provide me with feedback, I'm looking
283
00:15:04,680 --> 00:15:06,720
at, you know, doing an acknowledgement section
284
00:15:06,720 --> 00:15:08,840
in the book to name the people who've
285
00:15:08,840 --> 00:15:12,160
helped out and also give early access to
286
00:15:12,160 --> 00:15:16,560
people to the published book and the working
287
00:15:16,560 --> 00:15:18,040
materials that come with it.
288
00:15:18,040 --> 00:15:20,080
As I mentioned, there is quite a few
289
00:15:20,080 --> 00:15:22,080
little work worksheets and things that will
290
00:15:22,080 --> 00:15:25,000
help you create a record that you can save.
291
00:15:25,000 --> 00:15:27,960
So it's not huge, but 30,000 words.
292
00:15:28,280 --> 00:15:29,640
So you should be able to get through it in a
293
00:15:29,640 --> 00:15:30,160
couple of hours.
294
00:15:30,160 --> 00:15:32,440
So really excited to get people's feedback.
295
00:15:32,440 --> 00:15:34,880
And I think Tom is going to put a link to
296
00:15:34,880 --> 00:15:36,640
it in the show notes.
297
00:15:36,640 --> 00:15:39,600
So looking forward to getting more of that done.
298
00:15:39,760 --> 00:15:41,600
We'll be linking that in the show notes
299
00:15:41,600 --> 00:15:43,040
for everybody if you're interested.
300
00:15:43,360 --> 00:15:45,120
And if you want to connect with Scott on that,
301
00:15:45,120 --> 00:15:47,240
it's super, super important topic.
302
00:15:47,240 --> 00:15:49,320
And I think, like we've always said, right,
303
00:15:49,320 --> 00:15:51,280
Scott, the two things are inevitable in
304
00:15:51,280 --> 00:15:53,000
life, death and taxes.
305
00:15:55,040 --> 00:15:57,000
So very important topic for everybody.
306
00:15:58,240 --> 00:15:58,920
All right.
307
00:15:58,920 --> 00:16:01,360
Well, I think that's all we have time for today.
308
00:16:01,480 --> 00:16:03,760
So thank you all for listening.
309
00:16:03,840 --> 00:16:06,720
And until next time, stay safe, stay secure
310
00:16:06,760 --> 00:16:07,680
and stay private.
311
00:16:07,680 --> 00:16:09,240
Thank you for listening or watching.
312
00:16:09,440 --> 00:16:12,000
If you liked this episode, hit subscribe,
313
00:16:12,200 --> 00:16:14,040
share it with your friends and colleagues
314
00:16:14,080 --> 00:16:16,360
or jump into our community at shared
315
00:16:16,400 --> 00:16:18,880
security dot net slash supporter to keep the
316
00:16:18,880 --> 00:16:20,000
conversation going.
317
00:16:20,120 --> 00:16:22,520
Thanks again, and we'll see you next week for
318
00:16:22,520 --> 00:16:24,800
another episode of shared security.