Skip to content
This repository has been archived by the owner on Aug 29, 2018. It is now read-only.

Mcollective TLS uses SSLv3 after reboot #381

Open
andrewklau opened this issue Feb 5, 2015 · 2 comments
Open

Mcollective TLS uses SSLv3 after reboot #381

andrewklau opened this issue Feb 5, 2015 · 2 comments

Comments

@andrewklau
Copy link

After a reboot, mcollective tries to connect to activemq through SSLv3

As its not part of an available protocol it will error. Leaving hard to trace errors unless you explicitly check the connection. Removing the protocol restriction resumes the connection.

I'm not sure why this happens but thought I should report it in case someone else sees this. I'm still away for a few more days so can't investigate further.
@andrewklau
Copy link
Author

Issue happened after updating openssl around early Jan, getting the latest version of ruby193-mcollective has resolved this issue.

@andrewklau andrewklau reopened this Apr 18, 2015
@andrewklau
Copy link
Author

Still happens after reboot, seems upgrading/downgrading solves the issue but after a reboot some settings are lost. Can't seem to isolate what's doing this..

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@andrewklau