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 May 15, 2024
1 parent c8e5c7b commit 44356b9
Show file tree
Hide file tree
Showing 6 changed files with 3 additions and 3 deletions.
Binary file modified refs/pull/281/merge/en/.doctrees/environment.pickle
Binary file not shown.
Binary file modified refs/pull/281/merge/en/.doctrees/wallet-attestation.doctree
Binary file not shown.
2 changes: 1 addition & 1 deletion refs/pull/281/merge/en/_sources/wallet-attestation.rst.txt
Original file line number Diff line number Diff line change
Expand Up @@ -104,7 +104,7 @@ Wallet Instance Initialization and Registration
**Device Integrity Service:** In this section the Device Integrity Service is considered as it is provided by device manufacturers. This service allows the verification of a key being securely stored within the device's hardware through a signed object. Additionally, it offers the verifiable proof that a specific Wallet Instance is authentic, unaltered, and in its original state using a specialized signed document made for this scope.

The service also incorporates details in the signed object, such as the device type, model, app version, operating system version, bootloader status, and other relevant information to assess the device has not been compromised. For Android the service used is `Key Attestation`_ in addition to `Play Integrity API`_, while for iOS the `DeviceCheck`_ service.
This service, being custom made by the manufacturer, is already implemented within the Android or iOS SDKs therefore it is not necessary to have any hardcoded endpoint to reach it. Furthermore, being a custom service, it will not have to be part of the federation.
This service, specifically developed by the manufacturer, is already integrated within the Android or iOS SDKs, so there is no need for a predefined endpoint to access it. Moreover, as it is specifically developed in the mobile architecture, it does not need to be registered as a Federation Entity, though the national accreditation systems.

**Step 8**: The Device Integrity Service performs the following actions:

Expand Down
2 changes: 1 addition & 1 deletion refs/pull/281/merge/en/searchindex.js

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion refs/pull/281/merge/en/wallet-attestation.html
Original file line number Diff line number Diff line change
Expand Up @@ -1163,7 +1163,7 @@ <h3>Wallet Instance Initialization and Registration<a class="headerlink" href="#
<p class="admonition-title">Note</p>
<p><strong>Device Integrity Service:</strong> In this section the Device Integrity Service is considered as it is provided by device manufacturers. This service allows the verification of a key being securely stored within the device's hardware through a signed object. Additionally, it offers the verifiable proof that a specific Wallet Instance is authentic, unaltered, and in its original state using a specialized signed document made for this scope.</p>
<p>The service also incorporates details in the signed object, such as the device type, model, app version, operating system version, bootloader status, and other relevant information to assess the device has not been compromised. For Android the service used is <a class="reference external" href="https://developer.android.com/privacy-and-security/security-key-attestation">Key Attestation</a> in addition to <a class="reference external" href="https://developer.android.com/google/play/integrity?hl=it">Play Integrity API</a>, while for iOS the <a class="reference external" href="https://developer.apple.com/documentation/devicecheck">DeviceCheck</a> service.
This service, being custom made by the manufacturer, is already implemented within the Android or iOS SDKs therefore it is not necessary to have any hardcoded endpoint to reach it. Furthermore, being a custom service, it will not have to be part of the federation.</p>
This service, specifically developed by the manufacturer, is already integrated within the Android or iOS SDKs, so there is no need for a predefined endpoint to access it. Moreover, as it is specifically developed in the mobile architecture, it does not need to be registered as a Federation Entity, though the national accreditation systems.</p>
</div>
<p><strong>Step 8</strong>: The Device Integrity Service performs the following actions:</p>
<ul class="simple">
Expand Down
Binary file modified refs/pull/281/merge/it/.doctrees/environment.pickle
Binary file not shown.

0 comments on commit 44356b9

Please sign in to comment.