Add comparison blog posts

This commit is contained in:
davegson 2020-01-22 21:58:21 +01:00
parent ef906e8e14
commit e45d450cfb
4 changed files with 158 additions and 0 deletions

View file

@ -0,0 +1,78 @@
---
title: How the SPN compares to Tor
date: 2020-01-22
author: davegson
---
# How the SPN compares to Tor
## Different Missions
**Tor project's mission**
from [https://www.torproject.org/](https://www.torproject.org/) - in the footer
> To advance human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, supporting their unrestricted availability and use, and furthering their scientific and popular understanding.
**Safing's mission**
from [https://safing.io/our-values/](https://safing.io/our-values/)
> Enabling you to reclaim your privacy
> We're building tools to help everyone withstand today's mass surveillance
**A comparison**
How would you differentiate them?
My take is that Tor's mission is broader than ours. They do overlap, in the sense that one can interpret their mission to include ours. We wholeheartedly agree and appreciate Tor's work and outlined broader mission, but our focus is on a specific sub-area of theirs:
> Building tools to help everyone withstand today's mass surveillance.
We mean *everyone*. We want my mom and your mom to be able to conveniently withstand mass surveillance without having to venture deep into tech. This is our focus. This is what drives us. It's the reason we get out of bed.
## Maturity
Tor was released in 2002, while the SPN will launch in April 2020. It goes without saying that Tor is the far maturer project of the two. The SPN is still in its early days.
## Scope of Protection
The Tor browser has great coverage, supporting all major operating systems. It protects the browser habits of its users and is a breeze to set up. When one additionally wants to safeguard the whole computer via the Tor network one has to use the [operating system tails](https://tails.boum.org/install/index.en.html), which is great at what it does, but hard and technical to set up and use.
This is one key difference to the SPN. With it, it's a simple plug and play. You download the open source app and then it takes care of all your connections, not only those of the browser. When launching in April, we will support Windows, with Linux following shortly after. We are planning on supporting Mac and Mobile in the future too, so everybody can enjoy easy privacy with their preferred operating system.
Another detail is that Tor does not transport everything, notably UDP traffic. The SPN will support TCP and UDP (+ variants) from the get go and we will see if we will need and implement anything else.
## Handling Circuits
Both Tor and the SPN provide privacy by decoupling the person (ip-address) from the destination. This prevents your Internet Service Provider and everyone else from logging your Internet activities. When no other identification is provided you even arrive at the destination anonymously, meaning the visited server cannot know who you are.
This is achieved by routing connections through a circuit. This splits the full route into sub-routes so no single server can both know the person and the destination.
![SPN core](https://safing.io/assets/img/spn/spn-core-web.png)
When the connection arrives at the last server of the circuit it still has to travel to the desired website. With Tor, this may lead to a slower Internet experience. As an example, a person located in Europe loading a European website may receive a circuit exiting in the US. This means the connection has to cross the Atlantic twice (EU -> US -> EU). After a circuit with Tor is established all your other connection will use the same route. A circuit change normally occurs every 10 minutes.
With the SPN however, every connection is calculated individually and leaves the network as near to the destination as possible. This means:
<br/>
- your connections are spread across the globe
- visibility in the 'open web' is minimized
- connections are not slowed down by having to go extra miles
![SPN community](https://safing.io/assets/img/spn/spn-community-web.png)
## Minor comments
**The Dark Web**
Tor's mission for anonymity also enables people to host content anonymously through onion domains. This is a non goal for Safing.
**SPN enforces DoT**
While the open source SPN app sits at the kernel, it can do all sorts of amazing stuff. It will enforce all your DNS queries to use DNS over TLS (DoT), which also prevents your router from snooping on you. Later, it will also block malicious connections via an integrated Application Firewall.
**Free vs Paid product**
Both the SPN and Tor are FOSS. But Tor is free to use while you have to subscribe to the SPN in order to use it. Be aware you are not only paying for the SPN, but also supporting us to develop the free application firewall and enabling us to continue fighting for a brighter future.
## Conclusion
Tor is a great project which has pioneered privacy technology and is a firm player in the space while the SPN has fresh, innovative solutions which tackle uncharted ground and focuses on ease of use before all. Depending on your threat model, the SPN may be an alternative to Tor. Or it might not. Ask Marvin.

View file

@ -0,0 +1,72 @@
---
title: How the SPN compares to VPNs
date: 2020-01-22
author: davegson
---
# How the SPN compares to VPNs
## Introduction into VPN Technology
### What is a VPN here for?
The VPN technology was developed to allow remote workers to securely connect to a corporate network to virtually check into the office and access internal resources. It does this by establishing a secure tunnel between the worker and the company. The VPN shields the whole route from the worker to the office, never entering the "open Internet".
### What do commercial VPNs do?
Naturally, they do something very similar. As an example, let's say you want to connect to "google.com" via a VPN. The VPN client first creates a safe tunnel to the VPN server, which then calls upon "google.com". So a VPN safeguards your connections up until the VPN server, then unpacks their protection and routes it back into the open Internet.
### VPNs do not protect your privacy
There are many legitimate use cases for a VPN, like securely connecting to your corporate network or "beaming" into another country to enjoy different content or cheaper prices. But VPNs do *not* protect your privacy.
## Meta Data Collection
A VPN does protect you from your Internet Service Provider (ISP) to collect and process you browsing activities. But this just delegates the problem: now the VPN that can collect and sell all your data, which many of them do.
![VPNs](https://safing.io/assets/img/spn/vpn-web.png)
The SPN however decouples the person from the destination, resulting in true privacy. And already early in our alpha stage we will welcome community nodes into our network, creating a decentralized network without a single point of trust.
![SPN community](https://safing.io/assets/img/spn/spn-community-web.png)
## Scope of Protection
The VPN technology is widespread and almost every computer and mobile phone supports connecting to a VPN natively.
When launching in April, the SPN will support Windows, with Linux following shortly after. We are planning on supporting Mac and Mobile in the future too, so everybody can enjoy easy privacy with their preferred operating system.
The VPN and SPN both tunnel connections from your whole computer, not only from your browser.
## Open Source
Many commercial VPN providers use bold and misleading marketing claims without any evidence to back it up. The code on their servers and mostly on their clients cannot be investigated. They demand your trust but give little to no proof in return.
The SPN however is open source / FOSS. We do not believe users should simply 'trust' companies when it comes to their privacy. Instead they should be able to inspect vendors and hold them accountable publicly. So feel free to check out [our Github](https://github.com/Safing/).
## Extra Mileage
After a connection arrives at the VPN server it still has to travel to the desired website. Depending on where your VPN is located, this may lead to a slower Internet experience. As an example, a person who is located in Europe may be connected to a US VPN server while loading a European website. This means the connection has to cross the Atlantic twice (EU -> US -> EU).
With the SPN however, every connection is calculated individually and leaves the network as near to the destination as possible. This means:
<br/>
- your connections are spread across the globe
- visibility in the 'open web' is minimized
- connections are not slowed down by having to go extra miles
![SPN community](https://safing.io/assets/img/spn/spn-community-web.png)
## Minor comments
**SPN enforces DoT**
While the open source SPN app sits at the kernel, it can do all sorts of amazing stuff. It will enforce all your DNS queries to use DNS over TLS (DoT), which also prevents your router from snooping on you. Later, it will also block malicious connections via an integrated Application Firewall.
**VPN - a Very Precarious Narrative**
There is [a great write up by Dennis Schubert](https://schub.wtf/blog/2019/04/08/very-precarious-narrative.html) showcasing the problem of todays commercial VPNs, both from a privacy and security perspective. Feel free to check it out, it also shows the valid use cases of VPNs.
**Pricing**
While VPN providers basically rebrand the same basic technologies widely available, we built every aspect of the network from the ground up, by hand. This is a huge investment and will require lots of resources to properly maintain and improve. But this is the only way to achieve real privacy. Thank you for enabling us to continue fighting for a brighter future!
## Conclusion
The VPN technology was built to securely connect two company locations. However, the SPN was developed from the ground up to protect user privacy. As a result the SPN can easily outperform VPNs in every aspect.

7
_sass/new/blog.scss Normal file
View file

@ -0,0 +1,7 @@
.post {
.content {
img {
width: 100%;
}
}
}

View file

@ -11,3 +11,4 @@
@import "new/cast";
@import "new/footer";
@import "new/mission";
@import "new/blog";