Skip to content

Minor fixes for #157 #159

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nightwatchcyber merged 2 commits into from
Jun 17, 2019
Merged

Minor fixes for #157 #159

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0aa21e5
Fixes for #157
nightwatchcyber Jun 17, 2019
24c198b
fixes
nightwatchcyber Jun 17, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions draft-foudil-securitytxt.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -339,7 +339,7 @@

<meta name="dct.creator" content="Foudil, E. and Y. Shafranovich" />
<meta name="dct.identifier" content="urn:ietf:id:draft-foudil-securitytxt-06" />
<meta name="dct.issued" scheme="ISO8601" content="2019-06-04" />
<meta name="dct.issued" scheme="ISO8601" content="2019-06-16" />
<meta name="dct.abstract" content="When security vulnerabilities are discovered by independent security researchers, they often lack the channels to report them properly. As a result, security vulnerabilities may be left unreported. This document defines a format (&#8220;security.txt&#8221;) to help organizations describe the process for security researchers to follow in order to report security vulnerabilities." />
<meta name="description" content="When security vulnerabilities are discovered by independent security researchers, they often lack the channels to report them properly. As a result, security vulnerabilities may be left unreported. This document defines a format (&#8220;security.txt&#8221;) to help organizations describe the process for security researchers to follow in order to report security vulnerabilities." />

Expand All @@ -363,12 +363,12 @@
<td class="right">Y. Shafranovich</td>
</tr>
<tr>
<td class="left">Expires: December 6, 2019</td>
<td class="left">Expires: December 18, 2019</td>
<td class="right">Nightwatch Cybersecurity</td>
</tr>
<tr>
<td class="left"></td>
<td class="right">June 04, 2019</td>
<td class="right">June 16, 2019</td>
</tr>


Expand All @@ -384,7 +384,7 @@ <h1 id="rfc.status"><a href="#rfc.status">Status of This Memo</a></h1>
<p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
<p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.</p>
<p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."</p>
<p>This Internet-Draft will expire on December 6, 2019.</p>
<p>This Internet-Draft will expire on December 18, 2019.</p>
<h1 id="rfc.copyrightnotice"><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
<p>Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
<p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.</p>
Expand Down Expand Up @@ -561,7 +561,7 @@ <h1 id="rfc.section.3.2">
<h1 id="rfc.section.3.3">
<a href="#rfc.section.3.3">3.3.</a> <a href="#separate-fields" id="separate-fields">Separate Fields</a>
</h1>
<p id="rfc.section.3.3.p.1">A separate line is REQUIRED for every new value and field. You MUST NOT chain everything into a single field unless defined by that field. Every line MUST end either with a carriage return and line feed characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A).</p>
<p id="rfc.section.3.3.p.1">A separate line is REQUIRED for every field. You MUST NOT chain everything into a single field unless defined by that field. Every line MUST end either with a carriage return and line feed characters (CRLF / %x0D %x0A) or just a line feed character (LF / %x0A).</p>
<h1 id="rfc.section.3.4">
<a href="#rfc.section.3.4">3.4.</a> <a href="#signature" id="signature">Digital signature</a>
</h1>
Expand Down Expand Up @@ -799,12 +799,12 @@ <h1 id="rfc.section.6.2">
<h1 id="rfc.section.6.3">
<a href="#rfc.section.6.3">6.3.</a> <a href="#intentionally-malformed-files-resources-and-reports" id="intentionally-malformed-files-resources-and-reports">Intentionally Malformed Files, Resources and Reports</a>
</h1>
<p id="rfc.section.6.3.p.1">It is possible for attackers to generate files that are extraordinarily large or otherwise malformed in an attempt to discover or exploit weaknesses in parsing code. Implementors SHOULD make sure that any such code be robust against large and malformed files. ABNF grammar (as defined in <a href="#abnf" class="xref">Section 5</a>) SHOULD be used as a way to verify these files.</p>
<p id="rfc.section.6.3.p.1">It is possible for attackers to generate files that are extraordinarily large or otherwise malformed in an attempt to discover or exploit weaknesses in parsing code. Implementors SHOULD make sure that any such code is robust against large and malformed files. ABNF grammar (as defined in <a href="#abnf" class="xref">Section 5</a>) SHOULD be used as a way to verify these files.</p>
<p id="rfc.section.6.3.p.2">Same concerns apply to any other resources referenced within security.txt files, as well as any security reports received as a result of publishing this file. Such resources and reports may be hostile, malformed or malicious.</p>
<h1 id="rfc.section.6.4">
<a href="#rfc.section.6.4">6.4.</a> <a href="#no-implied-permission-for-testing" id="no-implied-permission-for-testing">No Implied Permission for Testing</a>
</h1>
<p id="rfc.section.6.4.p.1">The presence of a security.txt file can be interpreted by researchers as providing permission to do security testing against that asset. This can lead to increased testing against an organization by researchers. On the other hand, a decision not to publish a security.txt file, can be interpreted by the organization operating that website to be a way to signal to researchers that permission to test that particular site or project is denied. This can lead to pushback against researchers reporting security issues to that organization.</p>
<p id="rfc.section.6.4.p.1">The presence of a security.txt file can be interpreted by researchers as providing permission to do security testing against that asset. This can lead to increased testing against an organization by researchers. On the other hand, a decision not to publish a security.txt file can be interpreted by the organization operating that website to be a way to signal to researchers that permission to test that particular site or project is denied. This can lead to pushback against researchers reporting security issues to that organization.</p>
<p id="rfc.section.6.4.p.2">Therefore, implementors MUST NOT assume that presence or absence of a &#8220;security.txt&#8221; file grants or denies permission for security testing. Any such permission MAY be defined in a security or disclosure policy (as per <a href="#policy" class="xref">Section 3.5.6</a>) or a new directive (as per <a href="#extensibility" class="xref">Section 4.4</a>).</p>
<h1 id="rfc.section.6.5">
<a href="#rfc.section.6.5">6.5.</a> <a href="#multi-user-environments" id="multi-user-environments">Multi-user Environments</a>
Expand All @@ -813,7 +813,7 @@ <h1 id="rfc.section.6.5">
<h1 id="rfc.section.6.6">
<a href="#rfc.section.6.6">6.6.</a> <a href="#protecting-data-in-transit" id="protecting-data-in-transit">Protecting Data in Transit</a>
</h1>
<p id="rfc.section.6.6.p.1">To protect a &#8220;security.txt&#8221; file from being tampered in transit, implementors MUST use HTTPS when serving the file itself and any web URLs referenced in it (except as noted in this specification). Implementors MUST also perform the correct TLS verification (as per <a href="#RFC6125" class="xref">[RFC6125]</a>).</p>
<p id="rfc.section.6.6.p.1">To protect a &#8220;security.txt&#8221; file from being tampered with in transit, implementors MUST use HTTPS when serving the file itself and any web URLs referenced in it (except as noted in this specification). Implementors MUST also perform the correct TLS verification (as per <a href="#RFC6125" class="xref">[RFC6125]</a>).</p>
<p id="rfc.section.6.6.p.2">As an additional layer of protection, it is also RECOMMENDED that organizations digitally sign their &#8220;security.txt&#8221; file with OpenPGP (as per <a href="#signature" class="xref">Section 3.4</a>). Also, to protect security reports from being tampered with or observed while in transit, organizations SHOULD specify encryption keys (as per <a href="#encryption" class="xref">Section 3.5.4</a>) unless HTTPS is being used.</p>
<p id="rfc.section.6.6.p.3">However, the determination of validity of keys being used is out of scope for this specification. Implementors MUST establish other secure means to verify these keys.</p>
<h1 id="rfc.section.6.7">
Expand Down
8 changes: 4 additions & 4 deletions draft-foudil-securitytxt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ respective field.

