Suggestion for changing cockpit default session timeout
by Gal Zaidman
Hi Cockpit developers,
I saw that on cockpit-209 Session timeouts were added with the default to
15 minutes of inactivity (https://cockpit-project.org/blog/cockpit-209.html
).
I think that this change is problematic because:
1. The timeout is very short and it can cause unexpected behavior to users
and cockpit packages.
2. The timeout can only be configured in the /etc/cockpit.conf file, so it
is hard for packages to configure it to fit to their behavior.
For example,
we created a package for installing ovirt with cockpit UI, that
installation can take a lot of time, it has different phases and
logging out in the middle can cause problems.
We prefer to avoid editing /etc/cockpit.conf because we don't want to run
over user configuration (what to do when there is already cockpit.conf
present?)
I want to suggest:
1. Raising the timeout to 2 hours of inactivity, this seems reasonable.
2. Provide a more flexible way of configuring the timeout, with an option
to the manifest.json package file and/or with a cockpit API call.
Thanks
3 years, 10 months
Development configuration for Cockpit Plugin
by Gal Zaidman
Hi cockpit developers,
I'm new to cockpit and working on creating a new plugin, which should
enable oVirt users to install oVirt hosted engine through cockpit UI.
I'm at the beginning of the project and trying to create a proper
development environment.
I'm using react and want to work with webserver I need a special
configuration on cockpit side which I'm hoping you can help me with.
On my local env I installed cockpit and cloned the starter-kit, created
a link to base1 directory, and added this script line to my index.html file:
<script type="text/javascript" src="../base1/cockpit.js"></script>
My app can import cockpit, now I need to configure cockpit to interact with
a local running VM instead of my own PC.
I want that the cockpit service which is running local on my machine
connect to a cockpit bridge running on a local VM as a primary server,
basically:
[image: image.png]
The end result I want to achieve is that when I'm developing my plugin I
will use webserver and only see the plugin windows (without the cockpit UI)
and each interaction with cockpit will be triggered on a remote VM running
cockpit, this way I will not have to refresh my page to see changes in the
UI.
Can you help me understand the required configuration for cockpit ?
4 years, 2 months
Re: Cockpit installed on local dev machine
by Stef Walter
On Wed, Mar 4, 2020 at 6:12 PM Jonathan Aquilina
<jaquilina(a)eagleeyet.net> wrote:
> I am a bit lost if I am using my local dev machine with cockpit to access a remote server how secure is it to keep it over http and not move to https?
Cockpit can use SSH to access a remote server. If you're using Cockpit
locally (via localhost) to accomplish that, it's secure use plain HTTP
on the local machine.
Here's some documentation about how that works:
https://cockpit-project.org/guide/latest/feature-machines
Cheers,
Stef
> -----Original Message-----
> From: Stef Walter <swalter(a)redhat.com>
> Sent: Wednesday, 4 March 2020 16:43
> To: Development discussion for the Cockpit Project <cockpit-devel(a)lists.fedorahosted.org>; Jonathan Aquilina <jaquilina(a)eagleeyet.net>
> Subject: Re: Cockpit installed on local dev machine
>
> On 22.02.20 05:35, Jonathan Aquilina wrote:
> > Hi All,
> >
> >
> >
> > I have a dev laptop which I have installed cockpit on. My question
> > even though I have it installed on a local laptop would you guys still
> > recommend I setup https on it if I plan on connecting to remote machines?
>
> If you plan on connecting *from* remote machines to your local laptop, then setting up https on it makes sense.
>
> However if you're purely using Cockpit on your local laptop to connect out to other machines (either from the Login screen, or from the multi-machine Dashboard) then it's not necessary to use https.
>
> In fact when accessed locally on localhost (127.0.0.1/8), Cockpit will allow you to use plain http, rather than forcing a redirect to https like it typically does.
>
> Cheers,
>
> Stef
>
--
Stef Walter (he / his)
Linux Engineering
Red Hat
4 years, 2 months
Re: Cockpit installed on local dev machine
by Stef Walter
On 22.02.20 05:35, Jonathan Aquilina wrote:
> Hi All,
>
>
>
> I have a dev laptop which I have installed cockpit on. My question even
> though I have it installed on a local laptop would you guys still
> recommend I setup https on it if I plan on connecting to remote machines?
If you plan on connecting *from* remote machines to your local laptop,
then setting up https on it makes sense.
However if you're purely using Cockpit on your local laptop to connect
out to other machines (either from the Login screen, or from the
multi-machine Dashboard) then it's not necessary to use https.
In fact when accessed locally on localhost (127.0.0.1/8), Cockpit will
allow you to use plain http, rather than forcing a redirect to https
like it typically does.
Cheers,
Stef
4 years, 2 months
