minitar 1.1.0 → 1.1.1

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.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 59638d7516e33ff6d61b73b96aaa0b17446606dfebaff5c04ba2f4cb29db842e
4
- data.tar.gz: b90a67f815f2f4ee38f5b4a0050d6bc2ef52794b3da80e767fee4a66c57ed2c3
3
+ metadata.gz: 7855c77e89244e7288b4bb9398593ea6ac680a3891f3e9ce0bda77a8ea5f2e48
4
+ data.tar.gz: 1c2d05408cc0d2a69b604e257ec032bdbd98efd5384198a0b0d47f78e1407a31
5
5
  SHA512:
6
- metadata.gz: 5b3f09d060b05dee333e3e2652b0b36e9533b3be9b9dbc94cb25948e12905d6518678774ab74a770723e21ebd583ee2bbb2a5d5b75ef38884632dc1e71a4ca84
7
- data.tar.gz: 95354454f621aabe1d5c20615ac48a5b4f92ab27c35af1cf296afca5b3516369e12c54ac01175fd472715d7fdf509f8c7ed358b9e84ad672d0d9fb1407a195d8
6
+ metadata.gz: 01dd7962ebc29dcdfa69221b6ece851f4ad488b1c9f25cd546054a611ec90f9ae3f44a7a3d0555f9efb7927a71f9c59cba75729bd46b103e4a8b4ead52e46547
7
+ data.tar.gz: 58e66377d5e593c6be0c149ac392931affea945c03fc12b34262fe5fa6154edd24247aa2ad7008b37891c12002199e664b8fe4875833b70d961492b8a42b2628
data/CHANGELOG.md CHANGED
@@ -1,5 +1,43 @@
1
1
  # Changelog
2
2
 
