brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Thompson (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (BROOKLYN-374) The debian package should generate a private key
Date Thu, 20 Oct 2016 15:22:58 GMT

     [ https://issues.apache.org/jira/browse/BROOKLYN-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Justin Thompson updated BROOKLYN-374:
-------------------------------------
    Description: 
When the Debian + RPM + Vagrant package installs Brooklyn, it should generate a private key
for Brooklyn to use.

Currently it generates a private key but it is saved in memory which makes it difficult to
debug

post-install deb

  was:
When the Debian + RPM + Vagrant package installs Brooklyn, it should generate a private key
for Brooklyn to use.

Currently it generates a private key but it is saved in memory which makes it difficult to
debug


> The debian package should generate a private key
> ------------------------------------------------
>
>                 Key: BROOKLYN-374
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-374
>             Project: Brooklyn
>          Issue Type: Improvement
>    Affects Versions: 0.10.0
>            Reporter: Justin Thompson
>            Priority: Minor
>              Labels: debian
>
> When the Debian + RPM + Vagrant package installs Brooklyn, it should generate a private
key for Brooklyn to use.
> Currently it generates a private key but it is saved in memory which makes it difficult
to debug
> post-install deb



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message