Doc files updated (#445)

Doc files updated

.github/workflows/integrate.yml

@@ -226,7 +226,7 @@ jobs:
 
       - name: "Check exported files"
         run: |
-          EXPECTED="LICENSE,README.md,SECURITY.md,composer.json,link,package.json"
+          EXPECTED="LICENSE,README.md,RELEASES.md,SECURITY.md,composer.json,link,package.json"
           CURRENT="$(git archive HEAD | tar --list --exclude="src" --exclude="src/*" | paste -s -d ",")"
           echo "CURRENT =${CURRENT}"
           echo "EXPECTED=${EXPECTED}"

CODE_OF_CONDUCT.md

@@ -11,19 +11,19 @@ religion, or sexual identity and orientation.
 
 Examples of behavior that contributes to creating a positive environment include:
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+-   Using welcoming and inclusive language
+-   Being respectful of differing viewpoints and experiences
+-   Gracefully accepting constructive criticism
+-   Focusing on what is best for the community
+-   Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
+-   The use of sexualized language or imagery and unwelcome sexual attention or advances
+-   Trolling, insulting/derogatory comments, and personal or political attacks
+-   Public or private harassment
+-   Publishing others' private information, such as a physical or electronic address, without explicit permission
+-   Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
@@ -57,5 +57,4 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage], versi
 at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
-
 [version]: http://contributor-covenant.org/version/1/4/

README.md

@@ -1,5 +1,4 @@
-Webauthn Framework
-==================
+# Webauthn Framework
 
 ![Build Status](https://github.com/web-auth/webauthn-framework/workflows/Integrate/badge.svg)
 

RELEASES.md

@@ -0,0 +1,21 @@
+# Versioning and Release
+
+This document describes the versioning and release process of the Webauthn Framework.
+This document is a living document, contents will be updated according to each release.
+
+## Releases
+
+Webauthn Framework releases will be versioned using dotted triples, similar to [Semantic Version](http://semver.org/).
+For this specific document, we will refer to the respective components of this triple as `<major>.<minor>.<patch>`.
+The version number may have additional information, such as "-rc1,-rc2,-rc3" to mark release candidate builds for earlier access.
+Such releases will be considered as "pre-releases".
+
+## Minor Release Support Matrix
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 4.7.x   | :white_check_mark: |
+| 4.6.x   | :white_check_mark: |
+| 4.5.x   | :white_check_mark: |
+| 3.3.x   | :white_check_mark: |
+| < 3.3.x | :x:                |

SECURITY.md

@@ -1,14 +1,74 @@
-# Security Policy
+# Security Release Process
+
+Webauthn Framework is devoted in providing the best experience for all developers who want to implement Webauthn in their applications.
+Spomky-Labs has adopted this security disclosure and response policy to ensure we responsibly handle critical issues.
 
 ## Supported Versions
 
-| Version | Supported          |
-|---------| ------------------ |
-| 4.x.x   | :white_check_mark: |
-| 3.3.x   | :white_check_mark: |
-| < 3.3.x | :x:                |
+The Webauthn Framework project maintains release branches for the three most recent minor releases.
+Applicable fixes, including security fixes, may be backported to those three release branches, depending on severity and feasibility. Please refer to [RELEASES.md](RELEASES.md) for details.
+
+## Reporting a Vulnerability - Private Disclosure Process
+
+Security is of the highest importance and all security vulnerabilities or suspected security vulnerabilities should be reported to Webauthn Framework privately, to minimize attacks against current users of the Webauthn Framework before they are fixed.
+Vulnerabilities will be investigated and patched on the next patch (or minor) release as soon as possible.
+This information could be kept entirely internal to the project.
+
+If you know of a publicly disclosed security vulnerability for the Webauthn Framework, please **IMMEDIATELY** contact security@spomky-labs.com to inform the Webauthn Framework Security Team.
+
+**IMPORTANT: Do not file public issues on GitHub for security vulnerabilities**
+
+To report a vulnerability or a security-related issue, please email the private address security@spomky-labs.com with the details of the vulnerability.
+The email will be fielded by the Webauthn Framework Security Team, which is made up of the Webauthn Framework maintainers who have committer and release permissions.
+Do not report non-security-impacting bugs through this channel. Use [GitHub issues](https://github.com/web-auth/webauthn-framework/issues/new/choose) instead.
+
+Emails can be encrypted if you wish to share the vulnerability details securely.
+The Webauthn Framework Security Team's PGP is key is available on the [PGP keyservers](https://keys.openpgp.org/search?q=security%40spomky-labs.com).
+
+### Proposed Email Content
+
+Provide a descriptive subject line and in the body of the email include the following information:
+
+-   Basic identity information, such as your name and your affiliation or company.
+-   Detailed steps to reproduce the vulnerability (POC scripts, screenshots, and compressed packet captures are all helpful to us).
+-   Description of the effects of the vulnerability on Webauthn Framework and the related hardware and software configurations, so that the Webauthn Framework Security Team can reproduce it.
+-   How the vulnerability affects Webauthn Framework usage and an estimation of the attack surface, if there is one.
+-   List other projects or dependencies that were used in conjunction with Webauthn Framework to produce the vulnerability.
+
+## When to report a vulnerability
+
+-   When you think Webauthn Framework has a potential security vulnerability.
+-   When you suspect a potential vulnerability, but you are unsure that it impacts Webauthn Framework.
+-   When you know of or suspect a potential vulnerability on another project that is used by Webauthn Framework. For example Webauthn Framework has a dependency on Docker, PGSql, Redis, Notary, Trivy, etc.
+
+## Patch, Release, and Disclosure
+
+The Webauthn Framework Security Team will respond to vulnerability reports as follows:
+
+1.  The Security Team will investigate the vulnerability and determine its effects and criticality.
+2.  If the issue is not deemed to be a vulnerability, the Security Team will follow up with a detailed reason for rejection.
+3.  The Security Team will initiate a conversation with the reporter as soon as possible.
+4.  If a vulnerability is acknowledged and the timeline for a fix is determined, the Security Team will work on a plan to communicate with the appropriate community, including identifying mitigating steps that affected users can take to protect themselves until the fix is rolled out.
+5.  The Security Team will work on fixing the vulnerability and perform internal testing before preparing to roll out the fix.
+6.  A public disclosure date is negotiated by the Webauthn Framework Security Team and the bug submitter. We prefer to fully disclose the bug as soon as possible once a user mitigation or patch is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for distributor coordination. The timeframe for disclosure is from immediate (especially if it’s already publicly known) to a few weeks. For a critical vulnerability with a straightforward mitigation, we expect report date to public disclosure date to be on the order of 14 business days. The Webauthn Framework Security Team holds the final say when setting a public disclosure date.
+7.  Once the fix is confirmed, the Security Team will patch the vulnerability in the next patch or minor release, and backport a patch release into all earlier supported releases. Upon release of the patched version of Webauthn Framework, we will follow the **Public Disclosure Process**.
+
+### Public Disclosure Process
+
+The Security Team publishes a public [advisory](https://github.com/web-auth/webauthn-framework/security/advisories) to the Webauthn Framework community via GitHub. In most cases, additional communication via Twitter, blog and other channels will assist in educating Webauthn Framework users and rolling out the patched release to affected users.
+
+The Security Team will also publish any mitigating steps users can take until the fix can be applied to their Webauthn Framework instances. Webauthn Framework distributors will handle creating and publishing their own security advisories.
+
+## Mailing lists
+
+-   Use security@spomky-labs.com to report security concerns to the Webauthn Framework Security Team, who uses the list to privately discuss security issues and fixes prior to disclosure.
+
+## Early Disclosure to Webauthn Framework Distributors List
+
+This private list is intended to be used primarily to provide actionable information to multiple distributor projects at once. This list is not intended to inform individuals about security issues.
 
-## Reporting a Vulnerability
+## Confidentiality, integrity and availability
 
-If you think you have found a security issue, DO NOT open an issue. You MUST email your issue: security AT
-spomky-labs.com.
+We consider vulnerabilities leading to the compromise of data confidentiality, elevation of privilege, or integrity to be our highest priority concerns.
+Availability, in particular in areas relating to DoS and resource exhaustion, is also a serious security concern.
+The Webauthn Framework Security Team takes all vulnerabilities, potential vulnerabilities, and suspected vulnerabilities seriously and will investigate them in an urgent and expeditious manner.

infection.json

@@ -1,8 +1,6 @@
 {
     "source": {
-        "directories": [
-            "src"
-        ]
+        "directories": ["src"]
     },
     "logs": {
         "text": "infection.log"

src/symfony/README.md

@@ -21,7 +21,7 @@ The official documentation is available at https://github.com/web-auth/webauthn-
 
 # Missing Features
 
-- [Extension support](https://www.w3.org/TR/webauthn/#extensions) is implemented but not fully tested
+-   [Extension support](https://www.w3.org/TR/webauthn/#extensions) is implemented but not fully tested
 
 # Support