## Separate Fields

A separate line is REQUIRED for every new value and field. You MUST
A separate line is REQUIRED for every field. You MUST
NOT chain everything into a single field unless defined by that field. Every line MUST end either
with a carriage return and line feed characters (CRLF / %x0D %x0A) or just
a line feed character (LF / %x0A).
Expand Down Expand Up @@ -508,7 +508,7 @@ and are kept secure.
It is possible for attackers to generate files that are extraordinarily
large or otherwise malformed in an attempt to discover or exploit weaknesses
in parsing code. Implementors SHOULD make sure that any such code
be robust against large and malformed files. ABNF grammar (as defined in
is robust against large and malformed files. ABNF grammar (as defined in
{{abnf}}) SHOULD be used as a way to verify these files.

Same concerns apply to any other resources referenced within security.txt
Expand All @@ -520,7 +520,7 @@ this file. Such resources and reports may be hostile, malformed or malicious.
The presence of a security.txt file can be interpreted by researchers
as providing permission to do security testing against that asset.
This can lead to increased testing against an organization by researchers. On the other hand, a decision not
to publish a security.txt file, can be interpreted by the
to publish a security.txt file can be interpreted by the
organization operating that website to be a way to signal to researchers
that permission to test that particular site or project is denied. This can lead to pushback against
researchers reporting security issues to that organization.
Expand All @@ -539,7 +539,7 @@ the "security.txt" AND "/.well-known/security.txt" names.

## Protecting Data in Transit

To protect a "security.txt" file from being tampered in transit, implementors MUST use
To protect a "security.txt" file from being tampered with in transit, implementors MUST use
HTTPS when serving the file itself and any web URLs referenced in it (except as noted in
this specification). Implementors MUST also perform the correct TLS
verification (as per {{!RFC6125}}).
Expand Down
Loading