-
Notifications
You must be signed in to change notification settings - Fork 8
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
No option to ignore self-signed certs #5
Comments
I never tested this with a self-signed cert. Let me dig around and see what I can come up with |
Thanks @kacole2. I'm not much of a node.js person but it doesn't look too promising: http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Config.html#constructor-property Which would suggest for testing purposes either (a) use a valid signed cert or (b) have a mechanism which allows for the option of SSL or not ala:
|
p.s. I'm in favour of adding (b) :D |
i'll have to get access to a self-signed cert environment to test it out and see if i can pipe in the sslEnabled ⇒ Boolean (readwrite) variable. In the mean time, does Eucalyptus have a non-SSL endpoint? you can try using |
Yup, that works just fine, thanks for the pointer there. Ref self-signed: aws.NodeHttpClient.sslAgent.options.rejectUnauthorized = false |
Hi, I'm using this against s3compatible storage (Eucalyptus) and have a cloud configured with SSL for the endpoints but I'm using a self-signed cert. I get this error:
# s3motion -b --client emeacloud Could not retrieve buckets. Error: NetworkingError: DEPTH_ZERO_SELF_SIGNED_CERT
Looking at the options list it seems there is no way to tell the tool to ignore a self-signed cert (or accept it regardless).
The text was updated successfully, but these errors were encountered: