Skip to content
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

ssl not activated #1350

Open
j4b3r opened this issue May 15, 2018 · 2 comments
Open

ssl not activated #1350

j4b3r opened this issue May 15, 2018 · 2 comments

Comments

@j4b3r
Copy link

j4b3r commented May 15, 2018

Hello

i use this setting in my riak-cs advanced.config:
[
{ssl, [
{certfile, "/etc/letsencrypt/live//cert.pem"},
{keyfile, "/etc/letsencrypt/live/
*/privkey.pem"},
{cacertfile, "/etc/letsencrypt/live/*****/chain.pem"}
]}
].

after restart riak-cs
ssl not activated
i use default ssl files too but ssl not activated :
[
{ssl, [
{certfile, "/etc/riak-cs/cert.pem"},
{keyfile, "/etc/riak-cs/key.pem"}
]}
].

@j4b3r j4b3r changed the title ئئ« ssl not activated May 15, 2018
@Bob-The-Marauder
Copy link

Please can you explain in more detail what you mean by "not activated"? How are you testing it?

@recursionbane
Copy link

I ran into this as well, and it seems the cacertfile is not optional.
For debug purposes, you can try these insecure settings:

## Measures were added to Riak 1.2 to counteract cross-site scripting and request-forgery attacks. Some reverse proxies cannot remove the Referer header and make serving data directly from Riak impossible. Turning this setting to off disables this security check.
secure_referer_check = off
## If you are using certificate-based authentication, Riak will check the certificate revocation list (CRL) of connecting clients’ certificate by default. To disable this behavior, set the check_crl parameter to off
check_crl = off

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

No branches or pull requests

3 participants