brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BROOKLYN-505) Amazon provisioning fails with "Illegal key size"
Date Fri, 26 May 2017 14:52:04 GMT

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

Aled Sage resolved BROOKLYN-505.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.12.0

Fix is just in docs; no code changes were required.

> Amazon provisioning fails with "Illegal key size"
> -------------------------------------------------
>
>                 Key: BROOKLYN-505
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-505
>             Project: Brooklyn
>          Issue Type: Bug
>    Affects Versions: 0.11.0
>            Reporter: Svetoslav Neykov
>             Fix For: 0.12.0
>
>
> Provisioning to Amazon with minimal location selects the image {{
> RightImage_CentOS_7.0_x64_v14.2.1_HVM_EBS}}. Later provisioning fails with {{Exhausted
available authentication methods}} error.
> Just before each failure the debug logs show
> {noformat}
> 2017-05-18 12:36:23,551 WARN   73 n.s.s.DefaultConfig [user thread 1] Illegal key size
> 2017-05-18 12:36:23,552 WARN   73 n.s.s.DefaultConfig [user thread 1] Illegal key size
or default parameters
> 2017-05-18 12:36:23,552 WARN   73 n.s.s.DefaultConfig [user thread 1] Disabling high-strength
ciphers: cipher strengths apparently limited by JCE policy
> {noformat}
> The workaround is to install the "high strength ciphers" extension if using Oracle Java
or move to OpenJDK which has those included.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message