train-winrm 0.2.3 → 0.2.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/LICENSE +201 -0
- data/lib/train-winrm/version.rb +1 -1
- metadata +3 -5
- data/Gemfile +0 -26
- data/README.md +0 -105
- data/train-winrm.gemspec +0 -44
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: fc1d41b57d545b68f13f61570bc2ea17e3a4ebf9347350107ec6c978325eaaf7
|
4
|
+
data.tar.gz: 88a024c773ae636e48510d1073407531a0fcd80b0442978ce718930f351bfac8
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 18cf8f0aee537e44d253bc97f0a55d1058d5958b80345fb0386d9a0db04ef6d762e88f75e9f8d51a90739fde3e3ed06261bc53c57d1b67809e0d7df09ba9e2e5
|
7
|
+
data.tar.gz: 2237f866a2f1070e4fb7acb3f46327991ce2a1ce15508fea52b8ac59e21e410e6dd7333f73a418423a040f11dd61a423d179409701ce4b79f48b78b9d88b4f26
|
data/LICENSE
ADDED
@@ -0,0 +1,201 @@
|
|
1
|
+
Apache License
|
2
|
+
Version 2.0, January 2004
|
3
|
+
http://www.apache.org/licenses/
|
4
|
+
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
6
|
+
|
7
|
+
1. Definitions.
|
8
|
+
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
11
|
+
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
13
|
+
the copyright owner that is granting the License.
|
14
|
+
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
16
|
+
other entities that control, are controlled by, or are under common
|
17
|
+
control with that entity. For the purposes of this definition,
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
19
|
+
direction or management of such entity, whether by contract or
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
22
|
+
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
24
|
+
exercising permissions granted by this License.
|
25
|
+
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
27
|
+
including but not limited to software source code, documentation
|
28
|
+
source, and configuration files.
|
29
|
+
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
31
|
+
transformation or translation of a Source form, including but
|
32
|
+
not limited to compiled object code, generated documentation,
|
33
|
+
and conversions to other media types.
|
34
|
+
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
36
|
+
Object form, made available under the License, as indicated by a
|
37
|
+
copyright notice that is included in or attached to the work
|
38
|
+
(an example is provided in the Appendix below).
|
39
|
+
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
46
|
+
the Work and Derivative Works thereof.
|
47
|
+
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
49
|
+
the original version of the Work and any modifications or additions
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
61
|
+
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
64
|
+
subsequently incorporated within the Work.
|
65
|
+
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
72
|
+
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
78
|
+
where such license applies only to those patent claims licensable
|
79
|
+
by such Contributor that are necessarily infringed by their
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
82
|
+
institute patent litigation against any entity (including a
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
85
|
+
or contributory patent infringement, then any patent licenses
|
86
|
+
granted to You under this License for that Work shall terminate
|
87
|
+
as of the date such litigation is filed.
|
88
|
+
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
91
|
+
modifications, and in Source or Object form, provided that You
|
92
|
+
meet the following conditions:
|
93
|
+
|
94
|
+
(a) You must give any other recipients of the Work or
|
95
|
+
Derivative Works a copy of this License; and
|
96
|
+
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
98
|
+
stating that You changed the files; and
|
99
|
+
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
102
|
+
attribution notices from the Source form of the Work,
|
103
|
+
excluding those notices that do not pertain to any part of
|
104
|
+
the Derivative Works; and
|
105
|
+
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
108
|
+
include a readable copy of the attribution notices contained
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
111
|
+
of the following places: within a NOTICE text file distributed
|
112
|
+
as part of the Derivative Works; within the Source form or
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
114
|
+
within a display generated by the Derivative Works, if and
|
115
|
+
wherever such third-party notices normally appear. The contents
|
116
|
+
of the NOTICE file are for informational purposes only and
|
117
|
+
do not modify the License. You may add Your own attribution
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
120
|
+
that such additional attribution notices cannot be construed
|
121
|
+
as modifying the License.
|
122
|
+
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
124
|
+
may provide additional or different license terms and conditions
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
128
|
+
the conditions stated in this License.
|
129
|
+
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
133
|
+
this License, without any additional terms or conditions.
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
135
|
+
the terms of any separate license agreement you may have executed
|
136
|
+
with Licensor regarding such Contributions.
|
137
|
+
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
140
|
+
except as required for reasonable and customary use in describing the
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
142
|
+
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
152
|
+
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
158
|
+
incidental, or consequential damages of any character arising as a
|
159
|
+
result of this License or out of the use or inability to use the
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
162
|
+
other commercial damages or losses), even if such Contributor
|
163
|
+
has been advised of the possibility of such damages.
|
164
|
+
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
168
|
+
or other liability obligations and/or rights consistent with this
|
169
|
+
License. However, in accepting such obligations, You may act only
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
174
|
+
of your accepting any such warranty or additional liability.
|
175
|
+
|
176
|
+
END OF TERMS AND CONDITIONS
|
177
|
+
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
179
|
+
|
180
|
+
To apply the Apache License to your work, attach the following
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
182
|
+
replaced with your own identifying information. (Don't include
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
184
|
+
comment syntax for the file format. We also recommend that a
|
185
|
+
file or class name and description of purpose be included on the
|
186
|
+
same "printed page" as the copyright notice for easier
|
187
|
+
identification within third-party archives.
|
188
|
+
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
190
|
+
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
192
|
+
you may not use this file except in compliance with the License.
|
193
|
+
You may obtain a copy of the License at
|
194
|
+
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
196
|
+
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
200
|
+
See the License for the specific language governing permissions and
|
201
|
+
limitations under the License.
|
data/lib/train-winrm/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: train-winrm
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.2.
|
4
|
+
version: 0.2.4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Chef InSpec Team
|
8
8
|
autorequire:
|
9
9
|
bindir: bin
|
10
10
|
cert_chain: []
|
11
|
-
date: 2019-
|
11
|
+
date: 2019-09-04 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: winrm
|
@@ -46,13 +46,11 @@ executables: []
|
|
46
46
|
extensions: []
|
47
47
|
extra_rdoc_files: []
|
48
48
|
files:
|
49
|
-
-
|
50
|
-
- README.md
|
49
|
+
- LICENSE
|
51
50
|
- lib/train-winrm.rb
|
52
51
|
- lib/train-winrm/connection.rb
|
53
52
|
- lib/train-winrm/transport.rb
|
54
53
|
- lib/train-winrm/version.rb
|
55
|
-
- train-winrm.gemspec
|
56
54
|
homepage: https://github.com/inspec/train-winrm
|
57
55
|
licenses:
|
58
56
|
- Apache-2.0
|
data/Gemfile
DELETED
@@ -1,26 +0,0 @@
|
|
1
|
-
# encoding: utf-8
|
2
|
-
|
3
|
-
source "https://rubygems.org"
|
4
|
-
|
5
|
-
# This is a Gemfile, which is used by bundler
|
6
|
-
# to ensure a coherent set of gems is installed.
|
7
|
-
# This file lists dependencies needed when outside
|
8
|
-
# of a gem (the gemspec lists deps for gem deployment)
|
9
|
-
|
10
|
-
# Bundler should refer to the gemspec for any dependencies.
|
11
|
-
gemspec
|
12
|
-
|
13
|
-
# Remaining group is only used for development.
|
14
|
-
group :development do
|
15
|
-
# Depend on this here, not in the gemspec - to avoid having to have
|
16
|
-
# client applications induce circular dependencies
|
17
|
-
gem "train-core", "~> 3.0"
|
18
|
-
gem "bundler"
|
19
|
-
gem "byebug"
|
20
|
-
gem "m"
|
21
|
-
gem "minitest"
|
22
|
-
gem "mocha"
|
23
|
-
gem "pry"
|
24
|
-
gem "rake"
|
25
|
-
gem "chefstyle"
|
26
|
-
end
|
data/README.md
DELETED
@@ -1,105 +0,0 @@
|
|
1
|
-
# train-winrm - Train Plugin for connecting to Windows via Remote Management
|
2
|
-
|
3
|
-
* **Project State: Active**
|
4
|
-
* **Issues Response SLA: 3 business days**
|
5
|
-
* **Pull Request Response SLA: 3 business days**
|
6
|
-
|
7
|
-
This plugin allows applications that rely on Train to communicate with the WinRM API. For example, you could use this to audit Windows Server 2016 machines.
|
8
|
-
|
9
|
-
This plugin relies on the `winrm` and `winrm-fs` gems for implementation.
|
10
|
-
|
11
|
-
Train itself has no CLI, nor a sophisticated test harness. Chef InSpec does have such facilities, so installing Train plugins will require a Chef InSpec installation. You do not need to use or understand Chef InSpec.
|
12
|
-
|
13
|
-
Train plugins may be developed without a Chef InSpec installation.
|
14
|
-
|
15
|
-
## To Install this as a User
|
16
|
-
|
17
|
-
### ChefDK Installation
|
18
|
-
|
19
|
-
After August 2019, this plugin will be distributed with ChefDK; you do not need to install it separately.
|
20
|
-
|
21
|
-
### Manual Installation using `inspec plugin install`
|
22
|
-
|
23
|
-
Train plugins are distributed as gems. You may choose to manage the gem yourself, but if you are an Chef InSpec user, Chef InSpec can handle it for you.
|
24
|
-
|
25
|
-
You will need Chef InSpec v2.3 or later.
|
26
|
-
|
27
|
-
Simply run:
|
28
|
-
|
29
|
-
```
|
30
|
-
$ inspec plugin install train-winrm
|
31
|
-
```
|
32
|
-
|
33
|
-
You can then run, using Chef InSpec as an example:
|
34
|
-
|
35
|
-
```
|
36
|
-
you@home $ inspec some-profile winrm://someuser@somehost --password somepassword
|
37
|
-
```
|
38
|
-
|
39
|
-
From Ruby code, you may use this plugin as follows:
|
40
|
-
```
|
41
|
-
require 'train'
|
42
|
-
transport = Train.create(
|
43
|
-
'winrm',
|
44
|
-
host: '1.2.3.4',
|
45
|
-
user: 'Administrator',
|
46
|
-
password: '...',
|
47
|
-
ssl: true,
|
48
|
-
self_signed: true
|
49
|
-
)
|
50
|
-
conn = transport.connection
|
51
|
-
```
|
52
|
-
|
53
|
-
## Target Options for Train-WinRM
|
54
|
-
|
55
|
-
### host
|
56
|
-
|
57
|
-
Required `String`. The hostname or IP address used for connection.
|
58
|
-
|
59
|
-
#### port
|
60
|
-
|
61
|
-
Optional `Integer`, default 5985 (plain) or 5896 (SSL). The port number to which the connection should be made.
|
62
|
-
|
63
|
-
### user
|
64
|
-
|
65
|
-
Optional `String`, username used for sign in. Default `Administrator`.
|
66
|
-
|
67
|
-
### password
|
68
|
-
|
69
|
-
Optional `String`, password used for sign in. None sent if not provided.
|
70
|
-
|
71
|
-
### ssl
|
72
|
-
|
73
|
-
Optional `Boolean`. Defaults to `false`. Determines whether to use SSL to encrypt communications.
|
74
|
-
|
75
|
-
Several other options exist. To see these options, run:
|
76
|
-
|
77
|
-
```
|
78
|
-
puts Train.options('winrm')
|
79
|
-
```
|
80
|
-
|
81
|
-
## Reporting Issues
|
82
|
-
|
83
|
-
Bugs, typos, limitations, and frustrations are welcome to be reported through the [GitHub issues page for the train-winrm project](https://github.com/inspec/train-winrm/issues).
|
84
|
-
|
85
|
-
You may also ask questions in the #inspec channel of the Chef Community Slack team. However, for an issue to get traction, please report it as a github issue.
|
86
|
-
|
87
|
-
## Development on this Plugin
|
88
|
-
|
89
|
-
### Development Process
|
90
|
-
|
91
|
-
If you wish to contribute to this plugin, please use the usual fork-branch-push-PR cycle. All functional changes need new tests, and bugfixes are expected to include a new test that demonstrates the bug.
|
92
|
-
|
93
|
-
### Reference Information
|
94
|
-
|
95
|
-
[Plugin Development](https://github.com/inspec/train/blob/master/docs/dev/plugins.md) is documented on the `train` project on GitHub.
|
96
|
-
|
97
|
-
### Unit tests
|
98
|
-
|
99
|
-
Run `bundle exec rake test:unit` to run the unit tests.
|
100
|
-
|
101
|
-
### Testing changes against a Windows Machine
|
102
|
-
|
103
|
-
Install Vagrant and VirtualBox. Check the Vagrantfile to verify that it references a Windows 2016 evaluation VagrantBox to which you have access.
|
104
|
-
|
105
|
-
Then, run `bundle exec rake test:integration`. There are sub-tasks you can use to run only the integration tests; to see a list of all tasks, run `rake -aT`.
|
data/train-winrm.gemspec
DELETED
@@ -1,44 +0,0 @@
|
|
1
|
-
# As plugins are usually packaged and distributed as a RubyGem,
|
2
|
-
# we have to provide a .gemspec file, which controls the gembuild
|
3
|
-
# and publish process. This is a fairly generic gemspec.
|
4
|
-
|
5
|
-
# It is traditional in a gemspec to dynamically load the current version
|
6
|
-
# from a file in the source tree. The next three lines make that happen.
|
7
|
-
lib = File.expand_path("../lib", __FILE__)
|
8
|
-
$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
|
9
|
-
require "train-winrm/version"
|
10
|
-
|
11
|
-
Gem::Specification.new do |spec|
|
12
|
-
# Importantly, all Train plugins must be prefixed with `train-`
|
13
|
-
spec.name = "train-winrm"
|
14
|
-
|
15
|
-
# It is polite to namespace your plugin under InspecPlugins::YourPluginInCamelCase
|
16
|
-
spec.version = TrainPlugins::WinRM::VERSION
|
17
|
-
spec.authors = ["Chef InSpec Team"]
|
18
|
-
spec.email = ["inspec@chef.io"]
|
19
|
-
spec.summary = "Windows WinRM API Transport for Train"
|
20
|
-
spec.description = "Allows applictaions using Train to speak to Windows using Remote Management; handles authentication, cacheing, and SDK dependency management."
|
21
|
-
spec.homepage = "https://github.com/inspec/train-winrm"
|
22
|
-
spec.license = "Apache-2.0"
|
23
|
-
|
24
|
-
# Though complicated-looking, this is pretty standard for a gemspec.
|
25
|
-
# It just filters what will actually be packaged in the gem (leaving
|
26
|
-
# out tests, etc)
|
27
|
-
spec.files = %w{
|
28
|
-
README.md train-winrm.gemspec Gemfile
|
29
|
-
} + Dir.glob(
|
30
|
-
"lib/**/*", File::FNM_DOTMATCH
|
31
|
-
).reject { |f| File.directory?(f) }
|
32
|
-
spec.require_paths = ["lib"]
|
33
|
-
|
34
|
-
# If you rely on any other gems, list them here with any constraints.
|
35
|
-
# This is how `inspec plugin install` is able to manage your dependencies.
|
36
|
-
|
37
|
-
# If you only need certain gems during development or testing, list
|
38
|
-
# them in Gemfile, not here.
|
39
|
-
|
40
|
-
# Do not list inspec as a dependency of a train plugin.
|
41
|
-
# Do not list train or train-core as a dependency of a train plugin.
|
42
|
-
spec.add_dependency "winrm", "~> 2.0"
|
43
|
-
spec.add_dependency "winrm-fs", "~> 1.0"
|
44
|
-
end
|