Skip to content

Client should default to true for ssl verification #12

Open

Description

@cpenner461

We are currently defaulting verify=False when creating the StackdIO client. We should default that to True, and then if the user sets that to False, print a warning message, then suppress additional warnings that are coming from urllib3 (otherwise they are constantly spewed out).

Activity

  1. clarkperkins commented on Dec 17, 2014

    @clarkperkins
    Member

    @cpenner461 @WLPhoenix So interesting caveat to this, when you're using a stackdio server with http and NOT https, defaulting verify to true crashes the CLI, saying that the "certificate verify failed". I have to set verify to false to get plain http working.

  2. clarkperkins commented on Dec 17, 2014

    @clarkperkins
    Member

    Actually, turns out I must have changed my CLI to point to stackd.corp and not realized it. Now that I have it back on my own stackdio instance it works fine.

  3. WLPhoenix commented on Feb 2, 2015

    @WLPhoenix
    Contributor

    Should be fixed w/ #14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions