From 0d3ccb3a38b446f6513cf4fd63c4a3f0a78188a3 Mon Sep 17 00:00:00 2001 From: fr33domlover Date: Thu, 25 Oct 2018 20:28:06 +0000 Subject: [PATCH] Document running the SSH server on port 22 --- INSTALL.md | 10 ++++++++++ README.md | 5 +++-- 2 files changed, 13 insertions(+), 2 deletions(-) diff --git a/INSTALL.md b/INSTALL.md index a1e9bed..0576f0a 100644 --- a/INSTALL.md +++ b/INSTALL.md @@ -115,6 +115,16 @@ Build. $ stack build +For convenience, at least on actual deployments, you may wish to run the Vervis +SSH server on port 22, so that people don't have to specify a custom port. For +that to work, the user that runs the Vervis server needs to get permission to +bind to ports below 1024. There are several ways to do that. One of them is to +use file capabilities to give the Vervis executable the permission to bind to +such ports (if you prefer not to trust the code, try one of the other methods, +such as sudo): + + $ sudo setcap CAP_NET_BIND_SERVICE=+ep `stack exec which vervis` + Run. $ stack exec vervis diff --git a/README.md b/README.md index e025d8e..346437b 100644 --- a/README.md +++ b/README.md @@ -48,10 +48,11 @@ time of writing, I'll try to keep this little tutorial up to date)! links for creating these 5. You can browse all the projects and repos hosted on the instance. 6. Add the following to your `~/.ssh/config` file, or create it if doesn't - exist: + exist. To be honest I'm not sure it's still required, and haven't tested + yet. If you find that this step is unnecessary and everything works without + it, let me know :) Host dev.angeley.es - Port 5021 ControlMaster no ForwardAgent no ForwardX11 no