Hi,
we just changed the port that Cockpit listens on by default. It's just nicer.
You need to download new images for the integration tests, because the firewall configuration in them have changed. The VERIFY script should do this automatically (via testsuite-prepare).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
On 05/06/2014 11:29 AM, Marius Vollmer wrote:
Hi,
we just changed the port that Cockpit listens on by default. It's just nicer.
Very much indeed! This will make it a lot easier to remember what to dial in to.
Looks like 1001 is not registered to any known service[1]. Probably would be a good idea to contact IANA and get this made official.
[1] http://www.iana.org/assignments/service-names-port-numbers/service-names-por...
On 06.05.2014 13:43, Stephen Gallagher wrote:
On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
On 05/06/2014 11:29 AM, Marius Vollmer wrote:
Hi,
we just changed the port that Cockpit listens on by default. It's just nicer.
Very much indeed! This will make it a lot easier to remember what to dial in to.
Looks like 1001 is not registered to any known service[1]. Probably would be a good idea to contact IANA and get this made official.
Would that work? Or would we just be treated as a website, and told to go port 80?
Stef
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Tue 06 May 2014 07:50:46 AM EDT, Stef Walter wrote:
On 06.05.2014 13:43, Stephen Gallagher wrote:
On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
On 05/06/2014 11:29 AM, Marius Vollmer wrote:
Hi,
we just changed the port that Cockpit listens on by default. It's just nicer.
Very much indeed! This will make it a lot easier to remember what to dial in to.
Looks like 1001 is not registered to any known service[1]. Probably would be a good idea to contact IANA and get this made official.
Would that work? Or would we just be treated as a website, and told to go port 80?
No, I think it makes perfect sense to have a separate address for a management service. We don't necessarily have to reserve it for Cockpit alone, but perhaps requisition it for "HTTP-based system management consoles".
Multiplexing port 80 is a hack of the worst kind and I think we can make that argument.
On 06.05.2014 13:56, Stephen Gallagher wrote:
On Tue 06 May 2014 07:50:46 AM EDT, Stef Walter wrote:
On 06.05.2014 13:43, Stephen Gallagher wrote:
On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
On 05/06/2014 11:29 AM, Marius Vollmer wrote:
Hi,
we just changed the port that Cockpit listens on by default. It's just nicer.
Very much indeed! This will make it a lot easier to remember what to dial in to.
Looks like 1001 is not registered to any known service[1]. Probably would be a good idea to contact IANA and get this made official.
Would that work? Or would we just be treated as a website, and told to go port 80?
No, I think it makes perfect sense to have a separate address for a management service. We don't necessarily have to reserve it for Cockpit alone, but perhaps requisition it for "HTTP-based system management consoles".
Multiplexing port 80 is a hack of the worst kind and I think we can make that argument.
Sounds good. Are you interested in writing the IANA?
Stef
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 05/06/2014 07:57 AM, Stef Walter wrote:
On 06.05.2014 13:56, Stephen Gallagher wrote:
On Tue 06 May 2014 07:50:46 AM EDT, Stef Walter wrote:
On 06.05.2014 13:43, Stephen Gallagher wrote:
On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
On 05/06/2014 11:29 AM, Marius Vollmer wrote:
Hi,
we just changed the port that Cockpit listens on by default. It's just nicer.
Very much indeed! This will make it a lot easier to remember what to dial in to.
Looks like 1001 is not registered to any known service[1]. Probably would be a good idea to contact IANA and get this made official.
Would that work? Or would we just be treated as a website, and told to go port 80?
No, I think it makes perfect sense to have a separate address for a management service. We don't necessarily have to reserve it for Cockpit alone, but perhaps requisition it for "HTTP-based system management consoles".
Multiplexing port 80 is a hack of the worst kind and I think we can make that argument.
Sounds good. Are you interested in writing the IANA?
Sure, I'll write something up later today.
On 05/06/2014 08:24 AM, Stephen Gallagher wrote:
On 05/06/2014 07:57 AM, Stef Walter wrote:
On 06.05.2014 13:56, Stephen Gallagher wrote:
On Tue 06 May 2014 07:50:46 AM EDT, Stef Walter wrote:
On 06.05.2014 13:43, Stephen Gallagher wrote:
On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
On 05/06/2014 11:29 AM, Marius Vollmer wrote: > Hi, > > we just changed the port that Cockpit listens on by > default. It's just nicer.
Very much indeed! This will make it a lot easier to remember what to dial in to.
Looks like 1001 is not registered to any known service[1]. Probably would be a good idea to contact IANA and get this made official.
Would that work? Or would we just be treated as a website, and told to go port 80?
No, I think it makes perfect sense to have a separate address for a management service. We don't necessarily have to reserve it for Cockpit alone, but perhaps requisition it for "HTTP-based system management consoles".
Multiplexing port 80 is a hack of the worst kind and I think we can make that argument.
Sounds good. Are you interested in writing the IANA?
Sure, I'll write something up later today.
cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
Anyone running this on Rawhide, getting any AVC messages, nothing in the cockpit policy to allow it to listen on any ports.
On 05/06/2014 09:03 AM, Stef Walter wrote:
On 06.05.2014 14:55, Daniel J Walsh wrote:
Anyone running this on Rawhide, getting any AVC messages, nothing in the cockpit policy to allow it to listen on any ports.
We use systemd socket activation in Fedora. Does it still need to be in the policy in that case?
Stef
cockpit-devel mailing list cockpit-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/cockpit-devel
Good question, I don't know. But I would guess it does, because anyone using cockpit on rawhide would probably see AVC messages.
cockpit-devel@lists.fedorahosted.org
-
Andreas Nilsson -
Daniel J Walsh -
Marius Vollmer -
Stef Walter -
Stephen Gallagher