brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From drigodwin <...@git.apache.org>
Subject [GitHub] brooklyn-docs pull request #129: Update: winrm connectivity limitations
Date Thu, 19 Jan 2017 11:08:35 GMT
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.
---

Mime
View raw message