Skip to content

Commit

Permalink
Deploy to GitHub pages
Browse files Browse the repository at this point in the history
  • Loading branch information
github-actions[bot] authored Mar 29, 2024
1 parent 940e557 commit ed7234c
Show file tree
Hide file tree
Showing 11 changed files with 122 additions and 88 deletions.
Binary file modified refs/pull/242/merge/en/.doctrees/defined-terms.doctree
Binary file not shown.
Binary file modified refs/pull/242/merge/en/.doctrees/environment.pickle
Binary file not shown.
Binary file modified refs/pull/242/merge/en/.doctrees/wallet-attestation.doctree
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 5 additions & 5 deletions refs/pull/242/merge/en/_sources/defined-terms.rst.txt
Original file line number Diff line number Diff line change
Expand Up @@ -38,15 +38,15 @@ Below are the description of acronyms and definitions which are useful for furth
* - Wallet Attestation
- Verifiable Attestation, issued by the Wallet Provider, that proves the security compliace of the Wallet Instance.
* - Wallet Secure Cryptographic Device
- Hardware-backed secure environment for creating, storing, and/or managing cryptographic keys and data. Examples include Secure Elements (SE), Trusted Execution Environments (TEEs), and Strongbox.
- Hardware-backed secure environment for creating, storing, and/or managing cryptographic keys and data. A WSCD MAY implement an association proof in different ways. This largely depends on the implementation of the WSCD for example: remote HSM, external smart card, internal UICC, internal native cryptographic hardware, such as the iOS Secure Enclave or the Android Hardware Backed Keystore or StrongBox
* - Credential Status Attestation
- Verifiable Attestation proving that a related Digital Credential is not revoked.
* - Device Integrity Service
- A service provided by device manufacturers that verifies the integrity and authenticity of the app instance (Wallet Instance), as well as certifying the secure storage of private keys generated by the device within its dedicated hardware. It's important to note that the terminology used to describe this service varies among manufacturers.
* - Wallet Hardware Keys
- During the app initialization, the Wallet Instance generates a pair of keys, one public and one private, which remain valid for the entire duration of the Wallet Instance's life. Functioning as a Master Key for the personal device, these Wallet Hardware Keys are confined to the OS domain and are not designed for signing arbitrary payloads. Their primary role is to provide a unique identification for each Wallet Instance.
* - Wallet Hardware Key Tag
- A unique identifier created by the operating system for the Wallet Hardware Keys, utilized to gain access to the private key stored in the hardware.
* - Cryptographic Hardware Keys
- During the app initialization, the Wallet Instance generates a pair of keys, one public and one private, which remain valid for the entire duration of the Wallet Instance's life. Functioning as a Master Key for the personal device, these Cryptographic Hardware Keys are confined to the OS domain and are not designed for signing arbitrary payloads. Their primary role is to provide a unique identification for each Wallet Instance.
* - Cryptographic Hardware Key Tag
- A unique identifier created by the operating system for the Cryptographic Hardware Keys, utilized to gain access to the private key stored in the hardware.
* - Key Attestation
- An attestation from the device's OEM that enhances your confidence in the keys used in your Wallet Instance being securely stored within the device's hardware-backed keystore.
* - Qualified Electronic Attestation of Attributes (QEAA)
Expand Down
97 changes: 56 additions & 41 deletions refs/pull/242/merge/en/_sources/wallet-attestation.rst.txt

Large diffs are not rendered by default.

10 changes: 5 additions & 5 deletions refs/pull/242/merge/en/defined-terms.html
Original file line number Diff line number Diff line change
Expand Up @@ -1113,19 +1113,19 @@ <h1>Defined Terms<a class="headerlink" href="#defined-terms" title="Permalink to
<td><p>Verifiable Attestation, issued by the Wallet Provider, that proves the security compliace of the Wallet Instance.</p></td>
</tr>
<tr class="row-odd"><td><p>Wallet Secure Cryptographic Device</p></td>
<td><p>Hardware-backed secure environment for creating, storing, and/or managing cryptographic keys and data. Examples include Secure Elements (SE), Trusted Execution Environments (TEEs), and Strongbox.</p></td>
<td><p>Hardware-backed secure environment for creating, storing, and/or managing cryptographic keys and data. A WSCD MAY implement an association proof in different ways. This largely depends on the implementation of the WSCD for example: remote HSM, external smart card, internal UICC, internal native cryptographic hardware, such as the iOS Secure Enclave or the Android Hardware Backed Keystore or StrongBox</p></td>
</tr>
<tr class="row-even"><td><p>Credential Status Attestation</p></td>
<td><p>Verifiable Attestation proving that a related Digital Credential is not revoked.</p></td>
</tr>
<tr class="row-odd"><td><p>Device Integrity Service</p></td>
<td><p>A service provided by device manufacturers that verifies the integrity and authenticity of the app instance (Wallet Instance), as well as certifying the secure storage of private keys generated by the device within its dedicated hardware. It's important to note that the terminology used to describe this service varies among manufacturers.</p></td>
</tr>
<tr class="row-even"><td><p>Wallet Hardware Keys</p></td>
<td><p>During the app initialization, the Wallet Instance generates a pair of keys, one public and one private, which remain valid for the entire duration of the Wallet Instance's life. Functioning as a Master Key for the personal device, these Wallet Hardware Keys are confined to the OS domain and are not designed for signing arbitrary payloads. Their primary role is to provide a unique identification for each Wallet Instance.</p></td>
<tr class="row-even"><td><p>Cryptographic Hardware Keys</p></td>
<td><p>During the app initialization, the Wallet Instance generates a pair of keys, one public and one private, which remain valid for the entire duration of the Wallet Instance's life. Functioning as a Master Key for the personal device, these Cryptographic Hardware Keys are confined to the OS domain and are not designed for signing arbitrary payloads. Their primary role is to provide a unique identification for each Wallet Instance.</p></td>
</tr>
<tr class="row-odd"><td><p>Wallet Hardware Key Tag</p></td>
<td><p>A unique identifier created by the operating system for the Wallet Hardware Keys, utilized to gain access to the private key stored in the hardware.</p></td>
<tr class="row-odd"><td><p>Cryptographic Hardware Key Tag</p></td>
<td><p>A unique identifier created by the operating system for the Cryptographic Hardware Keys, utilized to gain access to the private key stored in the hardware.</p></td>
</tr>
<tr class="row-even"><td><p>Key Attestation</p></td>
<td><p>An attestation from the device's OEM that enhances your confidence in the keys used in your Wallet Instance being securely stored within the device's hardware-backed keystore.</p></td>
Expand Down
2 changes: 1 addition & 1 deletion refs/pull/242/merge/en/searchindex.js

Large diffs are not rendered by default.

Loading

0 comments on commit ed7234c

Please sign in to comment.