Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Document device attestation and verification

Open
  • Is something wrong?
#3,745 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
android
Domain
documentation, security

Research direction

Start by locating the admin and user documentation sections covering the posture check wizard, edit form, Devices list, verification flow, and device-blocked screens. Trace the existing desktop tray, full-window, and mobile client guidance, then document the listed statuses, supported platforms, enforcement timing, and verification actions. Done means every acceptance criterion is covered with clear instructions for administrators and users.

Written by the indexing model from the issue text.

Description

Acceptance criteria

Admin documentation

  • An overview explains the attestation statuses (Not attested, Attested, On quarantine, Attested manually), the verification statuses (Verified, Not verified) and the Blocked access state.
  • Supported platforms are listed: desktop TPM, Apple Secure Enclave and Android Keystore, plus the minimum Defguard client versions.
  • The EK CA database page in Settings is described, including CAs marked "Manually added".
  • Configuring attestation and ownership verification is covered, both in the posture check wizard and in the edit form, including how to read the impact tables.
  • The docs explain how enforcement works and that changes apply at the device's next connection.
  • The Devices list, its filters and the Device details panel are described.
  • The verification flow is covered: initiate, compare the code, verify or cancel, and share instructions with the user.
  • "Mark as verified", blocking a device, and restarting verification to unblock it are described.
  • Handling unrecognised devices and accepting an unknown TPM is covered.

User documentation

  • The docs explain how to verify a device in the desktop client (tray view and full window) and in the mobile client.
  • The messages shown when a connection is rejected are explained, with what to do for each.
  • The "Device blocked" screen is explained, with how to start verification from it.
Dominant language
Rust
Stars
2.9k
Forks
119
Avg merge
1d 2h
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DefGuard/defguard

All issues in DefGuard/defguard

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.