i’ve finally found a vpn client that will allow connecting from an android phone to a microsoft windows server 2008-2019 environment over the sstp vpn protocol (vpn over ssl). the best part is that it is free, however not exactly so the app is cracked but fully functional. because you came here you can have it for free.
please make sure to support my site by clicking on an advertisement if you’ve found this site helpful in any way.
if you have only a single public ip to use and are already running something over tcp/443, fear not as i have proven you can use clever tricks such as pat (port-address translation) over nat (network-address translation). i basically reconfigure the listening port on the public side to another port such as tcp/444 in my case and then translate it to the proper destination port internally which is 443 obviously. here is a crewed diagram:
public internet > 18.104.22.168:444 [firewall] > 192.168.1.240:443 class-c style subnet.
the protocol is designed to secure online data and traffic, and is considered a much safer option for windows users than pptp or l2tp/ipsec.
how does the sstp protocol work?
sstp works by establishing a secure connection between a vpn client and a vpn server. basically, the protocol creates a secure “tunnel” between the client and the server, and all the data and traffic that passes through that tunnel is encrypted.
like pptp (point-to-point tunneling protocol), sstp transports ppp (point-to-point protocol) traffic, but – unlike pptp – it does it through a ssl/tls channel. because of that, sstp offers significantly more security than pptp since ssl/tls provides traffic integrity checking, secure key negotiation, and encryption.
due to the use of ssl/tls, sstp servers must be authenticated when a connection is established. sstp clients can be optionally authenticated too.
general technical details about the sstp vpn protocol
- sstp uses tcp port 443 – the same port used by https traffic.
- sstp is often compared to openvpn thanks to the high level of security it offers, and the fact that it can bypass nat firewalls.
- sstp doesn’t generally support site-to-site vpn tunnels. instead, it supports roaming since it uses ssl transmissions.
- sstp only supports user authentication. the protocol doesn’t support device or computer authentication.
what is secure socket tunneling protocol service?
the “secure socket tunneling protocol service” is a feature that was introduced with windows vista, and is also present on windows 7, windows 8, and windows 10. basically, it’s a service that offers support for the sstp vpn protocol, allowing it to connect to remote devices through vpn connections. if the service is disabled, you won’t be able to access remote servers using the sstp protocol.
you might also see that the “secure socket tunneling protocol service” is related to the “sstpsvc.dll” file. you should avoid messing with that file or deleting it since it provides the sstp service functionality on the windows platform.
how secure is the sstp protocol?
generally, sstp encryption is considered relatively safe to use when you’re browsing the web. many people even compare its security to the one offered by openvpn – most likely because it uses ssl and encapsulates data packets over https. what’s more, it can also use the aes encryption cipher, making it even safer.
however, it should be mentioned that there are two issues with sstp:
1. it’s susceptible to the “tcp meltdown” problem
without getting too technical, that’s an issue that might occur with the tcp connection that’s created within the vpn tunnel, and takes places over the tcp transmission protocol. basically, a tcp connection (the vpn one) contained within a tcp connection can result in a conflict between the two connections, which culminates in connectivity issues.
on its own, the “tcp meltdown” problem isn’t really a huge security flaw with sstp, but if you need round-the-clock online security or vpn encryption during critical moments (like when you’re downloading torrents, for example), it can be an annoying issue.
2. sstp is owned by microsoft
another problem some people have with the sstp vpn protocol is the fact that it’s closed-source and solely owned by microsoft. while there is no evidence to showcase that sstp was intentionally weakened or even cracked, it’s no secret that microsoft has closely collaborated with the nsa in the past – even going as far as offering them access to encrypted messages.
what’s more, microsoft belong to the prism surveillance program, and was even the program’s first partner. if you’re not familiar with prism, it’s a surveillance program run by the nsa which offers them access to emails, documents, and other user data that’s stored by major companies. so, it’s not far-fetched to think that the sstp protocol might (emphasis on “might”) have been compromised by the nsa during or after development.
overall, how good the security of the sstp vpn protocol is solely depends on how much you trust microsoft.
sstp vpn speed – what should you know?
sstp offers decent online speeds most of the time, though you might encounter some slowdowns if you don’t have enough bandwidth or a relatively strong cpu. don’t forget – sstp uses pretty strong encryption, and that can lower your online speeds, especially if a powerful encryption cipher is used too.
also, you should consider the fact that there are plenty of other factors that can influence the online speeds you get when using an sstp vpn connection.
sstp advantages and disadvantages
- sstp encryption offers a decent level of security, almost on par with openvpn (ssl 3.0 + 256-bit encryption).
- sstp is easy to configure on platforms it is built into.
- the sstp vpn protocol is very difficult to block because it uses tcp port 443 (the same one https uses).
- sstp offers good speeds if you have enough bandwidth.
- sstp is closed-source and solely owned by microsoft, a company that is well known to collaborate with the nsa.
- the sstp protocol is available on a limited number of platforms – windows, linux, android, and routers.
- sstp connections could be dropped if the network admin spots the sstp header (which is possible to do since the protocol doesn’t support authenticated web proxies).
- since sstp only works on tcp, it is susceptible to the “tcp meltdown” issue.
what is an sstp vpn?
an sstp vpn is a service offered by a vpn provider that gives you access to a ready-to-go sstp vpn connection. normally, you just need to download and install a vpn client, connect to a vpn server, and you’re good to go
ideally, you shouldn’t stick to a vpn provider that only offers you access to the sstp vpn protocol. it’s best to pick a provider who can offer you variety when it comes to choosing the vpn protocol you want to use.
sstp compared to other vpn protocols
here’s an in-depth overview showcasing how good or bad the sstp vpn protocol is compared to the other vpn protocols you can use. if you would like even more detail regarding the differences then see my other post called pptp vs l2tp vs openvpn vs sstp vs ikev2.
sstp vs. openvpn
security-wise, both vpn protocols are decent options since they can use strong encryption keys and ciphers, and also use ssl 3.0. but unlike sstp, openvpn is open-source and is not solely owned by microsoft. that makes it easier for online users to trust that the protocol offers reliable security with no potential loopholes.
besides that, openvpn can also use the udp transmission protocol alongside the tcp one which is used by sstp. as a result, you’re likely to get better online speeds with openvpn than with tcp. also, openvpn isn’t susceptible to the “tcp meltdown” issue mentioned above.
and while sstp can’t really be blocked by firewalls easily since it uses port 443 just like openvpn (the https port), it does have one weakness – the fact that it doesn’t support authenticated web proxies. why is that a problem? well, if sstp uses a non-authenticated web proxy, the administrator of a network could potentially detect sstp headers. in that situation, they could drop the connection if they want to.
openvpn is also available on more platforms than sstp. while it is convenient that sstp is natively built into windows operating systems, and thus can be easily set up, it can only be configured on routers, android, and linux. openvpn, on the other hand, can be set up on all those platforms, including many others (like windows xp, macos, ios, freebsd, openbsd, solaris, and netbsd.
oh, and openvpn could potentially be more stable than sstp when it comes to network changes. that’s because openvpn has the “float” command, which could ensure openvpn connections don’t drop when you switch networks.
sstp vs. ipsec
both protocols offer a pretty good level of security, though you might have to be a bit more careful when configuring the ipsec protocol since it’s easier to mess up the protection it offers if it’s not configured properly. on the plus side, ipsec works on more platforms than sstp, like macos, windows 2000, solaris, freebsd, openbsd, and netbsd.
also, ipsec is much easier to block with a firewall than sstp. since sstp uses tcp port 443 (the same port used by https), a network admin or isp can’t really block it without also blocking all other online activities. ipsec traffic, on the other hand, can be blocked if the network admin or isp blocks ip protocols 50 (which stops the encapsulating security payload offered by ipsec) and 51 (which would stop the authentication header used by ipsec). the same can happen if port 500 is blocked since it’s the port used for ipsec’s internet security association and key management protocol (isakmp).
in terms of speed, there’s a chance that sstp might be faster than ipsec because it can take ipsec longer to negotiate a vpn tunnel. a lot of online users have also been complaining, saying that ipsec tends to eat up a lot of resources – something that can further lower online speeds.
ipsec is normally paired with l2tp or ikev2, but you might see vpn providers who offer ipsec as a protocol on its own. overall, we’d recommend using sstp over ipsec if possible.
sstp vs. ikev2/ipsec
if you’re mostly interested in security, you should know that both sstp and ikev2/ipsec offer a similar level of protection. ikev2/ipsec might be a bit more trustworthy than sstp, though, since it’s not solely owned by microsoft. instead, it was developed by microsoft together with cisco. also, there are open-source implementations of ikev2 available online.
in terms of cross-platform compatibility, ikev2/ipsec has limited support just like sstp, but it still has an advantage since it also works on ios, macos, and blackberry platforms.
as for speed and stability, ikev2 might potentially be a bit faster than sstp since it uses udp, but it’s unfortunately also easier to block than sstp because it only uses udp port 500. if a network admin blocks it, ikev2/ipsec traffic is blocked altogether. sstp, however, uses tcp port 443, which is much harder to block. still, ikev2 has a very nice perk when it comes to stability – mobike (ikev2 mobility and multihoming), a feature that allows the protocol to seamlessly resist network changes without the connection being dropped.
in the end, ikev2/ipsec is only a better option than sstp if you use your mobile device a lot and travel often, or if you’d prefer an open-source alternative to sstp that’s easy to set up on windows platforms and blackberry devices.
sstp vs. l2tp/ipsec
generally, sstp is a much more secure option than l2tp/ipsec, though it is worth mentioning that some online users have an easier time placing their trust in l2tp/ipsec because it’s not solely developed by microsoft. however, l2tp/ipsec is easier blocked with a firewall than sstp, making it overall less reliable.
in terms of connection speeds, l2tp/ipsec is inferior to sstp because it uses double encapsulation – meaning it encrypts online traffic twice. there’s also a chance that l2tp/ipsec is more resource-intensive than sstp.
on the other hand, l2tp/ipsec is available on more platforms than sstp. what’s more, l2tp is even built into more devices and operating systems than sstp, which is only built into windows vista and higher.
if you were to choose between sstp and l2tp/ipsec, we’d say you’d be better off with sstp.
sstp vs. pptp
both sstp and pptp have been developed by microsoft, though pptp was developed by microsoft together with other companies. when it comes to security, sstp surpasses pptp because it offers better protection – especially since it has support for 256-bit encryption keys, while pptp can only has support for 128-bit keys.
normally, that wouldn’t be a huge issue for pptp users, but the main problem is with pptp’s own encryption – mppe – which is very flawed. also, it has been shown that the nsa can crack pptp traffic.
the only way pptp is better than sstp is when it comes to speed and availability. due to its poor encryption, pptp offers very fast connections. also, pptp is natively built into many platforms, though it is worth mentioning that – due to the protocol’s poor security – it might not continue to be natively included in future operating systems and devices. for example, pptp is no longer natively available on macos sierra and ios 10 (and newer versions).
sstp vs. softether
sstp and softether both seem to offer a decent level of security when it comes to high encryption and supported ciphers, but softether is simply more trustworthy because it’s open-source and because it isn’t owned by a company that’s been known to collaborate with the nsa. also, softether has a wide variety of security features that make it even stronger.
speed-wise, there’s a chance that softether is faster than sstp since it was programmed with fast throughput in mind. also, softether is allegedly 13 times faster than openvpn, and sstp speeds are often considered to be on a similar level to openvpn connection speeds.
now, it’s true that softether might be more difficult or inconvenient to set up than sstp. after all, sstp is natively built into windows platforms, so it can easily be configured with a few clicks. what’s more, if you use a third-party vpn service that offers softether connections, you’ll still need to download and install the softether software on your device.
on the other hand, softether works on more platforms than sstp, which is only available natively on windows operating systems, and can be manually configured on routers, android, and linux. softether works on all those platforms, and on other operating systems and devices like ios, freebsd, solaris, and macos.
another difference worth mentioning is the fact that the softether vpn server actually offers support for the sstp vpn protocol – alongside many other vpn protocols like openvpn, l2tp/ipsec, ipsec, and softether. an sstp vpn server doesn’t offer such flexibility.
overall, softether is a much better option than sstp – especially if you are looking for an open-source alternative.
sstp vs. wireguard
at the moment of writing of this article, wireguard is a very young vpn protocol, so not a lot of people trust it as much as they trust sstp – especially since it’s only in its experimental phase. still, the protocol is open-source, and it might end up offering better security than sstp since it uses state-of-the-art cryptography.
wireguard is also very likely faster than sstp if we are to believe the benchmarks on the protocol’s website that showcase how it has better throughput and less ping times than openvpn (a protocol sstp is often compared to in terms of speed).
at the moment, sstp is much more cross-platform compatible than wireguard since it’s available on linux (the only platform wireguard works on right now), and on windows, android, and routers. not to mention sstp is much easier to set up too.
as things stand right now, wireguard isn’t a better choice than sstp since it isn’t stable, nor is it fully secure. of course, if you just want to test it out, the protocol is a good option. in the future, wireguard might surpass sstp, though.
considering all that, is the sstp vpn protocol a good choice?
well, if you’re a windows user and can’t use openvpn or softether for various reasons, sstp is the next best vpn protocol in terms of security and reliability. of course, that depends on how much you trust the microsoft corporation. if you’re not particularly worried about that aspect, though, sstp could be a good choice then.
what is sstp? the main idea
sstp is a vpn protocol that encrypts online communications between a vpn client and a vpn server. it’s generally considered as secure as openvpn, but many online users don’t trust it fully because it’s solely owned by microsoft. also, the protocol has limited cross-platform compatibility, only being natively available on windows, and supporting configurations on android, linux, and routers.
overall, sstp is a good choice if you don’t mind the fact that it’s owned by microsoft, and that it’s not open-source. we generally recommend using it only when openvpn or softether are not valid options.