On Wed, Mar 4, 2020 at 6:12 PM Jonathan Aquilina
<[email protected]> 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 <[email protected]>
> Sent: Wednesday, 4 March 2020 16:43
> To: Development discussion for the Cockpit Project 
> <[email protected]>; Jonathan Aquilina 
> <[email protected]>
> 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
_______________________________________________
cockpit-devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedorahosted.org/archives/list/[email protected]

Reply via email to