[PATCH phosphor-rest-server] Add self-signed cert
Brad Bishop
bradleyb at fuzziesquirrel.com
Sat Nov 14 03:50:50 AEDT 2015
I just opened issue https://github.com/openbmc/phosphor-rest-server/issues/5 <https://github.com/openbmc/phosphor-rest-server/issues/5>
to track that.
Can we settle for this in the short term?
> On Nov 13, 2015, at 11:44 AM, Brad Bishop <bradleyb at fuzziesquirrel.com> wrote:
>
> At the moment we don’t have any cert at all. Baby steps...
>
>> On Nov 13, 2015, at 11:42 AM, Patrick Williams <patrick at stwcx.xyz> wrote:
>>
>> On Fri, Nov 13, 2015 at 10:10:24AM -0500, OpenBMC Patches wrote:
>>> Eventually will be running with SSL.
>>>
>>> https://github.com/openbmc/phosphor-rest-server/pull/4
>>>
>>> Brad Bishop (1):
>>> Add self-signed cert
>>>
>>> cert.pem | 48 ++++++++++++++++++++++++++++++++++++++++++++++++
>>
>> Why aren't we generating a new self-signed certificate on the machine
>> instead of including a global one here in the package? It seems like at
>> a minimum we should generate a new one on each build.
>>
>>> setup.py | 6 ++++--
>>> 2 files changed, 52 insertions(+), 2 deletions(-)
>>> create mode 100644 cert.pem
>>>
>>> --
>>> 2.6.3
>>>
>>>
>>> _______________________________________________
>>> openbmc mailing list
>>> openbmc at lists.ozlabs.org
>>> https://lists.ozlabs.org/listinfo/openbmc
>>
>> --
>> Patrick Williams
>> _______________________________________________
>> openbmc mailing list
>> openbmc at lists.ozlabs.org
>> https://lists.ozlabs.org/listinfo/openbmc
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20151113/8e23cd90/attachment.html>
More information about the openbmc
mailing list