chef-cleanroom 1.0.1

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml ADDED
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA256:
3
+ metadata.gz: 0125c144c34a18a068b08176ee06cf025b397886a875d34bbe11e6645fd1a308
4
+ data.tar.gz: 5816b276ca9d3f7927d60c9625e50b39651ecb6e8145f19a1cbc8d32fe88bbf8
5
+ SHA512:
6
+ metadata.gz: 12b20e9ac1f7ac1035cbf05a3b2a6f12706a2fbf475654bd7a7c666dc1264e7e3e806c92a76a5a23dbba4e04c11f403563dc086f65f196142ca1743838908cb6
7
+ data.tar.gz: 45132675fa40024cdf89c3fbf6ab4a11dec5061d6208dc6f57f677abedc724f797d508ba5284b14d273d9d7896b87a1b34742a9f4b51330f0f28047441784537
data/.gitignore ADDED
@@ -0,0 +1,35 @@
1
+ ### Ruby ###
2
+ *.gem
3
+ *.rbc
4
+ /.config
5
+ /coverage/
6
+ /InstalledFiles
7
+ /pkg/
8
+ /spec/reports/
9
+ /test/tmp/
10
+ /test/version_tmp/
11
+ /tmp/
12
+
13
+ ## Specific to RubyMotion:
14
+ .dat*
15
+ .repl_history
16
+ build/
17
+
18
+ ## Documentation cache and generated files:
19
+ /.yardoc/
20
+ /_yardoc/
21
+ /doc/
22
+ /rdoc/
23
+
24
+ ## Environment normalisation:
25
+ /.bundle/
26
+ /vendor/bundle
27
+ /lib/bundler/man/
28
+
29
+ ## Ruby gem
30
+ Gemfile.lock
31
+ .ruby-version
32
+ .ruby-gemset
33
+
34
+ # unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
35
+ .rvmrc
data/.travis.yml ADDED
@@ -0,0 +1,12 @@
1
+ rvm:
2
+ - 1.9.3
3
+ - 2.0.0
4
+ - 2.1
5
+
6
+ bundler_args: --jobs 7
7
+
8
+ branches:
9
+ only:
10
+ - master
11
+
12
+ script: bundle exec rake travis:ci
data/CHANGELOG.md ADDED
@@ -0,0 +1,6 @@
1
+ Cleanroom CHANGELOG
2
+ ===================
3
+
4
+ v1.0.0 (August, 12, 2014)
5
+ -------------------------
6
+ - Initial public release
data/Gemfile ADDED
@@ -0,0 +1,2 @@
1
+ source 'https://rubygems.org'
2
+ gemspec
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/README.md ADDED
@@ -0,0 +1,225 @@
1
+ Ruby Cleanroom
2
+ ==============
3
+ [![Gem Version](http://img.shields.io/gem/v/cleanroom.svg)][gem]
4
+ [![Build Status](http://img.shields.io/travis/sethvargo/cleanroom.svg)][travis]
5
+ [![Code Climate](http://img.shields.io/codeclimate/github/sethvargo/cleanroom.svg)][codeclimate]
6
+
7
+ [gem]: https://rubygems.org/gems/cleanroom
8
+ [travis]: http://travis-ci.org/sethvargo/cleanroom
9
+ [codeclimate]: https://codeclimate.com/github/sethvargo/cleanroom
10
+
11
+ Ruby is an excellent programming language for creating and managing custom DSLs, but how can you securely evaluate a DSL while explicitly controlling the methods exposed to the user? Our good friends `instance_eval` and `instance_exec` are great, but they expose all methods - public, protected, and private - to the user. Even worse, they expose the ability to accidentally or intentionally alter the behavior of the system! The cleanroom pattern is a safer, more convenient, Ruby-like approach for limiting the information exposed by a DSL while giving users the ability to write awesome code!
12
+
13
+ The cleanroom pattern is a unique way for more safely evaluating Ruby DSLs without adding additional overhead.
14
+
15
+
16
+ Installation
17
+ ------------
18
+
19
+ Add this line to your application's Gemfile:
20
+
21
+ ```ruby
22
+ gem 'cleanroom'
23
+ ```
24
+
25
+ And then execute:
26
+
27
+ $ bundle
28
+
29
+ Or install it yourself as:
30
+
31
+ $ gem install cleanroom
32
+
33
+
34
+ Usage
35
+ -----
36
+
37
+ ### Setup
38
+ In order to use the cleanroom, you must first load the cleanroom gem:
39
+
40
+ ```ruby
41
+ require 'cleanroom'
42
+ ```
43
+
44
+ Next, for any file you wish to be evaluated as a DSL, include the module:
45
+
46
+ ```ruby
47
+ class MyDSL
48
+ include Cleanroom
49
+ end
50
+ ```
51
+
52
+ ### Writing DSLs
53
+ For each public method you with to expose as a DSL method, call `expose` after the method definition in your class:
54
+
55
+ ```ruby
56
+ class MyDSL
57
+ include Cleanroom
58
+
59
+ def my_method
60
+ # ...
61
+ end
62
+ expose :my_method
63
+
64
+ def public_method
65
+ # ...
66
+ end
67
+
68
+ private
69
+
70
+ def private_method
71
+ # ...
72
+ end
73
+ end
74
+ ```
75
+
76
+ In this example, `MyDSL` exposes two public API methods:
77
+
78
+ - `my_method`
79
+ - `public_method`
80
+
81
+ which would be accessible via:
82
+
83
+ ```ruby
84
+ instance = MyDSL.new
85
+ instance.my_method
86
+ instance.public_method
87
+ ```
88
+
89
+ MyDSL also exposes one DSL method:
90
+
91
+ - `my_method`
92
+
93
+ which would be accessible in a DSL file:
94
+
95
+ ```ruby
96
+ my_method
97
+ ```
98
+
99
+ The use of the `expose` method has the added advantage of clearly identifying which methods are available as part of the DSL.
100
+
101
+ The method `private_method` is never accessible in the DSL or as part of the public API.
102
+
103
+ ### Evaluating DSLs
104
+ The cleanroom also includes the ability to more safely evaluate DSL files. Given an instance of a class, you can call `evaluate` or `evaluate_file` to read a DSL.
105
+
106
+ ```ruby
107
+ instance = MyDSL.new
108
+
109
+ # Using a Ruby block
110
+ instance.evaluate do
111
+ my_method
112
+ end
113
+
114
+ # Using a String
115
+ instance.evaluate "my_method"
116
+
117
+ # Given a file at /file
118
+ instance.evaluate_file('/file')
119
+ ```
120
+
121
+ These same methods are available on the class as well, but require you pass in the instance:
122
+
123
+ ```ruby
124
+ instance = MyDSL.new
125
+
126
+ # Using a Ruby block
127
+ MyDSL.evaluate(instance) do
128
+ my_method
129
+ end
130
+
131
+ # Using a String
132
+ MyDSL.evaluate(instance) "my_method"
133
+
134
+ # Given a file at /file
135
+ MyDSL.evaluate_file(instance, '/file')
136
+ ```
137
+
138
+ For both of these examples, _the given instance is modified_, meaning `instance` holds the values after the evaluation took place.
139
+
140
+
141
+ "Security"
142
+ ----------
143
+ The cleanroom gem tries to prevent unauthorized variable access and attempts to alter the behavior of the system.
144
+
145
+ First, the underlying instance object is never stored in an instance variable. Due to the nature of `instance_eval`, it would be trivial for a malicious user to directly access methods on the delegate class.
146
+
147
+ ```ruby
148
+ # Some DSL file
149
+ @instance #=> nil
150
+ ```
151
+
152
+ Second, access to the underlying `instance` in the cleanroom is restricted to `self` by inspecting the `caller` attempts to access `__instance__` from outside of a method in the cleanroom will result in an error.
153
+
154
+ ```ruby
155
+ # Some DSL file
156
+ __instance__ #=> Cleanroom::InaccessibleError
157
+ send(:__instance__) #=> Cleanroom::InaccessibleError
158
+ ```
159
+
160
+ Third, the ability to create new methods on the cleanroom is also disabled:
161
+
162
+ ```ruby
163
+ # Some DSL file
164
+ self.class.class_eval { } #=> Cleanroom::InaccessibleError
165
+ self.class.instance_eval { } #=> Cleanroom::InaccessibleError
166
+ ```
167
+
168
+ Fourth, when delegating to the underlying instance object, `public_send` (as opposed to `send` or `__send__`) is used. Even if an attacker could somehow bypass the previous safeguards, they would be unable to call non-public methods on the delegate object.
169
+
170
+ If you find a security hole in the cleanroom implementation, please email me at the contact info found in my [GitHub profile](https://github.com/sethvargo). **Do not open an issue!**
171
+
172
+
173
+ Testing
174
+ -------
175
+ If you are using cleanroom in your DSLs, you will likely want to test a particular DSL method is exposed. Cleanroom packages some RSpec matchers for your convienence:
176
+
177
+ ```ruby
178
+ # spec/spec_helper.rb
179
+ require 'rspec'
180
+ require 'cleanroom/rspec'
181
+ ```
182
+
183
+ This will define the following matchers:
184
+
185
+ ```ruby
186
+ # Check against an instance
187
+ expect(:my_method).to be_an_exposed_method_on(instance)
188
+
189
+ # Check against a class
190
+ expect(:my_method).to be_an_exposed_method_on(klass)
191
+
192
+ # Check against an instance
193
+ expect(instance).to have_exposed_method(:my_method)
194
+
195
+ # Check against a class
196
+ expect(klass).to have_exposed_method(:my_method)
197
+ ```
198
+
199
+
200
+ Contributing
201
+ ------------
202
+ 1. Fork the project
203
+ 1. Write tests
204
+ 1. Run tests
205
+ 1. Create a new Pull Request
206
+
207
+
208
+ License
209
+ -------
210
+ ```text
211
+ Copyright 2014 Seth Vargo <sethvargo@gmail.com>
212
+
213
+ Licensed under the Apache License, Version 2.0 (the "License");
214
+ you may not use this file except in compliance with the License.
215
+ You may obtain a copy of the License at
216
+
217
+ http://www.apache.org/licenses/LICENSE-2.0
218
+
219
+ Unless required by applicable law or agreed to in writing, software
220
+ distributed under the License is distributed on an "AS IS" BASIS,
221
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
222
+ See the License for the specific language governing permissions and
223
+ limitations under the License.
224
+ ```
225
+