3
+ ## 1.1.1 / 2026-11-11
4
+
5
+ - Security:
6
+
7
+ - Relative path rejection ignored Windows-like filenames in maliciously
8
+ crafted tarballs _on Windows itself_. This affects all versions of minitar
9
+ < 1.1.1.
10
+
11
+ Tar entry names are byte strings following POSIX rules, where `/` is the
12
+ only directory separator and characters special on Windows (`:` and `\`)
13
+ are ordinary. This meant that `..\x` skipped relative path rejection and
14
+ affected files or directories outside of the extraction destination.
15
+
16
+ When running on Windows, Minitar now normalizes all `\` characters to `/`
17
+ before checking for potential relative path escapes.
18
+
19
+ The following filename patterns are all rejected with
20
+ `UnsafeFileNameError`:
21
+
22
+ - paths that start with drive designators (`[A-Z]:`);
23
+ - paths that contain `:` (NTFS alternate data stream names); and
24
+ - path components that have trailing `.` or space characters.
25
+
26
+ UNC paths are normalized to relative directories in the destination.
27
+
28
+ Behaviour on non-Windows platform has not been changed.
29
+
30
+ - Bug fix:
31
+
32
+ - The `..` check now rejects only path components that are exactly `..`.
33
+ Names such as `dirname../file` were previously rejected incorrectly on all
34
+ platforms.
35
+
36
+ - Documentation:
37
+
38
+ - Removed duplicate documentation files and updated the RDoc to match the
39
+ configuration.
40
+
3
41
  ## 1.1.0 / 2025-09-07
4
42
 
5
43
  - Enhancements:
@@ -25,13 +63,14 @@
25
63
 
26
64
  Changes described below are effective 2024-12-31.
27
65
 
28
- - Update gem management details to use markdown files for everything, enabled
29
- in part by [flavorjones/hoe-markdown][hoe-markdown]. Several files were
30
- renamed to be more consistent with standard practices.
66
+ - Update gem management details to use markdown files for everything,
67
+ enabled in part by [flavorjones/hoe-markdown][hoe-markdown]. Several files
68
+ were renamed to be more consistent with standard practices.
31
69
 
32
- - Updated security notes with an [age][age] public key rather than pointing to
33
- Keybase.io and a PGP public key which I no longer use. The use of the
34
- [Tidelift security contact][tidelift] is recommended over direct disclosure.
70
+ - Updated security notes with an [age][age] public key rather than pointing
71
+ to Keybase.io and a PGP public key which I no longer use. The use of the
72
+ [Tidelift security contact][tidelift] is recommended over direct
73
+ disclosure.
35
74
 
36
75
  Changes described below are effective 2025-08-04.
37
76
 
@@ -41,15 +80,15 @@
41
80
 
42
81
  - Bug fix:
43
82
 
44
- - Minitar 1.0.1 was released with an unchanged gemspec. Reported by Debashish
45
- Biswas in [#65][issue-65].
83
+ - Minitar 1.0.1 was released with an unchanged gemspec. Reported by
84
+ Debashish Biswas in [#65][issue-65].
46
85
 
47
86
  ## 1.0.1 / 2024-08-08
48
87
 
49
88
  - Bug fix:
50
89
 
51
- - Resolve a constant lookup issue. The accepted fix has been provided by Aram
52
- Price in [#58][issue-58].
90
+ - Resolve a constant lookup issue. The accepted fix has been provided by
91
+ Aram Price in [#58][issue-58].
53
92
 
54
93
  ## 1.0.0 / 2024-08-07
55
94
 
@@ -79,8 +118,8 @@
79
118
 
80
119
  ## 0.11 / 2022-12-31
81
120
 
82
- - symlink support is complete. Merged as PR [#42][pull-42], rebased and built on
83
- top of PR [#12][pull-12] by fetep.
121
+ - symlink support is complete. Merged as PR [#42][pull-42], rebased and built
122
+ on top of PR [#12][pull-12] by fetep.
84
123
 
85
124
  - kymmt90 fixed a documentation error on `Minitar.pack` in PR [#43][pull-43].
86
125
 
@@ -100,10 +139,10 @@
100
139
 
101
140
  ## 0.8 / 2019-01-05
102
141
 
103
- - [@inkstak](https://github.com/inkstak) resolved an issue introduced in the fix
104
- for [#31][issue-31] by allowing spaces to be considered valid characters in
105
- strict octal handling. Octal conversion ignores leading spaces. Merged from a
106
- slightly modified version of PR [#35][pull-35].
142
+ - [@inkstak](https://github.com/inkstak) resolved an issue introduced in the
143
+ fix for [#31][issue-31] by allowing spaces to be considered valid characters
144
+ in strict octal handling. Octal conversion ignores leading spaces. Merged
145
+ from a slightly modified version of PR [#35][pull-35].
107
146
 
108
147
  - [@dearblue](https://github.com/dearblue) contributed PR [#32][pull-32]
109
148
  providing an explicit call to #bytesize for strings that include multibyte
@@ -122,21 +161,21 @@
122
161
  patch. Additional information was added as [#30][issue-30].
123
162
 
124
163
  - [@dearblue](https://github.com/dearblue) contributed PR [#33][pull-33]
125
- providing a fix for `Minitar::Reader` when the IO-like object does not have a
126
- `#pos` method.
164
+ providing a fix for `Minitar::Reader` when the IO-like object does not have
165
+ a `#pos` method.
127
166
 
128
167
  - Kevin McDermott contributed PR [#34][pull-34] so that an InvalidTarStream is
129
- raised if the tar header is not valid, preventing incorrect streaming of files
130
- from a non-tarfile. This is a minor breaking change, so the version has been
131
- bumped accordingly.
168
+ raised if the tar header is not valid, preventing incorrect streaming of
169
+ files from a non-tarfile. This is a minor breaking change, so the version
170
+ has been bumped accordingly.
132
171
 
133
- - Kazuyoshi Kato contributed PR [#26][pull-26] providing support for the GNU tar
134
- long filename extension.
172
+ - Kazuyoshi Kato contributed PR [#26][pull-26] providing support for the GNU
173
+ tar long filename extension.
135
174
 
136
175
  - Addressed a potential DOS with negative size fields in tar headers
137
- ([#31][issue-31]). This has been handled in two ways: the size field in a tar
138
- header is interpreted as a strict octal value and the `Minitar` reader will
139
- raise an InvalidTarStream if the size ends up being negative anyway.
176
+ ([#31][issue-31]). This has been handled in two ways: the size field in a
177
+ tar header is interpreted as a strict octal value and the `Minitar` reader
178
+ will raise an InvalidTarStream if the size ends up being negative anyway.
140
179
 
141
180
  ## 0.6.1 / 2017-02-07
142
181
 
@@ -150,28 +189,29 @@
150
189
 
151
190
  - Breaking Changes:
152
191
 
153
- - Extracted `bin/minitar` into a new gem, `minitar-cli`. No, I am _not_ going
154
- to bump the major version for this. As far as I can tell, few people use the
155
- command-line utility anyway. (Installing `archive-tar-minitar` will install
156
- both `minitar` and `minitar-cli`, at least until version 1.0.)
192
+ - Extracted `bin/minitar` into a new gem, `minitar-cli`. No, I am _not_
193
+ going to bump the major version for this. As far as I can tell, few people
194
+ use the command-line utility anyway. (Installing `archive-tar-minitar`
195
+ will install both `minitar` and `minitar-cli`, at least until version
196
+ 1.0.)
157
197
 
158
198
  - `Minitar` extraction before 0.6 traverses directories if the tarball
159
199
  includes a relative directory reference, as reported in [#16][issue-16] by
160
200
  [@ecneladis](https://github.com/ecneladis). This has been disallowed
161
201
  entirely and will throw a `SecureRelativePathError` when found.
162
202
  Additionally, if the final destination of an entry is an already-existing
163
- symbolic link, the existing symbolic link will be removed and the file will
164
- be written correctly (on platforms that support symbolic links).
203
+ symbolic link, the existing symbolic link will be removed and the file
204
+ will be written correctly (on platforms that support symbolic links).
165
205
 
166
206
  - Enhancements:
167
207
 
168
- - Licence change. After speaking with Mauricio Fernández, we have changed the
169
- licensing of this library to Ruby and Simplified BSD and have dropped the
170
- GNU GPL license. This takes effect from the 0.6 release.
208
+ - Licence change. After speaking with Mauricio Fernández, we have changed
209
+ the licensing of this library to Ruby and Simplified BSD and have dropped
210
+ the GNU GPL license. This takes effect from the 0.6 release.
171
211
  - Printing a deprecation warning for including Archive::Tar to put `Minitar`
172
212
  in the top-level namespace.
173
- - Printing a deprecation warning for including `Archive::Tar::Minitar` into a
174
- class (`Minitar` will be a class for version 1.0).
213
+ - Printing a deprecation warning for including `Archive::Tar::Minitar` into
214
+ a class (`Minitar` will be a class for version 1.0).
175
215
  - Moved `Archive::Tar::PosixHeader` to `Archive::Tar::Minitar::PosixHeader`
176
216
  with a deprecation warning. Do not depend on
177
217
  `Archive::Tar::Minitar::PosixHeader`, as it will be moving to
@@ -188,11 +228,12 @@
188
228
  internal implementation detail.
189
229
  - `Writer::BoundedStream` was renamed to `Writer::BoundedWriteStream` for
190
230
  clarity. A deprecation warning is provided on first use because a
191
- BoundedWriteStream may raise a `BoundedWriteStream::FileOverflow` exception.
231
+ BoundedWriteStream may raise a `BoundedWriteStream::FileOverflow`
232
+ exception.
192
233
  - `Writer::BoundedWriteStream::FileOverflow` has been renamed to
193
- `Writer::WriteBoundaryOverflow` and inherits from `StandardError` instead of
194
- `RuntimeError`. Note that for Ruby 2.0 or higher, an error will be raised
195
- when specifying `Writer::BoundedWriteStream::FileOverflow` because
234
+ `Writer::WriteBoundaryOverflow` and inherits from `StandardError` instead
235
+ of `RuntimeError`. Note that for Ruby 2.0 or higher, an error will be
236
+ raised when specifying `Writer::BoundedWriteStream::FileOverflow` because
196
237
  `Writer::BoundedWriteStream` has been declared a private constant.
197
238
  - Modified `Writer#add_file_simple` to accept the data for a file in
198
239
  `opts[:data]`. When `opts[:data]` is provided, a stream block must not be
@@ -212,16 +253,16 @@
212
253
  - Fix [#2][issue-02] to handle IO streams that are not seekable, such as
213
254
  pipes, `STDIN`, or `STDOUT`.
214
255
  - Fix [#3][issue-03] to make the test timezone resilient.
215
- - Fix [#4][issue-04] for supporting the reading of tar files with filenames in
216
- the GNU long filename extension format. Ported from
217
- [@atoulme](https://github.com/atoulme)’s fork, originally provided by Curtis
218
- Sampson.
219
- - Fix [#6][issue-06] by making it raise the correct error for a long filename
220
- with no path components.
221
- - Fix [#13][issue-13] provided by [@fetep](https://github.com/fetep) fixes an
222
- off-by-one error on filename splitting.
223
- - Fix [#14][issue-14] provided by [@kzys](https://github.com/kzys) should fix
224
- Windows detection issues.
256
+ - Fix [#4][issue-04] for supporting the reading of tar files with filenames
257
+ in the GNU long filename extension format. Ported from
258
+ [@atoulme](https://github.com/atoulme)’s fork, originally provided by
259
+ Curtis Sampson.
260
+ - Fix [#6][issue-06] by making it raise the correct error for a long
261
+ filename with no path components.
262
+ - Fix [#13][issue-13] provided by [@fetep](https://github.com/fetep) fixes
263
+ an off-by-one error on filename splitting.
264
+ - Fix [#14][issue-14] provided by [@kzys](https://github.com/kzys) should
265
+ fix Windows detection issues.
225
266
  - Fix [#16][issue-16] as specified above.
226
267
  - Fix an issue where `Minitar.pack` would not include Unix hidden files when
227
268
  creating a tarball.
@@ -243,8 +284,8 @@
243
284
 
244
285
  ## 0.5.0
245
286
 
246
- - Initial release. Does files and directories. Command does create, extract, and
247
- list.
287
+ - Initial release. Does files and directories. Command does create, extract,
288
+ and list.
248
289
 
249
290
  [age]: https://github.com/FiloSottile/age
250
291
  [hoe-halostatue]: https://github.com/halostatue/hoe-halostatue
data/CODE_OF_CONDUCT.md CHANGED
@@ -1,128 +1,167 @@
1
- # Contributor Covenant Code of Conduct
1
+ # Contributor Covenant 3.0 Code of Conduct
2
2
 
3
3
  ## Our Pledge
4
4
 
5
- We as members, contributors, and leaders pledge to make participation in our
6
- community a harassment-free experience for everyone, regardless of age, body
7
- size, visible or invisible disability, ethnicity, sex characteristics, gender
8
- identity and expression, level of experience, education, socio-economic status,
9
- nationality, personal appearance, race, caste, color, religion, or sexual
10
- identity and orientation.
11
-
12
- We pledge to act and interact in ways that contribute to an open, welcoming,
13
- diverse, inclusive, and healthy community.
14
-
15
- ## Our Standards
16
-
17
- Examples of behavior that contributes to a positive environment for our
18
- community include:
19
-
20
- - Demonstrating empathy and kindness toward other people
21
- - Being respectful of differing opinions, viewpoints, and experiences
22
- - Giving and gracefully accepting constructive feedback
23
- - Accepting responsibility and apologizing to those affected by our mistakes,
24
- and learning from the experience
25
- - Focusing on what is best not just for us as individuals, but for the overall
26
- community
27
-
28
- Examples of unacceptable behavior include:
29
-
30
- - The use of sexualized language or imagery, and sexual attention or advances of
31
- any kind
32
- - Trolling, insulting or derogatory comments, and personal or political attacks
33
- - Public or private harassment
34
- - Publishing others' private information, such as a physical or email address,
35
- without their explicit permission
36
- - Other conduct which could reasonably be considered inappropriate in a
37
- professional setting
38
-
39
- ## Enforcement Responsibilities
40
-
41
- Community leaders are responsible for clarifying and enforcing our standards of
42
- acceptable behavior and will take appropriate and fair corrective action in
43
- response to any behavior that they deem inappropriate, threatening, offensive,
44
- or harmful.
45
-
46
- Community leaders have the right and responsibility to remove, edit, or reject
47
- comments, commits, code, wiki edits, issues, and other contributions that are
48
- not aligned to this Code of Conduct, and will communicate reasons for moderation
49
- decisions when appropriate.
5
+ We pledge to make our community welcoming, safe, and equitable for all.
6
+
7
+ We are committed to fostering an environment that respects and promotes the
8
+ dignity, rights, and contributions of all individuals, regardless of
9
+ characteristics including race, ethnicity, caste, color, age, physical
10
+ characteristics, neurodiversity, disability, sex or gender, gender identity or
11
+ expression, sexual orientation, language, philosophy or religion, national or
12
+ social origin, socio-economic position, level of education, or other status.
13
+ The same privileges of participation are extended to everyone who participates
14
+ in good faith and in accordance with this Covenant.
15
+
16
+ ## Encouraged Behaviors
17
+
18
+ While acknowledging differences in social norms, we all strive to meet our
19
+ community's expectations for positive behavior. We also understand that our
20
+ words and actions may be interpreted differently than we intend based on
21
+ culture, background, or native language.
22
+
23
+ With these considerations in mind, we agree to behave mindfully toward each
24
+ other and act in ways that center our shared values, including:
25
+
26
+ 1. Respecting the **purpose of our community**, our activities, and our ways
27
+ of gathering.
28
+ 2. Engaging **kindly and honestly** with others.
29
+ 3. Respecting **different viewpoints** and experiences.
30
+ 4. **Taking responsibility** for our actions and contributions.
31
+ 5. Gracefully giving and accepting **constructive feedback**.
32
+ 6. Committing to **repairing harm** when it occurs.
33
+ 7. Behaving in other ways that promote and sustain the **well-being of our
34
+ community**.
35
+
36
+ ## Restricted Behaviors
37
+
38
+ We agree to restrict the following behaviors in our community. Instances,
39
+ threats, and promotion of these behaviors are violations of this Code of
40
+ Conduct.
41
+
42
+ 1. **Harassment.** Violating explicitly expressed boundaries or engaging in
43
+ unnecessary personal attention after any clear request to stop.
44
+ 2. **Character attacks.** Making insulting, demeaning, or pejorative comments
45
+ directed at a community member or group of people.
46
+ 3. **Stereotyping or discrimination.** Characterizing anyone’s personality or
47
+ behavior on the basis of immutable identities or traits.
48
+ 4. **Sexualization.** Behaving in a way that would generally be considered
49
+ inappropriately intimate in the context or purpose of the community.
50
+ 5. **Violating confidentiality**. Sharing or acting on someone's personal or
51
+ private information without their permission.
52
+ 6. **Endangerment.** Causing, encouraging, or threatening violence or other
53
+ harm toward any person or group.
54
+ 7. Behaving in other ways that **threaten the well-being** of our community.
55
+
56
+ ### Other Restrictions
57
+
58
+ 1. **Misleading identity.** Impersonating someone else for any reason, or
59
+ pretending to be someone else to evade enforcement actions.
60
+ 2. **Failing to credit sources.** Not properly crediting the sources of
61
+ content you contribute.
62
+ 3. **Promotional materials**. Sharing marketing or other commercial content in
63
+ a way that is outside the norms of the community.
64
+ 4. **Irresponsible communication.** Failing to responsibly present content
65
+ which includes, links or describes any other restricted behaviors.
66
+
67
+ ## Reporting an Issue
68
+
69
+ Tensions can occur between community members even when they are trying their
70
+ best to collaborate. Not every conflict represents a code of conduct
71
+ violation, and this Code of Conduct reinforces encouraged behaviors and norms
72
+ that can help avoid conflicts and minimize harm.
73
+
74
+ When an incident does occur, it is important to report it promptly. To report
75
+ a possible violation, create a [private security advisory][advisory]
76
+ — violations of this code of conduct are considered security vulnerabilities.
77
+
78
+ Community Moderators take reports of violations seriously and will make every
79
+ effort to respond in a timely manner. They will investigate all reports of
80
+ code of conduct violations, reviewing messages, logs, and recordings, or
81
+ interviewing witnesses and other participants. Community Moderators will keep
82
+ investigation and enforcement actions as transparent as possible while
83
+ prioritizing safety and confidentiality. In order to honor these values,
84
+ enforcement actions are carried out in private with the involved parties, but
85
+ communicating to the whole community may be part of a mutually agreed upon
86
+ resolution.
87
+
88
+ ## Addressing and Repairing Harm
89
+
90
+ If an investigation by the Community Moderators finds that this Code of
91
+ Conduct has been violated, the following enforcement ladder may be used to
92
+ determine how best to repair harm, based on the incident's impact on the
93
+ individuals involved and the community as a whole. Depending on the severity
94
+ of a violation, lower rungs on the ladder may be skipped.
95
+
96
+ 1. Warning
97
+ 1. Event: A violation involving a single incident or series of incidents.
98
+ 2. Consequence: A private, written warning from the Community Moderators.
99
+ 3. Repair: Examples of repair include a private written apology,
100
+ acknowledgement of responsibility, and seeking clarification on
101
+ expectations.
102
+
103
+ 2. Temporarily Limited Activities
104
+ 1. Event: A repeated incidence of a violation that previously resulted in a
105
+ warning, or the first incidence of a more serious violation.
106
+ 2. Consequence: A private, written warning with a time-limited cooldown
107
+ period designed to underscore the seriousness of the situation and give
108
+ the community members involved time to process the incident. The
109
+ cooldown period may be limited to particular communication channels or
110
+ interactions with particular community members.
111
+ 3. Repair: Examples of repair may include making an apology, using the
112
+ cooldown period to reflect on actions and impact, and being thoughtful
113
+ about re-entering community spaces after the period is over.
114
+
115
+ 3. Temporary Suspension
116
+ 1. Event: A pattern of repeated violation which the Community Moderators
117
+ have tried to address with warnings, or a single serious violation.
118
+ 2. Consequence: A private written warning with conditions for return from
119
+ suspension. In general, temporary suspensions give the person being
120
+ suspended time to reflect upon their behavior and possible corrective
121
+ actions.
122
+ 3. Repair: Examples of repair include respecting the spirit of the
123
+ suspension, meeting the specified conditions for return, and being
124
+ thoughtful about how to reintegrate with the community when the
125
+ suspension is lifted.
126
+
127
+ 4. Permanent Ban
128
+ 1. Event: A pattern of repeated code of conduct violations that other steps
129
+ on the ladder have failed to resolve, or a violation so serious that the
130
+ Community Moderators determine there is no way to keep the community
131
+ safe with this person as a member.
132
+ 2. Consequence: Access to all community spaces, tools, and communication
133
+ channels is removed. In general, permanent bans should be rarely used,
134
+ should have strong reasoning behind them, and should only be resorted to
135
+ if working through other remedies has failed to change the behavior.
136
+ 3. Repair: There is no possible repair in cases of this severity.
137
+
138
+ This enforcement ladder is intended as a guideline. It does not limit the
139
+ ability of Community Managers to use their discretion and judgment, in keeping
140
+ with the best interests of our community.
50
141
 
51
142
  ## Scope
52
143
 
53
- This Code of Conduct applies within all community spaces, and also applies when
54
- an individual is officially representing the community in public spaces.
55
- Examples of representing our community include using an official email address,
56
- posting via an official social media account, or acting as an appointed
57
- representative at an online or offline event.
58
-
59
- ## Enforcement
60
-
61
- Instances of abusive, harassing, or otherwise unacceptable behavior may be
62
- reported to the community leaders responsible for enforcement at [INSERT CONTACT
63
- METHOD]. All complaints will be reviewed and investigated promptly and fairly.
64
-
65
- All community leaders are obligated to respect the privacy and security of the
66
- reporter of any incident.
67
-
68
- ## Enforcement Guidelines
69
-
70
- Community leaders will follow these Community Impact Guidelines in determining
71
- the consequences for any action they deem in violation of this Code of Conduct:
72
-
73
- ### 1. Correction
74
-
75
- **Community Impact**: Use of inappropriate language or other behavior deemed
76
- unprofessional or unwelcome in the community.
77
-
78
- **Consequence**: A private, written warning from community leaders, providing
79
- clarity around the nature of the violation and an explanation of why the
80
- behavior was inappropriate. A public apology may be requested.
81
-
82
- ### 2. Warning
83
-
84
- **Community Impact**: A violation through a single incident or series of
85
- actions.
86
-
87
- **Consequence**: A warning with consequences for continued behavior. No
88
- interaction with the people involved, including unsolicited interaction with
89
- those enforcing the Code of Conduct, for a specified period of time. This
90
- includes avoiding interactions in community spaces as well as external channels
91
- like social media. Violating these terms may lead to a temporary or permanent
92
- ban.
93
-
94
- ### 3. Temporary Ban
95
-
96
- **Community Impact**: A serious violation of community standards, including
97
- sustained inappropriate behavior.
98
-
99
- **Consequence**: A temporary ban from any sort of interaction or public
100
- communication with the community for a specified period of time. No public or
101
- private interaction with the people involved, including unsolicited interaction
102
- with those enforcing the Code of Conduct, is allowed during this period.
103
- Violating these terms may lead to a permanent ban.
104
-
105
- ### 4. Permanent Ban
106
-
107
- **Community Impact**: Demonstrating a pattern of violation of community
108
- standards, including sustained inappropriate behavior, harassment of an
109
- individual, or aggression toward or disparagement of classes of individuals.
110
-
111
- **Consequence**: A permanent ban from any sort of public interaction within the
112
- community.
144
+ This Code of Conduct applies within all community spaces, and also applies
145
+ when an individual is officially representing the community in public or other
146
+ spaces. Examples of representing our community include using an official email
147
+ address, posting via an official social media account, or acting as an
148
+ appointed representative at an online or offline event.
113
149
 
114
150
  ## Attribution
115
151
 
116
- This Code of Conduct is adapted from the [Contributor Covenant][homepage],
117
- version 2.1, available at
118
- <https://www.contributor-covenant.org/version/2/1/code_of_conduct.html>.
152
+ This Code of Conduct is adapted from the Contributor Covenant, version 3.0,
153
+ permanently available at <https://www.contributor-covenant.org/version/3/0/>.
119
154
 
120
- Community Impact Guidelines were inspired by
121
- [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
155
+ Contributor Covenant is stewarded by the Organization for Ethical Source and
156
+ licensed under CC BY-SA 4.0. To view a copy of this license, visit
157
+ <https://creativecommons.org/licenses/by-sa/4.0/>.
122
158
 
123
- For answers to common questions about this code of conduct, see the FAQ at
124
- <https://www.contributor-covenant.org/faq>. Translations are available at
125
- <https://www.contributor-covenant.org/translations>.
159
+ For answers to common questions about Contributor Covenant, see the FAQ at
160
+ <https://www.contributor-covenant.org/faq>. Translations are provided at
161
+ <https://www.contributor-covenant.org/translations>. Additional enforcement
162
+ and community guideline resources can be found at
163
+ <https://www.contributor-covenant.org/resources>. The enforcement ladder was
164
+ inspired by the work of [Mozilla’s code of conduct team][inclusion].
126
165
 
127
- [homepage]: https://www.contributor-covenant.org
128
- [Mozilla CoC]: https://github.com/mozilla/diversity
166
+ [advisory]: https://github.com/halostatue/minitar/security/advisories/new
167
+ [inclusion]: https://github.com/mozilla/inclusion