Ports that are being listened need to stop being indiscriminately changed

Lots of services use sockets internally on the system or otherwise.

I do not care if Keybase does as well.

I care that they are being changed seemingly randomly without any notification to the users.

Constantly changing hard-coded network connections is a bad thing. They conflict with other apps. The user should be allowed to, of their own volition, change which ports are being used via some form of config. This way they can decide which apps to listen to which ports.

In my case, I have a Cassandra cluster running on a number of my machines. This cluster is used via me to test out a variety of software and to also keep my own records. Cassandra has the ability to change ports, however, doing so would be a tedious process as I'd have to change the configuration across multiple machines.

Keybase started listening on port 7000 as of the release prior to the one that occurred today (08 May 2018). As of today's release it listens to 16423 instead, so my issue is resolved, but the problem as a whole still exists. The port that is being used should be configurable.

No files, tests, or entry points are named. Start by locating the Keybase service components that create listening sockets and their configuration handling, then determine how port selection is currently changed. Done means users can configure the relevant ports and the service no longer changes them unexpectedly, with tests covering the behavior.

Written by the indexing model from the issue text.