cleanroom 1.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -0,0 +1,7 @@
1
+ ---
2
+ SHA1:
3
+ metadata.gz: 5f611b9683805a4330c66fdf770e643d708000e5
4
+ data.tar.gz: 767bc0ba13fd9353126926340b0a70f7cd0756aa
5
+ SHA512:
6
+ metadata.gz: 72132627920374fcc949aca0c453c09ae891e4e9da28c58356e4e8846974c2599705b589e9a0d1f91efb908c7a8f63e4221e642c6d04ee070bfbbccbdca0f221
7
+ data.tar.gz: c16576092728a82074a7ea0a4864ed1d5bcbed4098e5b09c245d17de2302506de5562b628675ed8f0b94ddcac69867dbfbab8615023e9d0c05be007e5240e5cd
@@ -0,0 +1,14 @@
1
+ /.bundle/
2
+ /.yardoc
3
+ /Gemfile.lock
4
+ /_yardoc/
5
+ /coverage/
6
+ /doc/
7
+ /pkg/
8
+ /spec/reports/
9
+ /tmp/
10
+ *.bundle
11
+ *.so
12
+ *.o
13
+ *.a
14
+ mkmf.log
@@ -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
@@ -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.
@@ -0,0 +1,229 @@
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
+ [![Dependency Status](http://img.shields.io/gemnasium/sethvargo/cleanroom.svg)][gemnasium]
6
+ [![Code Climate](http://img.shields.io/codeclimate/github/sethvargo/cleanroom.svg)][codeclimate]
7
+ [![Gittip](http://img.shields.io/gittip/sethvargo.svg)][gittip]
8
+
9
+ [gem]: https://rubygems.org/gems/cleanroom
10
+ [travis]: http://travis-ci.org/sethvargo/chef-suguar
11
+ [gemnasium]: https://gemnasium.com/sethvargo/cleanroom
12
+ [codeclimate]: https://codeclimate.com/github/sethvargo/cleanroom
13
+ [gittip]: https://www.gittip.com/sethvargo
14
+
15
+ 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!
16
+
17
+ The cleanroom pattern is a unique way for more safely evaluating Ruby DSLs without adding additional overhead.
18
+
19
+
20
+ Installation
21
+ ------------
22
+
23
+ Add this line to your application's Gemfile:
24
+
25
+ ```ruby
26
+ gem 'cleanroom'
27
+ ```
28
+
29
+ And then execute:
30
+
31
+ $ bundle
32
+
33
+ Or install it yourself as:
34
+
35
+ $ gem install cleanroom
36
+
37
+
38
+ Usage
39
+ -----
40
+
41
+ ### Setup
42
+ In order to use the cleanroom, you must first load the cleanroom gem:
43
+
44
+ ```ruby
45
+ require 'cleanroom'
46
+ ```
47
+
48
+ Next, for any file you wish to be evaluated as a DSL, include the module:
49
+
50
+ ```ruby
51
+ class MyDSL
52
+ include Cleanroom
53
+ end
54
+ ```
55
+
56
+ ### Writing DSLs
57
+ For each public method you with to expose as a DSL method, call `expose` after the method definition in your class:
58
+
59
+ ```ruby
60
+ class MyDSL
61
+ include Cleanroom
62
+
63
+ def my_method
64
+ # ...
65
+ end
66
+ expose :my_method
67
+
68
+ def public_method
69
+ # ...
70
+ end
71
+
72
+ private
73
+
74
+ def private_method
75
+ # ...
76
+ end
77
+ end
78
+ ```
79
+
80
+ In this example, `MyDSL` exposes two public API methods:
81
+
82
+ - `my_method`
83
+ - `public_method`
84
+
85
+ which would be accessible via:
86
+
87
+ ```ruby
88
+ instance = MyDSL.new
89
+ instance.my_method
90
+ instance.public_method
91
+ ```
92
+
93
+ MyDSL also exposes one DSL method:
94
+
95
+ - `my_method`
96
+
97
+ which would be accessible in a DSL file:
98
+
99
+ ```ruby
100
+ my_method
101
+ ```
102
+
103
+ The use of the `expose` method has the added advantage of clearly identifying which methods are available as part of the DSL.
104
+
105
+ The method `private_method` is never accessible in the DSL or as part of the public API.
106
+
107
+ ### Evaluating DSLs
108
+ 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.
109
+
110
+ ```ruby
111
+ instance = MyDSL.new
112
+
113
+ # Using a Ruby block
114
+ instance.evaluate do
115
+ my_method
116
+ end
117
+
118
+ # Using a String
119
+ instance.evaluate "my_method"
120
+
121
+ # Given a file at /file
122
+ instance.evaluate_file('/file')
123
+ ```
124
+
125
+ These same methods are available on the class as well, but require you pass in the instance:
126
+
127
+ ```ruby
128
+ instance = MyDSL.new
129
+
130
+ # Using a Ruby block
131
+ MyDSL.evaluate(instance) do
132
+ my_method
133
+ end
134
+
135
+ # Using a String
136
+ MyDSL.evaluate(instance) "my_method"
137
+
138
+ # Given a file at /file
139
+ MyDSL.evaluate_file(instance, '/file')
140
+ ```
141
+
142
+ For both of these examples, _the given instance is modified_, meaning `instance` holds the values after the evaluation took place.
143
+
144
+
145
+ "Security"
146
+ ----------
147
+ The cleanroom gem tries to prevent unauthorized variable access and attempts to alter the behavior of the system.
148
+
149
+ 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.
150
+
151
+ ```ruby
152
+ # Some DSL file
153
+ @instance #=> nil
154
+ ```
155
+
156
+ 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.
157
+
158
+ ```ruby
159
+ # Some DSL file
160
+ __instance__ #=> Cleanroom::InaccessibleError
161
+ send(:__instance__) #=> Cleanroom::InaccessibleError
162
+ ```
163
+
164
+ Third, the ability to create new methods on the cleanroom is also disabled:
165
+
166
+ ```ruby
167
+ # Some DSL file
168
+ self.class.class_eval { } #=> Cleanroom::InaccessibleError
169
+ self.class.instance_eval { } #=> Cleanroom::InaccessibleError
170
+ ```
171
+
172
+ 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.
173
+
174
+ 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!**
175
+
176
+
177
+ Testing
178
+ -------
179
+ 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:
180
+
181
+ ```ruby
182
+ # spec/spec_helper.rb
183
+ require 'rspec'
184
+ require 'cleanroom/rspec'
185
+ ```
186
+
187
+ This will define the following matchers:
188
+
189
+ ```ruby
190
+ # Check against an instance
191
+ expect(:my_method).to be_an_exposed_method_on(instance)
192
+
193
+ # Check against a class
194
+ expect(:my_method).to be_an_exposed_method_on(klass)
195
+
196
+ # Check against an instance
197
+ expect(instance).to have_exposed_method(:my_method)
198
+
199
+ # Check against a class
200
+ expect(klass).to have_exposed_method(:my_method)
201
+ ```
202
+
203
+
204
+ Contributing
205
+ ------------
206
+ 1. Fork the project
207
+ 1. Write tests
208
+ 1. Run tests
209
+ 1. Create a new Pull Request
210
+
211
+
212
+ License
213
+ -------
214
+ ```text
215
+ Copyright 2014 Seth Vargo <sethvargo@gmail.com>
216
+
217
+ Licensed under the Apache License, Version 2.0 (the "License");
218
+ you may not use this file except in compliance with the License.
219
+ You may obtain a copy of the License at
220
+
221
+ http://www.apache.org/licenses/LICENSE-2.0
222
+
223
+ Unless required by applicable law or agreed to in writing, software
224
+ distributed under the License is distributed on an "AS IS" BASIS,
225
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
226
+ See the License for the specific language governing permissions and
227
+ limitations under the License.
228
+ ```
229
+