Hacker News new | ask | show | jobs
by ipozgaj 3645 days ago
One thing that I was pretty annoyed about while testing (server) beta and alpha was Cockpit web UI that is enabled by default. I know it's easy to disable it with `systemctl disable cocpit.socket`, but if you select "minimal/base install" you shouldn't get a full blown web UI management console installed and enabled by default.
2 comments
ohmarmalade 3644 days ago
I'm interested in this issue. As I understand it, Cockpit shouldn't be included in a minimal install. It is included in the default Fedora Server install.

If you like, join us on IRC in #cockpit on FreeNode, and we can work through this there.

link
catern 3645 days ago
It's installed by default but not running by default. So the only resource it consumes is a small amount of disk space, plus one socket so it autostarts if you try to use it (by connecting to example.com:8888 or whatever it is).
link
emidln 3645 days ago
If it's listening on a socket and spins up on a request sent to the port that socket is bound on, for all intents and purposes, it is running and enabled. This is the same behavior as old inetd-based servers.
link
ipozgaj 3645 days ago
Correct, if you try to open http://<hostname>:9090/ it will get automatically started. I'm not concerned about the resources it uses, I just don't like having services that I don't use installed and listening on ports in minimal install, especially on servers.
link
surge 3645 days ago
Isn't auto starting if someone hits the port effectively the same as having it running. At least from a security standpoint.
link
nothrabannosir 3645 days ago
Why did this get down voted ? Is it not true?
link