We could also use the launcher, but it is a weak selector, and then, for more
complicated test cases when another terminal is already running, it could be
confused e.g. with the window title bar icon.

This required to make the polkit-related steps more generic: there's more
than one possible polkit prompt.

I suspect that doing this twice in a row might optimize things a little bit:
the second run takes the results of the first one into account.

This way, if a bug such as the one fixed in the previous commit is introduced
again, then we'll notice by running the automated test suite (as I did this
time), that will fail since the remote shell won't be running.

This script, like all other live-config hooks, is *sourced* by a live-config
script, so using `set -e', `set -u' or `return' in it makes all further such
scripts be skipped.

There's one known application that uses BOB:
 - it's no longer maintained; and
 - it would need more ports opened in ferm. It would be hard to justify
   this for a non-essential application which users are not likely to
   install themselves.

That being the case, let's close the port for BOB.

Although I2P will likely not ship any files which are named 'wrapper',
this will avoid any potential future clobbering.

The firewall rules should be enough.

No commit message

We were previously pointing to a certification that expired a while ago.