vpn - How to set up an SSTP Server

  • spambas

    Is there a way to set up a linux based, preferably ubuntu, SSTP server?

    I know there is a SSTP client available on sourceforge, but I can't find a server.

    To be clear: I do NOT want openVPN, I want SSTP

  • Answers
  • Anonymous

    Yes, there is a Linux (and Windows/Mac) based SSTP (and lot more) VPN Server. It is called SoftEther VPN (http://www.softether.org). Best of off, it is free. Granted, there are couple of limitations with the free version (for example, cannot use external authentication, client certificates etc.)

    In general, it seems to work fine. It is easy to install, use and manage. Has decently good documentation. Has quite a few options. I used it on Ubuntu 13.04 release. It does serve my SSTP server requirements.

  • Related Question

    ssh - how to set up a ubuntu server to be (securely) available from internet?
  • Steve B

    (apologize in advance, I'm a pro-windows newly converted to ubuntu... if my questions are obvious, please tell me).

    I want to build a ubuntu server continuously connected to the internet. I own only IP address. The main purpose of the server is to serve as a source code controller (probably git or svn... haven't choose yet), but also some occasional other uses (file sharing with family or customer, personal backup, host of web applications I may wrote, etc. I also would like to be able to access at any time to the computer to administer it, even behind some customer's proxy that allows only http or https

    What are the standard steps to achieve that ?

    • My first though is to set up openssh server. Is it possible (and "quite" secure) to open it to the internet on standard port (i.e. customer firewall/proxy compatible).
    • Is it possible to set up a VPN server, that is run from a webpage plugin (also hosted by the server)?
    • as I have only one IP address (IP V4 and IPV 6 actually, but I don't think IP V6 address will be accessible from customers network by now), can I make apache and other server software to coexists on the same standard ports ?

    thanks in advance ;)

  • Related Answers
  • Lekensteyn

    When properly set-up OpenSSH is safe, even on the standard port. Moving it away from the standard port saves you from your log files being filled up by unauthorized login attempts. More details on the end.

    It's very dangerous to access your server if you do not have control over the computer which should connect to your server (which I think that's the reason why you need to use a browser plugin)

    OpenVPN can be set up to share TCP ports with a HTTP/HTTPS server, from its manual page:

    --port-share host port
    When run in TCP server mode, share the OpenVPN port with another application, such as an HTTPS server. If OpenVPN senses a connection to its port which is using a non-OpenVPN protocol, it will proxy the connection to the server at host:port. Currently only designed to work with HTTP/HTTPS, though it would be theoretically possible to extend to other protocols such as ssh.

    It's not recommended to use OpenVPN with a TCP connection due to its overhead (TCP 3-way handshake). If you've no choice, you could give it a go.

    Using OpenVPN, you can avoid any port restriction imposed on you and secure the connection. Please refer to How do I setup OpenVPN so I can securely use the internet from an unsecured hotspot? for a guide on setting up OpenVPN.

    You cannot share ports unless an application supports it (like OpenVPN), so I must disappoint you on that.

    SSH server

    Password-based authentication without limiting connection attempts is asking for trouble. Because of that, it's preferred to use key-based authentication and disable password-based authentication altogether.

    1. Install openssh-serverInstall openssh-server by running sudo apt-get install openssh-server
    2. Disable password-based authentication by editing the configuration file /etc/ssh/sshd_config. To start editing, run sudo nano /etc/ssh/sshd_config. Find the line #PasswordAuthentication yes and change it to PasswordAuthentication no. By default, SSH listens on port 22. If you want to change it, use a port below 1024 for security reasons. (change the line with Port 22)
    3. For extra security, you can configure a list of users who are allowed to login. Add a line with:

      AllowUsers someuser

      Replace someuser by the username of the account that is allowed to login. Multiple usernames should be separated by a space.

    4. Generate a key on your computer using the command ssh-keygen -t rsa. Enter whatever values you want and choose a secure passphrase.
    5. Copy the contents of ~/.ssh/id_rsa.pub file to /home/someuser/.ssh/authorized_keys file on your server. someuser is the user that should be allowed to login. (it's a single line that should be copied, never copy the contents of a file that starts with -----BEGIN RSA PRIVATE KEY
    6. Reload the configuration of your SSH server:

      sudo reload ssh
    7. If you're remotely accessing your server over SSH, verify that you can make a new SSH connection to avoid locking yourself out.