pax_global_header00006660000000000000000000000064146375301440014521gustar00rootroot0000000000000052 comment=cc0c7c22623c60ea84e057912d2b1833faf5957f golang-github-go-webauthn-webauthn-0.10.2/000077500000000000000000000000001463753014400203615ustar00rootroot00000000000000golang-github-go-webauthn-webauthn-0.10.2/.commitlintrc.yml000066400000000000000000000007661463753014400236770ustar00rootroot00000000000000extends: - '@commitlint/config-conventional' rules: body-max-line-length: [2, always, Infinity] body-min-length: [2, always, 20] header-case: [2, always, lower-case] header-max-length: [2, always, 72] type-enum: [2, always ["build", "ci", "docs", "feat", "fix", "perf", "refactor", "revert", "test"]] scope-enum: [2, always, ["metadata", "protocol", "webauthn"]] defaultIgnores: true helpUrl: 'https://github.com/go-webauthn/webauthn/blob/master/CONTRIBUTING.md#commit-message-convention'golang-github-go-webauthn-webauthn-0.10.2/.github/000077500000000000000000000000001463753014400217215ustar00rootroot00000000000000golang-github-go-webauthn-webauthn-0.10.2/.github/CODEOWNERS000066400000000000000000000001411463753014400233100ustar00rootroot00000000000000# The maintainers team is a code owner for the whole repository. * @go-webauthn/maintainersgolang-github-go-webauthn-webauthn-0.10.2/.github/ISSUE_TEMPLATE/000077500000000000000000000000001463753014400241045ustar00rootroot00000000000000golang-github-go-webauthn-webauthn-0.10.2/.github/ISSUE_TEMPLATE/bug-report.yml000066400000000000000000000030621463753014400267160ustar00rootroot00000000000000--- name: Bug Report description: Report a potential bug labels: - type/potential-bug - status/needs-triage - priority/normal body: - type: markdown attributes: value: | Thanks for taking the time to fill out this bug report. Please try to give as much information as possible for us to be able to reproduce the issue and provide a quick fix. - type: dropdown id: version attributes: label: Version description: What version of the library are you using or which versions do you see the issue in? multiple: true options: - 0.10.1 - 0.10.0 - 0.9.4 - 0.9.3 - 0.9.2 - 0.9.1 - 0.9.0 - 0.8.6 - 0.8.5 - 0.8.4 - 0.8.3 - 0.8.2 - 0.8.1 - 0.8.0 validations: required: true - type: textarea id: description attributes: label: Description description: Describe the bug validations: required: true - type: textarea id: reproduction attributes: label: Reproduction description: Describe how we can reproduce this issue validations: required: true - type: textarea id: expectations attributes: label: Expectations description: Describe the desired or expected results validations: required: false - type: textarea id: documentation attributes: label: Documentation description: Provide any relevant specification or other documentation if applicable validations: required: false ... golang-github-go-webauthn-webauthn-0.10.2/.github/ISSUE_TEMPLATE/config.yml000066400000000000000000000004401463753014400260720ustar00rootroot00000000000000--- blank_issues_enabled: false contact_links: - name: Documentation url: https://github.com/go-webauthn/webauthn about: Read the documentation - name: Question/Other url: https://github.com/go-webauthn/webauthn/discussions/new about: Discuss other questions etc. ... golang-github-go-webauthn-webauthn-0.10.2/.github/ISSUE_TEMPLATE/feature-request.yml000066400000000000000000000012701463753014400277500ustar00rootroot00000000000000--- name: Feature Request description: Request a feature labels: - type/feature-request - status/needs-triage - priority/normal body: - type: textarea id: description attributes: label: Description description: Provide a description of the feature validations: required: true - type: textarea id: use-case attributes: label: Use Case description: Provide a use case if applicable validations: required: false - type: textarea id: documentation attributes: label: Documentation description: Provide any relevant specification or other documentation if applicable validations: required: false ...golang-github-go-webauthn-webauthn-0.10.2/.github/workflows/000077500000000000000000000000001463753014400237565ustar00rootroot00000000000000golang-github-go-webauthn-webauthn-0.10.2/.github/workflows/go.yml000066400000000000000000000014621463753014400251110ustar00rootroot00000000000000name: Go on: pull_request: {} push: branches: - master jobs: build: name: Build runs-on: ubuntu-latest strategy: matrix: go: - '1.20' - '1.21' - '1.22' fail-fast: false steps: - name: Set up Go ${{ matrix.go }} uses: actions/setup-go@v3 with: go-version: ${{ matrix.go }} - name: Check out code into the Go module directory uses: actions/checkout@v3 - name: Get dependencies run: | go get -v -t -d ./... if [ -f Gopkg.toml ]; then curl https://raw.githubusercontent.com/golang/dep/master/install.sh | sh dep ensure fi - name: Build run: go build -v ./... - name: Test run: go test -v ./... golang-github-go-webauthn-webauthn-0.10.2/.gitignore000066400000000000000000000071211463753014400223520ustar00rootroot00000000000000# Created by https://www.toptal.com/developers/gitignore/api/go,osx,linux,goland,windows,visualstudiocode # Edit at https://www.toptal.com/developers/gitignore?templates=go,osx,linux,goland,windows,visualstudiocode ### Go ### # Binaries for programs and plugins *.exe *.exe~ *.dll *.so *.dylib # Test binary, built with `go test -c` *.test # Output of the go coverage tool, specifically when used with LiteIDE *.out # Dependency directories (remove the comment below to include it) # vendor/ ### Go Patch ### /vendor/ /Godeps/ ### Goland ### # Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm, Rider and Goland # Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839 # User-specific stuff .idea/**/workspace.xml .idea/**/tasks.xml .idea/**/usage.statistics.xml .idea/**/dictionaries .idea/**/shelf # AWS User-specific .idea/**/aws.xml # Generated files .idea/**/contentModel.xml # Sensitive or high-churn files .idea/**/dataSources/ .idea/**/dataSources.ids .idea/**/dataSources.local.xml .idea/**/sqlDataSources.xml .idea/**/dynamic.xml .idea/**/uiDesigner.xml .idea/**/dbnavigator.xml # Gradle .idea/**/gradle.xml .idea/**/libraries # Gradle and Maven with auto-import # When using Gradle or Maven with auto-import, you should exclude module files, # since they will be recreated, and may cause churn. Uncomment if using # auto-import. # .idea/artifacts # .idea/compiler.xml # .idea/jarRepositories.xml # .idea/modules.xml # .idea/*.iml # .idea/modules # *.iml # *.ipr # CMake cmake-build-*/ # Mongo Explorer plugin .idea/**/mongoSettings.xml # File-based project format *.iws # IntelliJ out/ # mpeltonen/sbt-idea plugin .idea_modules/ # JIRA plugin atlassian-ide-plugin.xml # Cursive Clojure plugin .idea/replstate.xml # Crashlytics plugin (for Android Studio and IntelliJ) com_crashlytics_export_strings.xml crashlytics.properties crashlytics-build.properties fabric.properties # Editor-based Rest Client .idea/httpRequests # Ignores the whole .idea folder and all .iml files .idea/ # Android studio 3.1+ serialized cache file .idea/caches/build_file_checksums.ser ### Linux ### *~ # temporary files which can be created if a process still has a handle open of a deleted file .fuse_hidden* # KDE directory preferences .directory # Linux trash folder which might appear on any partition or disk .Trash-* # .nfs files are created when an open file is removed but is still being accessed .nfs* ### OSX ### # General .DS_Store .AppleDouble .LSOverride # Icon must end with two \r Icon # Thumbnails ._* # Files that might appear in the root of a volume .DocumentRevisions-V100 .fseventsd .Spotlight-V100 .TemporaryItems .Trashes .VolumeIcon.icns .com.apple.timemachine.donotpresent # Directories potentially created on remote AFP share .AppleDB .AppleDesktop Network Trash Folder Temporary Items .apdisk ### VisualStudioCode ### .vscode/* !.vscode/settings.json !.vscode/tasks.json !.vscode/launch.json !.vscode/extensions.json *.code-workspace # Local History for Visual Studio Code .history/ ### VisualStudioCode Patch ### # Ignore all local history of files .history .ionide # Support for Project snippet scope !.vscode/*.code-snippets ### Windows ### # Windows thumbnail cache files Thumbs.db Thumbs.db:encryptable ehthumbs.db ehthumbs_vista.db # Dump file *.stackdump # Folder config file [Dd]esktop.ini # Recycle Bin used on file shares $RECYCLE.BIN/ # Windows Installer files *.cab *.msi *.msix *.msm *.msp # Windows shortcuts *.lnk # End of https://www.toptal.com/developers/gitignore/api/go,osx,linux,goland,windows,visualstudiocode golang-github-go-webauthn-webauthn-0.10.2/.golangci.yml000066400000000000000000000023521463753014400227470ustar00rootroot00000000000000--- run: timeout: 3m linters-settings: goconst: min-len: 2 min-occurrences: 2 gocyclo: min-complexity: 15 godot: check-all: true goimports: local-prefixes: github.com/go-webauthn/webauthn linters: enable: - asciicheck - goconst - gocritic - gocyclo - godot - gofmt - goimports - gosec - misspell - nolintlint - prealloc - revive - unconvert - unparam - whitespace - wsl issues: exclude: - Error return value of .((os\.)?std(out|err)\..*|.*Close|.*Flush|os\.Remove(All)?|.*printf?|os\.(Un)?Setenv). is not checked # yamllint disable-line rule:line-length - func name will be used as test\.Test.* by other packages, and that stutters; consider calling this - (possible misuse of unsafe.Pointer|should have signature) - ineffective break statement. Did you mean to break out of the outer loop - Use of unsafe calls should be audited - Subprocess launch(ed with variable|ing should be audited) - (G104|G307) - (Expect directory permissions to be 0750 or less|Expect file permissions to be 0600 or less) - Potential file inclusion via variable exclude-use-default: false max-issues-per-linter: 0 max-same-issues: 0 ... golang-github-go-webauthn-webauthn-0.10.2/.renovaterc000066400000000000000000000011431463753014400225310ustar00rootroot00000000000000{ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "constraints": { "go": "1.21" }, "extends": [ "config:base", ":semanticCommitTypeAll(build)", ":separatePatchReleases" ], "ignorePresets": [ ":combinePatchMinorReleases", ":prHourlyLimit2", ":semanticPrefixFixDepsChoreOthers" ], "enabledManagers": [ "gomod" ], "labels": [ "dependencies" ], "packageRules": [ { "datasources": [ "go" ], "addLabels": [ "go" ] } ], "postUpdateOptions": [ "gomodTidy", "gomodNoMassage" ] }golang-github-go-webauthn-webauthn-0.10.2/CODE_OF_CONDUCT.md000066400000000000000000000121171463753014400231620ustar00rootroot00000000000000# Contributor Covenant Code of Conduct ## Our Pledge We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: * Demonstrating empathy and kindness toward other people * Being respectful of differing opinions, viewpoints, and experiences * Giving and gracefully accepting constructive feedback * Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience * Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: * The use of sexualized language or imagery, and sexual attention or advances of any kind * Trolling, insulting or derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or email address, without their explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Enforcement Responsibilities Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact**: A violation through a single incident or series of actions. **Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact**: A serious violation of community standards, including sustained inappropriate behavior. **Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence**: A permanent ban from any sort of public interaction within the community. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity). [homepage]: https://www.contributor-covenant.org For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations. golang-github-go-webauthn-webauthn-0.10.2/CONTRIBUTING.md000066400000000000000000000124471463753014400226220ustar00rootroot00000000000000# Contributing Guidelines ## Pull Request Conventions It's encouraged to discuss proposed changes prior to opening a PR, especially when the change is large. Pull request subjects should have the same format as the [Commit Message Header](#commit-message-header). ### Documentation / Specifications You should include reference documentation specifically if there is a section in the W3C Webauthn specification that relates to your pull request and explain in the PR how it implements the spec or implements the spec more closely. ### Force Push Force pushing once a pull request has been opened is heavily frowned upon. All pull requests will be merged using `git merge --squash` to avoid cluttering the master branch history with changes made during the review process. As such the only purpose force pushing to a branch once a pull request is opened is making it harder for reviewers to review your code; especially if a review has already taken place or has been started. ## Commit Message Convention _This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format]. This is an adapted version of the [Angular commit guidelines]._ We have very precise rules over how our Git commit messages must be formatted. This format leads to **easier to read commit history**. Each commit message consists of a **header**, a **body**, and a **footer**. ```