Podcast
Root Causes 263: Secure Connection Methods Roundup


Hosted by
Tim Callan
Chief Compliance Officer
Jason Soroko
Fellow
Original broadcast date
December 20, 2022
In this episode we discuss the three methods a user might choose for secure remote communications: VPN, SSH, and TOR. For each we discuss the reasons you might choose them and the pros and cons of each.
Podcast Transcript
Lightly edited for flow and brevity.
The topics are VPN, SSH and TOR. And the idea being when do you select them and why. So, there’s really three different properties - -
So, we are gonna ask the question then – who are you distrusting and are you shifting trust from one place to another? The other question I’m gonna be asking is what are you actually protecting and what are you potentially putting at risk? And then I’m gonna call out alternatives and other ways to think about these technologies.
And the reason why I’m bringing it up like that, Tim, is because I think for all three of these things – VPN, SSH and TOR – it’s almost like they’re complete ideas upon themselves that people think, ah, I’m just gonna use this and I’m safe. And that’s true sometimes for you might be giving advice to a family member. Oh, just, you know, here, let me help you use a VPN.
Let’s start with VPN first just because it’s the one everybody knows and it’s the one that’s probably universally applicable whether it’s family, you know, or Uncle Tom or whether it’s at the enterprise. You might be using VPN everywhere. And we said this before and, Tim, I believe it was – I’m gonna go up to my notes – it was Podcast 80 where we talk quite a bit about VPNs. So, I’m not gonna get into detail about it except to answer the three questions that I asked – Who are you distrusting and how are you shifting trust? Well, with VPN, Tim, you know this. When you are using VPN it’s because you distrust the ISP. You distrust your internet service provider.
So, the next question of course, for the enterprise user what are you protecting? Well, what you actually have done now with the enterprise is you are now trusting the enterprise. That’s typically a very good idea. The enterprise is asking you to use VPN. Great. But remember, the second part of my question is what are putting at risk and remember now that by creating that VPN, basically that privilege of being able to open that door to the network, you now have a privileged credential sitting out in the world somewhere that can access your network.
So, the alternatives, Tim, and I’m working through this very quickly but the alternatives are I think that if you are a home user and you just have your standard internet that you trust from your ISP or if you are a mobile user and you are just on cellular data, I don’t think there’s a lot of real big necessity to turn on VPN if you are, of course, using your enterprise.
With SSH, typically you are going to be an enterprise user. You are going to be some sort of administrator. But I think there are also a lot of internet hobbyists out there, especially now with cloud adoption. I know a lot of people who are not enterprise users and still using SSH.
The problem with SSH, of course, and we’ve talked about this before, Tim. I believe that podcast 224 or 226 and we talked at length about the problems with unmanaged cryptographic keys that are the heart of SSH, and I think for those of you who are hardcore enterprise administrators, I don’t need to drill down at all. You already know the risks that that opens up and I do want to mention though for everybody else who is a little bit less experienced, you absolutely need to be taking better care of your crypto keys. Otherwise you may have created more problems that you are solving.
In order to be able to get to your remote server. It’s fantastic that you can remotely administrate it, but keep in mind that you have opened up Port 22 to the hostile public internet. And not only that, but these crypto keys are a pain in the butt. We detailed that quite a lot in Episode 266 of this podcast. So, what I’m gonna offer then is an alternative and this is for those of you who are either home users or enterprise users. But that whole problem with the Port 22 means wouldn’t it be great if basically the main server you are trying to get to you, you got to it indirectly through a jump server. A server that you were less concerned about and so, therefore, you could open up say a Port 22 on a jump server and then have a dedicated connection between your jump server and your final destination server. It’s a slightly advanced topic.
So, it’s not necessarily a VPN. It’s similar in idea to VPN but there is an actual TLS connection where you can hold the keys. You can hold the keys and actually make a TLS connection between you and those two other servers – the jump server and the destination server, and then your SSH session occurs inside that TLS encrypted network connection. And I like that idea, Tim. And that’s a very modern idea that’s now out there. There are some startups that have those capabilities, and I just wanted to mention on this podcast because when we are choosing between VPN and SSH and any other of these kinds of connection technologies, it’s not often recommended to have a connection with a connection within a connection because a really smart operator can unravel all of that rather rapidly if the connections are weak. But one reason I like SSH within TLS is because TLS certificates can be managed very, very carefully. SSH less so.
If you were to come up to Tim and I and ask how can I protect my SSH keys vs. my TLS certificates, we could have a lot to say about using the two together. There is, of course, Tim, the topic of SSH certificates in itself, was a whole other idea, Podcast 226, if you want to hear about that, but I just wanted to bring it up here just to complete the thought of the alternatives for SSH. It is so readily used and so poorly used I wanted to spell it out.
I think, Tim, in the spirit of an end of year podcast – and this is why I bring this up – I think there’s a lot of people who might have a spare ten minutes or like, hey, I’m gonna download a TOR browser and check it out. Just play with it and see what’s going on. And they might come to the conclusion, hey, this is a really good way for me to anonymize stuff I’m doing on the internet. Maybe there’s some shopping I want to keep away from family. I don’t want them to know what I’ve been shopping for. Maybe I just want to avoid internet marketers and just get a little privacy into my life in terms of I don’t want to be cookie tracked. I don’t want to have, you know, all the things we’ve talked about previously on this podcast about browsing privacy, Tim.
And then, of course, there’s other folks who are using TOR in order to engage in other stuff on the dark web. Some of which is no big deal and some of which is just really, really, really perhaps bad. Right? And I’ve gotten not a lot of comment about that. It’s just that’s what some people are using it for.
So, let’s get into the brass tacks. What are you protecting and what are you putting at risk? And I think even before we get into that I do want to mention, Tim, VPN over TOR in terms of the question who do you distrust, VPN over TOR is when you don’t trust your ISP but you still want to do TOR and believe it or not, there is a concept of TOR over VPN. You know, you might ask the question, well, why would you do that? That’s if you don’t trust the exit node of TOR, which is kind of a strange topic. I’m sure some people have reasons why they’d want to do that, but I’ve never understood why you would distrust the exit node of TOR because I don’t believe that exit node is gonna give up a lot of information about you. If you are doing TOR over VPN compared to say VPN over TOR. TOR over VPN actually deanonymizes you in a way that you are giving up a lot of information to your VPN provider. So, that’s just something to keep in mind.
So, what are you protecting? With TOR, there’s really bad stuff sometimes going on over TOR. Let’s just face it. Right? On the entire public, hostile public internet, it’s hostile out there.
And I think if your purpose is really about anonymizing from a privacy standpoint then I would suggest as an alternative check out some of the privacy browsers that are out there. DuckDuckGo and Brave and there’s a few other good ones out there. I think that’s my suggestion.
We don’t know exactly how the clever malicious people are gonna figure out how to exploit information and we won’t know until it’s been exploited. This is how exploits work. And the more we mask this stuff, the more we reduce the opportunity for those people to do that. A good example is if you go back to Snowden and the NSA, nobody – I don’t want to say nobody – but lay people did not have any idea that that was going on until it was exposed. And so, what else is going on or could go on that we are not aware of? If we harden our privacy, this is what people like Electronic Frontier Foundation are all about, right? If we harden our privacy everywhere, then the opportunities for very clever, educated people with malicious intention to exploit the mechanisms of the digital world, those opportunities go down.
And that would be the other reason you would do it, is almost for ideological reasons. To say, I just want the chance for somebody to find information they are not entitled to to be as low as it possibly can because I cannot forecast how everybody in the world is gonna figure out a way to use that maliciously. And there is an aspect of that I think for sure among a subset of people. A pretty small subset of people but a subset of people who think in those terms. They are usually pretty educated about computers, and again, they usually have a little bit of an ideological bent when it comes to this sort of thing.

