[OldWolf]

Is anyone able to do this? I have followed many online tuitorials but cant get any setups working. Have installed pptpd and setup the /etc/ppp.config as well as the /etc/ppp/chap-options and /etc/ppp/chap-secrets but mainly they fail upon checking the username and password. Once i managed to login and connect but had no internet access :S
Thnx OW

[OldWolf]

In case anyone was interested, i found this script useful for setting up a quick vpn server.
https://github.com/viljoviitanen/setup-simple-pptp-vpn
i added

Code:

echo vpninfo vpn:$PASS>vpninfo.txt

third line up from the end of the script; so it saves the details to text file.

[blackhatcat]

Just like the GitHub README says, PPTP has been known as a broken protocol for years and if you care at all about your security you should take the time to set up an OpenVPN server.

[Infinity]

Interesting, I normally just use a SSH tunnel, but this is helpful if you want to use openVPN, or similar.

[Eclipse]

Just like the GitHub README says, PPTP has been known as a broken protocol for years and if you care at all about your security you should take the time to set up an OpenVPN server.

This.

Interesting, I normally just use a SSH tunnel, but this is helpful if you want to use openVPN, or similar.

They both have their advantages. However, an SSH tunnel relies on your applications supporting SOCKS 5. A VPN has no such limitation.

[phyrrus9]

Just like the GitHub README says, PPTP has been known as a broken protocol for years and if you care at all about your security you should take the time to set up an OpenVPN server.

openvpn is by far the WORST vpn server I have ever seen. Just because a protocol is referred to as broken does not make it insecure. Anything when used properly can be secure.

[blackhatcat]

openvpn is by far the WORST vpn server I have ever seen. Just because a protocol is referred to as broken does not make it insecure. Anything when used properly can be secure.

PPTP is thoroughly broken.

MS-CHAPv1 was owned 15 years ago, its replacement MS-CHAPv2 was known to be just as weak and was eventually owned, not too long ago actually.

At this point nobody who cares in the least about the communications they intend to protect should be using it.
And it's not a matter of choosing someone's implementation over another; its most serious flaws are in the protocol design and cannot be fixed.