Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: drigodwin <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
References: <git-pr-129-brooklyn-docs@git.apache.org>
In-Reply-To: <git-pr-129-brooklyn-docs@git.apache.org>
Subject: [GitHub] brooklyn-docs pull request #129: Update: winrm connectivity limitations
Content-Type: text/plain
Message-Id: <20170119110835.B2FCDDFA85@git1-us-west.apache.org>
Date: Thu, 19 Jan 2017 11:08:35 +0000 (UTC)
archived-at: Thu, 19 Jan 2017 11:08:37 -0000

Github user drigodwin commented on a diff in the pull request:

    https://github.com/apache/brooklyn-docs/pull/129#discussion_r96837642
  
    --- Diff: guide/yaml/winrm/index.md ---
    @@ -515,11 +515,9 @@ Known Limitations
     
     ### Use of Unencrypted HTTP
     
    -Brooklyn is currently using unencrypted HTTP for WinRM communication. This means that the login credentials will be
    -transmitted in clear text.
    +By default Brooklyn is currently using unencrypted HTTP for WinRM communication. It does not support encrypted HTTP for WinRM.
     
    -In future we aim to improve Brooklyn to support HTTPS. However this requires adding support to the underlying 
    -WinRM library, and also involves certificate creation and verification.
    +HTTPS is supported but there is no mechanism of specifying certificates to trust to.
    --- End diff --
    
    What does this mean? If it's supported that implies it's usable.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---