Skip to content

Add "depth" as a valid SSL option #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 3, 2017

Conversation

tianon
Copy link
Member

@tianon tianon commented Apr 3, 2017

Closes #144

@tianon
Copy link
Member Author

tianon commented Apr 3, 2017

This should be usable via RABBITMQ_SSL_DEPTH=2, as an example.

@tianon
Copy link
Member Author

tianon commented Apr 3, 2017

Here's an example generated configuration: (obviously using a bogus cert file, because I just wanted to test the config generation 😇)

[ { rabbit, [
	{ loopback_users, [ ] },
	{ tcp_listeners, [ ] },
	{ ssl_listeners, [ 5671 ] },
	{ ssl_options, [
		{ cacertfile, "/etc/passwd" },
		{ certfile, "/etc/passwd" },
		{ depth, 2 },
		{ fail_if_no_peer_cert, true },
		{ keyfile, "/etc/passwd" },
		{ verify, verify_peer }
	] },
	{ hipe_compile, false }
] } ].

@tianon tianon merged commit c814069 into docker-library:master Apr 3, 2017
@tianon tianon deleted the ssl-depth branch April 3, 2017 18:21
@michaelklishin
Copy link
Collaborator

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants