On Feb 19 2016, pisymbol <[email protected]> wrote:
> On Friday, February 19, 2016 at 4:58:04 PM UTC-5, Nikolaus Rath wrote:
>> Do you know why the verification fails? I assume you're not connecting
>> to something like S3 or Google Storage?
>
> That is correct. I am testing EMC's ECS product which implements S3.
>
>>> Other tools like s3fs, s3, etc. all allow skipping cert validation upon
>>> connecting via https.
>>
>> Because no one needed it and/or implemented it.
>>
>
> Would you consider a patch then to add it as a --backend-option then? That
> would seem most appropriate.
Not sure. Can you explain for what exactly this is useful? Why can't you
use plain HTTP for testing, or use your own CA if you want to test TLS?
Best,
-Nikolaus
(No Cc on replies please, I'm reading the list)
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
