[
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
Recommend modifying the post-install Debian + RPM scripts
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
post-install deb
> 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
> Recommend modifying the post-install Debian + RPM scripts
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
