Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
	Khem Raj <raj.khem@gmail.com>,
	 openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] send-error-report: Use https instead of http protocol
Date: Mon, 04 Mar 2019 09:23:42 +0000	[thread overview]
Message-ID: <12b1452d894058e0a03398ae65b0f52deaeb9182.camel@linuxfoundation.org> (raw)
In-Reply-To: <e0f4b1c8-54f9-63c9-b08b-147243ebe1ce@windriver.com>

On Mon, 2019-03-04 at 15:50 +0800, Robert Yang wrote:
> Hi Khem,
> 
> We have an internal error web server, this patch breaks it:
> 
> You're accessing the development server over HTTPS, but it only
> supports HTTP
> 
> So I tried to use runsslserver, but it doesn't work either since the
> host is
> Ubuntu 14.04 (python 2.7.6):
> 
> $ python manage.py runsslserver
> 
> [snip]
>      ssl_version=ssl.PROTOCOL_TLSv1_2,
> AttributeError: 'module' object has no attribute 'PROTOCOL_TLSv1_2'
> 
> This is because python is old.
> 
> I think that make it default to https would make the server harder to
> set up,
> so is it possible to:
> 
> * Make it default to http, and add an option such as --https (or --
> ssl) for https
> 
> Or:
> 
> * Add an option such as --no-ssl to make it use http.
> 
> I prefer the first one since https server is harder to setup than
> http in django. I can work on it if no objections.

At this point the project does require python3 so python2 being old
shouldn't be a reason to be changing this.

The project also needs to be seen to encourage secure practises so I
think https should be the default but adding an option to use http
should be ok.

Cheers,

Richard





  reply	other threads:[~2019-03-04  9:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 18:13 [PATCH] send-error-report: Use https instead of http protocol Khem Raj
2019-03-04  7:50 ` Robert Yang
2019-03-04  9:23   ` Richard Purdie [this message]
2019-03-04 10:02     ` Robert Yang
2019-03-04 10:26       ` Richard Purdie
2019-03-04 10:33         ` Robert Yang
2019-03-05  8:54           ` Robert Yang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12b1452d894058e0a03398ae65b0f52deaeb9182.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox