Welcome everybody to my Proton Hardening Tutorial Part 2. The last video talked about Proton Mail
as well as your Proton Account just on a meta level. It's important to watch that first because
that Proton Account stuff is going to impact all the tools we covered today. This video we're going
to touch on pretty much everything in the rest of the Proton Suite from ProtonVPN, ProtonPass,
ProtonLumo, ProtonDrive, ProtonWallet, ProtonMeet. So I want to dive into the rest of the
stuff, show you guys the things to enable, not enable, what each thing means. And again, this is
a hardening guide, which means that this is for people who want to go above and beyond the already
really good default settings that Proton offers. The goal isn't for you to enable everything 100%.
It's to decide which of the tools make sense for your situation. And I'm going to do my best to
educate you as I go. There will be timestamps for each tool in the suite. Go ahead and click around
if you just want to look for a specific tool in the Proton ecosystem. The PGP guide should be the
next video so we can talk about pretty good privacy and email encryption in the next video.
Now let's get into ProtonVPN. So the first thing is picking a server. And this is a bit of a
polarizing topic, but I think for most people, the right advice is to just pick a server that's
closest to you. You're going to get the best feeds and you're going to get most of the benefits from
your VPN. I think it's more about the company you're trusting. And as long as you're not picking
a country that specifically is known to target VPN servers, you're probably still going to get very
good benefits. But that is kind of a personal call. I think the universal advice I share with people
is pick a server closest to you, unless you have a reason to not pick that server. Now port forwarding
is a really good feature if you are torrenting or you have any games that go through P2P and you
want the best speed. So if you are one of those people, you can definitely turn this feature on.
Just keep in mind, it does create an inbound path to your device. So if you want to get very
technical, that is opening up some attack surface, though I think a lot of that's speculative.
But either way, if you're really going for the max hardening, I would definitely leave this off, especially if you have no reason to turn it on.
The kill switch is one of the most important things of a VPN.
It ensures that when you're connected to the VPN, all the traffic only goes through the VPN.
And if you disconnect for whatever reason, all the traffic gets cut out.
I do recommend for almost all situations, especially if you're watching this guy, to enable your kill switch, especially the one here.
because this is their simple kill switch,
which what it means is if you are actively connected to the VPN server,
then the kill switch is enabled,
which means if anything else tries to connect outside the VPN tunnel,
then it won't go through,
which I think for most people is exactly what they want.
Now, they do technically have an advanced kill switch,
which I believe is on Windows as well as Linux.
And that one actually applies even when you click disconnect,
which means that when you're disconnected
and you have that one on,
it literally just doesn't connect to anything.
There is a big gotcha with the advanced kill switch.
The simple one is safe to use,
but for the advanced kill switch,
it can actually lock you out of your operating system itself.
You could be in a situation
where the kill switch is still activated,
but you get logged out of ProtonVPN,
so you can't connect,
and now you're kind of stuck
with broken internet on your system.
The next feature is NetShield.
This is a DNS feature.
They don't really present it that way,
but it is how it works.
So when you connect to your VPN tunnel,
oftentimes, especially the case with Proton,
Proton then becomes your DNS provider as well,
which means that they are the ones
who are handling your queries.
The cool thing is that they're able to do some filtering
because they get access to those DNS queries.
I always enable this
because it means that anytime you access a website,
it can block malware ads and trackers.
You can also just block malware only,
but I think for almost everyone out there,
you want to do the most amount of filtering.
If you're already trusting a provider with your DNS queries, there's no more trust required for them to filter those DNS queries.
So this is no different from regular DNS filtering.
It's just streamlined for you within the Proton ecosystem.
We'll talk about custom DNS in a second here.
But if you're not going to be touching custom DNS and you want to stick with just Proton stuff, enable this.
SecureCore is a bit of an interesting feature.
So if you turn SecureCore on, it's going to filter your traffic through more than one server.
And they specifically have these servers with higher levels of security.
If there's a malicious server, if there's something wrong with it, it's going to take you through a second server, which does have some potential privacy benefits there.
But the caveat is you're still trusting two Proton servers.
So it's not like you're trusting two different parties, which is a bit different from Apple's private relay or even Obscura's system with MulVad.
Because in that situation, you have Obscura and MulVad, each of which are two different parties in the relay.
This is also going to downgrade your speed.
So I don't personally use SecureCore because for me, a VPN is very simple.
I'm shifting trust away from my internet service provider,
and I'm hiding my IP address from websites.
Those are the two reasons why I'm using a VPN.
The other feature that is actually a little bit hard to isolate here,
but you're going to see an Onion logo here on Georgia, on Colorado.
And if you pull up that server list specifically and you go to the bottom,
you're going to see that there are these Onion servers.
This is Proton essentially handling the Tor layer on the VPN server itself, which in some
ways violates the whole trustless model of Tor.
But I think it's all relative, right?
So if you're comparing this to rolling your own Tor browser and, you know, doing that by
yourself, I'm always going to say use Tor browser for that.
This doesn't replace that use case.
But if you want Tor system wide for whatever reason, or you just want something that adds
more privacy than a regular Proton VPN connection for whatever reason, then you have the option
use these onion servers. Now, if we go into the settings, we have a few features. Start on boot
is really nice if you're someone who wants 24 seven VPN connections. So that way, like right when you
start, boom, it starts and it just connects right away. Notify unprotected networks is just going to
ping you and give you notification if you connect to a less secure network. So that way it's more
like on demand. So that's maybe for someone who just wants to use a VPN when they're traveling or
something like that. In terms of protocol, I, you know, they said they have smart. Personally, I'm a
WireGuard kind of person. I like how it's a much smaller code base. They don't even have
OpenVPN here as an option on the macOS client anymore. I think for most of you out there,
WireGuard is pretty much what you should be using. The one thing to flag though is Stealth,
which is WireGuard over TLS, which tries to obfuscate the fact that you're using WireGuard
in the first place. It's important to understand what Stealth is doing. This is for censorship
resistance. It's actually going to go through some bigger companies like AWS to try to obfuscate
your traffic. That doesn't mean your web traffic is getting sent to those companies necessarily.
It's just routing the encrypted tunnel through them. But again, it is actually adding a party.
That is how the stealth functionality works. So only enable stealth if you need it in a region or
a situation where your Wi-Fi or your region is blocking your VPN traffic. Split tunneling is
interesting. It is, as it says, experimental on macOS. I don't think it's experimental on other
platforms, though. What this is going to do is you can set it so, oh, hey, just these five apps go
through the tunnel, the VPN tunnel, and these five don't. I think if you just want a system-wide
VPN, you probably don't need to touch split tunneling. Split tunneling is very useful though
in situations where, hey, you know, I need pretty much a full system-wide VPN, but there's this one
program I absolutely need access to that doesn't work with the VPN. And if it wasn't for split
tunneling, then I couldn't use the VPN at all and I have to turn it off system-wide. Allow LAN
connections is the next thing. And definitely off is a good safe default. This is a situation where
you have a local printer on your network. Or for me, I have my NAS behind me and I like to connect
to that. So if you have a local machine on your network, you need to be able to access on a local
IP address, then you have to enable allow LAN connections. And that's how you can still access
it with the VPN still being enabled. Otherwise, if the VPN is enabled and allow LAN connections is
off, you're not going to be able to access those devices. Alternative routing actually functions
independent of this protocol. So they are both censorship resistant techniques. It actually
comes enabled by default. I don't see a reason to disable it. It's just in a situation where you
can't connect to Proton to log in. It's going to allow alternative routing to still try to make it
work if for whatever reason Proton is censored. Moderate NAT you should keep off unless you
absolutely really need the feature. It's for peer-to-peer applications. It kind of gives a
description there. It's not a feature I've used before, but this is one of the few features that
Proton specifically says slightly reduces your privacy. So it's something to keep off if you're
able to keep it off. And just like I covered in the last hardening guide, you know, I think there's
a difference between like invasive telemetry and analytics designed to just track you versus an
organization that is privacy respecting like Proton who wants to collect basic information.
But this is a hardening guide. So if you are trying to make things as private as you possibly can,
definitely keep these off. Custom DNS is something that I've covered more in other content. I made a
whole video that does like DNS versus VPN. And I would really check that out if you want to learn
more. If you are watching this video and you just need a basic VPN connection, you're in the Proton
ecosystem, I don't think you need to touch custom DNS. But I do sometimes like using a custom DNS
provider. And so if you want to learn more, check out that video and make sure you're using a trusted
DNS provider if you do choose to use a custom DNS. This is going to override NetShield. Again,
NetShield is a DNS filtering tool.
So if you use a custom DNS here
and you use your own DNS provider
like Mulvad DNS or NextDNS or even Control-D,
you are going to override NetShield.
So you are having to shift that feature to another tool.
My last thing to mention about ProtonVPN
is that there is kind of these like always connected
slash kill switch features on mobile.
I would just overall treat mobile
as a little bit less robust,
especially on the iOS side of things.
We see time and time again,
that full system-wide VPNs on iOS,
while they still very much do something,
we can't fully guarantee that 100% of your traffic
is guaranteed to go through the VPN tunnel.
This is a serious issue.
It is an Apple problem that Apple refuses to acknowledge
within the iOS ecosystem
because they still try to, at times,
make weird exceptions for their own traffic.
On Android, while this is much better
than what we've seen on iOS,
we have still seen examples in the past
where some things didn't go through
even the whole like only allow connections through your VPN feature on Android. So just in general,
I would treat mobile devices as like, hey, your VPN is going to work for you potentially 99% of the
times. And that's still really good. But I really want to make that clear so that no one feels
misled by the privacy they're getting on a mobile operating system. All right, the next tool is
going to be Proton Pass. And it's my favorite Proton tool, like for the record. So for this one,
I actually want to start in the settings first.
In general, while I'm not saying that the ProtonPass beta is insecure,
I do like to run stable software for something as sensitive for me personally as my password manager.
So I don't enable the beta and that is something I do recommend if you have a higher security threat model.
Website favicons, favicons, however you want to say that, that's a polarized topic, I think.
This is going to be anonymously proxy.
Just be aware that is technically something that you are adding a bit of trust in.
I do keep it enabled.
I like the icons next to the entry, but just be aware that there is a little bit of trust
you're handing over there.
Offline mode, I would always enable.
It's not necessarily a security thing, but I've been in so many situations where I need
to be able to log into something.
I think my Wi-Fi router is a perfect example.
I don't know the password to my Wi-Fi.
It's in my password manager.
But if I don't have internet for whatever reason, and then I can't log into ProtonPass
because it requires an internet connection,
then I can't get the password, so I'm stuck.
So enable this, it's very good to have,
and I can't think of anything it's going to cost you
from a privacy or security perspective.
Next is the security tab, and guys, I want to be clear here.
There is, in my view, no right answer.
I do think a pin code might not be the right answer,
and none is not the right answer.
So I think picking between password and biometrics
is really where the real debate's going to lie
for most of you out there.
Biometrics are really nice because they're convenient,
they're easy, and also there's no way to shoulder surf
biometric. If I'm out and about and I'm traveling and I'm using, you know, touch ID or something like
that. And if there's someone sitting next to me, they can't see me type in my Proton password to
get into my password manager, which is a really important benefit. And think about security
cameras and stuff like that, too. The nice thing about a password, though, is that it actually has,
you know, different jurisdiction benefits because police probably can't compel you to hand over a
password, but they can compel you to unlock something via biometrics. So this is something
that you need to make a decision on. I think maybe a safe thing like what I would personally do if
I'm trying to pick between these situations. If I have a mobile device, biometrics might make more
sense because I'm on the go. I want things to be convenient. And also I want to prevent that
shoulder surfing concern. And if I'm at home at my desktop, I'm personally still going to be using
biometrics, but I could see someone where they do like password on their desktop and then they use
biometrics on the go. Or if you have a different threat model, you could even end up reversing that
where if your main concern is traveling over a border,
you may actually be more likely to use biometrics at home
and then a password when you're traveling.
Autolock is something that is not even able to turn off with ProtonPass.
Obviously, the sooner you can make the autolock, the better.
What this is going to do is if you unlock ProtonPass,
you copy a password and you don't use it,
it's going to autolock itself.
So I do 10 minutes.
I think 10 minutes is a nice middle ground here.
You can do quicker,
but then you're going to have to constantly be unlocking your vault.
If you want extra security, and this is nice because, you know, you are still ultimately logging into ProtonPass with the same password as the rest of your Proton account.
And I know that bothers a lot of people.
So you can add an extra password so that you need to only protect ProtonPass with this extra password.
You're definitely going to gain security when you do this.
It's a question of convenience and how it's going to benefit you.
But you definitely should enable this if you have the absolute highest security needs.
And that is going to be the best way forward for you.
This is one I do also recommend everybody uses.
You know, a lot of programs can read your clipboard
or you could accidentally paste something from your clipboard.
And so this is going to automatically clear your clipboard
when you copy a password.
So I open ProtonPass, copy my password, I paste it.
And then two minutes later, it's just going to clear it.
So that way I can't paste my password again.
You can paste it as many times as you want within the two minutes.
Of course, you can turn it off, but I do think it's a good feature to enable.
Now I created this test vault here.
And within the vault, keep in mind, when you're generating a password, you have a lot of options
here for most situations. The defaults are pretty good. They normally default to like four or five
words, I've noticed, for the memorable passwords. And there's also the random passwords. And you
can just drag it here. You can have advanced options just to make sure you're generating
strong passwords, because you are using a password manager and you have that luxury.
Parts of Pass also integrates with SimpleLogin, which I think is actually my favorite feature.
Now, something I didn't know that a Techlorian told me in our call is if I generate this here,
like I just generated this alias and then I click save.
If I create this alias, right, and this is for like, let's say use this to become a Techlorian,
which you guys should do.
You can support what we do down in the description.
We have a private signal group and there's lots of other fun perks there.
If I email you to your alias, it's going to go to your regular email inbox
and you're never going to expose your email to me directly, which is a huge privacy benefit.
But let's say you want to email me first, right?
Normally, what I would do is I have to log into SimpleLogin, find the alias, generate the reverse alias, and then I have to email it to that.
If you guys know, you know.
It's kind of a pain in the butt.
But what the Techlorian taught me is that if you go to the alias here, right?
Like this is just for the email.
If you go to contacts, if I already emailed you, it's going to show up here.
But I can also create the contact here, right?
So I can do contact.techlor.tech.
And then you can click this and it'll open in your email client or you can copy the forwarding address.
And that forwarding address, it looks like gibberish, but that allows you to be able to email someone.
And I would only ever see this alias.
So it looks like you're emailing me from this alias.
I would recommend all of you enable pass monitor.
I think it's on by default, but there is no reason not to use this.
It's going to monitor your passwords to see if any of them got breached.
This could be where you find out that one of your services got breached.
Here, first, before the company tells you about it.
That's not uncommon.
It's going to tell you if you have reused passwords, weak passwords.
It also can check if you put a domain, if that domain has 2FA, but you don't have it enabled in ProtonPass.
It'll tell you that so you can enable two-factor authentication.
And we already talked about ProtonSentinel in the last hardening guide.
The last two things, again, guys, go back to the first hardening guide because your ProtonPass, where all of your passwords live,
largely inherits the security of your Proton account, which was covered in the first video.
So that is always a thing I'm going to remind you about.
The last thing I want to talk about is shared links.
This is when I go to an item and I click share and it's going to give you a secure link.
Guys, if you give that secure link to anybody, they have access to that credential.
And also keep in mind, when you have a shared vault, when you share it with somebody else,
they're also going to have access to everything in the vault.
There actually was some really interesting research from Zurich,
which found that there were some password managers and their sharing features
were actually how they were exploited to access many things in the vault.
They did not study ProtonPass specifically,
But it's really important to read into that research and understand that just having any kind of sharing enabled on your account, period, is opening up your attack surface a little bit.
So I try to avoid sharing unless I absolutely need to.
As you can see, I actually have one link that I generated recently to someone I had to share one credential with.
But keep your sharing as minimal as you can.
Proton Drive is pretty straightforward.
And honestly, I don't have too much to share, but there are still a few things I wanted to cover.
First off, a lot of these will have app blocks on mobile.
So you can set some kind of way to make sure that you need extra authentication to access the app on mobile.
Proton Drive also has share link controls.
So if I create a new folder here, you should understand what those controls are.
So if I click share, you can share it with other people within the Proton ecosystem,
which would keep it encrypted between those people.
And then you also can do a public link.
If you do a public link, you can set it to editor so anyone with the link can view.
But keep in mind, there is this feature down here, which a lot of people don't know about,
which is you can require a password as well.
So if you do a public link, again, you can do it with a password,
which is nice if that person doesn't have Proton.
Keep in mind, if you are sharing access to someone else,
the email address of your Proton account, if you're sharing a document or something,
is visible to the recipient.
So just be aware of that before you share things.
Proton does also say if you're doing a photo backup,
there is the creation date that is not encrypted.
That's just so that they can actually chronologically sort your photos.
I don't think there's anything really privacy invasive there, but it is something I wanted to flag.
In terms of docs and sheets, it's pretty well done.
Document names, the contents, the edits, the comments, suggestions, those are all end-to-end encrypted.
And so the documents are all very well thought out and there's no caveats I wanted to share there.
Now, one question I do see a lot, which I did want to clear up, is should I encrypt my files before uploading them to ProtonDrive,
specifically with tools like Cryptomator, which are designed for that?
And I have a whole guide on Cryptomator if you guys want to encrypt your files before they go on any cloud provider.
I think it's really unnecessary, right?
Like this is by itself end-to-end encrypted.
So unless you have a crazy high threat model where even Proton themselves having some weird, let's say, vulnerability in their encryption,
and you want to make sure all your documents are completely secure, then sure, you can combine Cryptomator with ProtonDrive.
But you're getting double end-to-end encryption for what I think is really no real benefit and also less reliability.
Lumo AI is next, and it is their LLM chat.
They made a lot of updates to this over time, and it's really developed since I first looked at it.
The first feature is their ghost mode, so this disappears when you close it and is never saved.
I don't think this meaningfully changes the privacy or security in terms of how much you're trusting Proton or anything like that.
They do have a very good write-up on how they're able to process these queries as privately as they do.
And it's very cool and interesting text.
So if you guys want to check that out, definitely look into that.
Based on what I've seen, Ghost Mode doesn't change any of that system.
It just is a local feature.
So if you want to be able to do things locally and it's not going to save the history locally in your browser,
that's what Ghost Mode is really for.
It's kind of like incognito mode in a more traditional browser setting.
If you go into the settings, the personalization is stored zero access.
So nothing here should impact your privacy or security.
So feel free to have fun and use those features to your heart's content.
Memory is the same thing.
Also zero access.
So you can turn it on.
It's not going to really jeopardize your privacy in any way.
The main feature actually that I really think in any way changes the privacy of LUMO.
It's a pretty reliable and similar experience across the board.
But automatic web search.
So this actually will transmit, if you have it enabled,
it transmits a simplified version of your request.
to a select partner API to retrieve results.
They say that they are privacy-respecting partners,
but it is worth mentioning that if you do have web searches enabled,
it is going to leave that Proton encrypted envelope
and where the normal privacy guarantees exist.
Every other Lumo feature is zero access encrypted end-to-end,
but the web search is the one feature
where obviously you can't really do that.
They have to search the web somehow.
I think if you're already trusting Proton with Lumo,
I don't see how this is going to make a huge difference for you.
But again, this is a hardening guide, so I want to make sure you guys are aware of that.
There is a delete everything button if you just want a simpler way to clear all the chats on your system.
Otherwise, Lumo is a pretty safe, reliable experience that doesn't have much variability
from the most to least possibilities of how secure you can make it.
Proton Calendar also doesn't have a huge amount here.
I think the one thing to just flag right out the gate is that event start and end times.
and time zones are signed, but not encrypted.
That's needed because the Proton servers
need to be able to index and retrieve them.
I kind of see this as the subject lines in ProtonMail,
which I covered in the last video.
So it's just kind of a necessary part of running the service.
The other main thing,
and this is probably the main exposure
to kind of flag for you,
even though Proton Calendar is end-to-end encrypted
and does a lot of really good stuff to help your privacy,
if you have an external attendee,
so you create an event and you add a participant
who does not use ProtonMail, the whole invite actually falls back to a normal unencrypted email
flow. In terms of sharing your calendar, you have a couple options. The first of which
is to just share your calendar with another Proton user. And this is end-to-unencrypted,
has all the collaboration. And so if you have someone you want to share your calendar with,
and they are a Proton user, this is always the way you should go. However, these links that you
generate here. I mean, there's some obscurity there because if I create a link, it's going to
be just random gibberish and then I can import that into any other calendar. But keep in mind
that that link, anybody theoretically could get that link if you leak it for whatever reason.
And now anyone can read your calendar entries. So keep in mind that this is a huge amount of
exposure. It's just part of how calendars work. It's not something that Proton is doing wrong.
But the nice thing is that this is view only and they cover that in their documentation. So this
is more for being able to just view your calendar from another calendar like Apple Calendar,
Google Calendar, etc. So you can subscribe to it essentially from a third party. The last piece of
advice I have is to compartmentalize calendars if you are using Proton Calendar for more than one
thing on the same account. So that way you can have maybe a shared calendar with co-workers,
a different shared calendar with someone in your personal life, and then maybe just a third calendar
for events that is made public for maybe like a group that you run or an event that you organize.
On the topic of Proton Calendar, recently they have also had Proton Meet, which is kind of their Zoom alternative.
And you can actually have a feature where it automatically attaches a Proton Meet link to Calendar Invites.
There's not much to talk about here.
It automatically enables MLS, which is messaging layer security, which is going to give you end-to-end encryption group communication within the call.
And that is just enabled by default.
If I start a new meeting here, it's actually going to be part of the link that you share.
The link that you share is the key.
So you're going to see here there's the ID and then there's the password there.
So when I copy the link, if I actually remove that password from the link, it's going to take me to the right room.
But if I click join, it's going to say, oh, the meeting password is incorrect.
So again, it really is everything after the hashtag that is the meeting password.
You can also lock a meeting in the settings.
So if you're hosting the meeting, once everyone's in the meeting, you can lock it so that no one else can join.
So that's a way to add a bit more security to the meeting.
Other than that, I think this is one of those cool privacy kind of services where there's not much to say.
Like if you use it, you're pretty well off.
There's not much more to do beyond the defaults in ProtonMeet.
Similar-ish story with ProtonWallet.
This is a self-custodial Bitcoin wallet that Proton put out.
There isn't honestly a huge amount of extra privacy that they've added.
And I think the biggest thing to flag here is that it is Bitcoin.
Bitcoin does have a lot of privacy concerns.
And so I always want to just quickly flag that.
I would assume most things that Bitcoin does by default are public and permanent.
And so if somebody really wants to start investigating trends over time, they can probably start to put those trends together.
That is not on Proton whatsoever.
That is just a reality of Bitcoin.
But I do wish that Proton added some more privacy features because it would make Bitcoin more private within the Proton wallet ecosystem.
The on-ramps, based on what I could find too, if you actually want to buy it, it seems like they're Banksa and Ramp, which do have some KYC as well, if not full KYC.
and it seems like they want to use a card.
So you see it's going to ask for a country.
So there are more private ways to be able to purchase Bitcoin.
So that is just something to flag right away.
One thing that is cool is that if you use their Bitcoin via email feature,
it is going to do address rotation.
So you're going to be using different Bitcoin addresses every time you send something.
If you're a Bitcoin nerd and you want to get really technical,
when you're creating a new wallet, you can actually use Taproot,
which has some privacy benefits, but it's not as widely supported.
So if you're more technical and you know what you're doing, they have a few more kind of details there.
But it's not something I would just widely recommend to everybody unless you know for sure you want to do that.
The other important thing is that I'd say 80% of your day-to-day safety and protection is actually from the first video.
It is actually the meta account protection because so much of that account is what gets access to these other tools, which is one of the main things I see online.
People are like, oh, wow, like, do you really want to put all your eggs in one basket?
And it's like, well, it's kind of a tradeoff.
Is it better to trust 10 different companies, half of which aren't doing as good as Proton in what they do best?
It is a trade-off.
I don't think there's a right answer here.
And I think it's really up to you and where you want to put trust.
But keep in mind, just because Proton has all these different things doesn't mean you have to use everything in the ecosystem.
The ecosystem is an option.
And you guys should try to use whatever in the ecosystem is benefiting your privacy and security the best.
The other overall theme between both videos is that when you share something, especially
outside of the Proton ecosystem, it can downgrade, oftentimes it does downgrade, the privacy
of what you're sharing.
Does that mean it's useless?
Absolutely not, because your data is still being stored in a central place that has zero
knowledge encryption.
And it's not your problem that someone else isn't using something that's end-to-end encrypted.
So if they were also doing what you were doing, then everyone is better protected, right?
So you are actually still part of the movement of helping secure yourself.
other people's data. But of course, for a hardening guide, always be a bit cautious when you're
sharing and just be aware that it is almost entirely a different amount of protection
when you're sharing anything outside of the Proton ecosystem to a non-Proton user.
The only other thing I'd say is keep automatic updates enabled on all of your operating systems,
especially if you're using the local apps and the local programs. Keep those enabled. That's how
Proton's going to be able to patch any kind of security issues in the software quickly.
And it's good to just remind you that everything that Proton does is open source, and most of their tools are independently audited.
So this is kind of a really good place to be for just really good out-of-the-box security and privacy.
And then with this hardening guide, you can really maximize it and take it to its full potential.
I want to thank you all for going on this journey.
If you're watching this, you clearly really care about your safety.
So that's really exciting for me because I also really care about this, and I have a lot of fun talking about it.
I want to definitely thank Proton for partnering with us and making it possible to do these kind of guides.
I would love to make these tutorials anyway.
So the fact that we're able to work with Proton and make sure that these are as good as they can be, it's just an honor.
So I really hope that it can help you guys, too.
And don't forget to stay subscribed because the third video I want to make is just going to be about PGP,
which is that whole thing of like, oh, how can we actually encrypt our emails to other people who are using PGP?
And how can we receive other people using PGP's emails in a secure way?
And that was kind of what I teased in the last video.
a lot of you asked for that PGP guide. So that will be the next video I'm going to make in this
series. Thank you again, The Proton. Thank you all for watching and I'll see you next time on Techlore.