all lists on lists.proxmox.com
 help / color / mirror / Atom feed
* [pve-devel] [PATCH pve_flutter_frontend v3] chore: ios: add export compliance key to info.plist
@ 2025-09-30  8:48 Shan Shaji
  2025-10-01 13:54 ` Thomas Lamprecht
  2025-10-02  8:39 ` [pve-devel] applied: " Dominik Csapak
  0 siblings, 2 replies; 3+ messages in thread
From: Shan Shaji @ 2025-09-30  8:48 UTC (permalink / raw)
  To: pve-devel

The app only uses TLS/SSL through iOS platform APIs, which are already
exported by Apple, and is therefore classified under 5A992/5D992 (Mass
Market [1]). Since march 29, 2021, mass market software no longer
requires a self-classification report except for "non-standared"
algorithms.

The `crypto` package is used solely for data integrity with SHA-256
(publicly available, standard algorithm) and not for
confidentiality [3], so it should fall under 5D992. Also this package
should also fall under mass market cryptographic library which
implements a standard algorithm [2] (Table Reference: Third Row).

The `biometric_storage` package relies on iOS platform APIs [4] for
biometrics, which are already exported by Apple. To avoid manually
completing the App Store export compliance step, the
`ITSAppUsesNonExemptEncryption = false` key has been added to
Info.plist.

- [1] https://www.bis.doc.gov/index.php/policy-guidance/encryption/3-license-exception-enc-and-mass-market/a-mass-market
- [2] https://www.bis.doc.gov/index.php/documents/pdfs/2759-table-of-changes-to-enc-in-wa2019-rule-final-version/file
- [3] https://www.bis.doc.gov/index.php/documents/new-encryption/1652-cat-5-part-2-quick-reference-guide/file
- [4] https://github.com/authpass/biometric_storage/blob/main/macos/Classes/BiometricStorageImpl.swift

Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
---
 changes since v1: 
 - Updated commit message with more rationale. 

 ios/Runner/Info.plist | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/ios/Runner/Info.plist b/ios/Runner/Info.plist
index 9949e0f..a5587ed 100644
--- a/ios/Runner/Info.plist
+++ b/ios/Runner/Info.plist
@@ -22,6 +22,8 @@
 	<string>????</string>
 	<key>CFBundleVersion</key>
 	<string>$(FLUTTER_BUILD_NUMBER)</string>
+	<key>ITSAppUsesNonExemptEncryption</key>
+	<false/>
 	<key>LSRequiresIPhoneOS</key>
 	<true/>
 	<key>NSFaceIDUsageDescription</key>
-- 
2.50.1



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [pve-devel] [PATCH pve_flutter_frontend v3] chore: ios: add export compliance key to info.plist
  2025-09-30  8:48 [pve-devel] [PATCH pve_flutter_frontend v3] chore: ios: add export compliance key to info.plist Shan Shaji
@ 2025-10-01 13:54 ` Thomas Lamprecht
  2025-10-02  8:39 ` [pve-devel] applied: " Dominik Csapak
  1 sibling, 0 replies; 3+ messages in thread
From: Thomas Lamprecht @ 2025-10-01 13:54 UTC (permalink / raw)
  To: Proxmox VE development discussion, Shan Shaji

Am 30.09.25 um 10:48 schrieb Shan Shaji:
> The app only uses TLS/SSL through iOS platform APIs, which are already
> exported by Apple, and is therefore classified under 5A992/5D992 (Mass
> Market [1]). Since march 29, 2021, mass market software no longer
> requires a self-classification report except for "non-standared"
> algorithms.
> 
> The `crypto` package is used solely for data integrity with SHA-256
> (publicly available, standard algorithm) and not for
> confidentiality [3], so it should fall under 5D992. Also this package
> should also fall under mass market cryptographic library which
> implements a standard algorithm [2] (Table Reference: Third Row).
> 
> The `biometric_storage` package relies on iOS platform APIs [4] for
> biometrics, which are already exported by Apple. To avoid manually
> completing the App Store export compliance step, the
> `ITSAppUsesNonExemptEncryption = false` key has been added to
> Info.plist.
> 
> - [1] https://www.bis.doc.gov/index.php/policy-guidance/encryption/3-license-exception-enc-and-mass-market/a-mass-market
> - [2] https://www.bis.doc.gov/index.php/documents/pdfs/2759-table-of-changes-to-enc-in-wa2019-rule-final-version/file
> - [3] https://www.bis.doc.gov/index.php/documents/new-encryption/1652-cat-5-part-2-quick-reference-guide/file
> - [4] https://github.com/authpass/biometric_storage/blob/main/macos/Classes/BiometricStorageImpl.swift
> 
> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
> ---
>  changes since v1: 
>  - Updated commit message with more rationale. 
> 
>  ios/Runner/Info.plist | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/ios/Runner/Info.plist b/ios/Runner/Info.plist
> index 9949e0f..a5587ed 100644
> --- a/ios/Runner/Info.plist
> +++ b/ios/Runner/Info.plist
> @@ -22,6 +22,8 @@
>  	<string>????</string>
>  	<key>CFBundleVersion</key>
>  	<string>$(FLUTTER_BUILD_NUMBER)</string>
> +	<key>ITSAppUsesNonExemptEncryption</key>
> +	<false/>
>  	<key>LSRequiresIPhoneOS</key>
>  	<true/>
>  	<key>NSFaceIDUsageDescription</key>

Acked-by: Thomas Lamprecht <t.lamprecht@proxmox.com>


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [pve-devel] applied: [PATCH pve_flutter_frontend v3] chore: ios: add export compliance key to info.plist
  2025-09-30  8:48 [pve-devel] [PATCH pve_flutter_frontend v3] chore: ios: add export compliance key to info.plist Shan Shaji
  2025-10-01 13:54 ` Thomas Lamprecht
@ 2025-10-02  8:39 ` Dominik Csapak
  1 sibling, 0 replies; 3+ messages in thread
From: Dominik Csapak @ 2025-10-02  8:39 UTC (permalink / raw)
  To: pve-devel, Shan Shaji

On Tue, 30 Sep 2025 10:48:52 +0200, Shan Shaji wrote:
> The app only uses TLS/SSL through iOS platform APIs, which are already
> exported by Apple, and is therefore classified under 5A992/5D992 (Mass
> Market [1]). Since march 29, 2021, mass market software no longer
> requires a self-classification report except for "non-standared"
> algorithms.
> 
> The `crypto` package is used solely for data integrity with SHA-256
> (publicly available, standard algorithm) and not for
> confidentiality [3], so it should fall under 5D992. Also this package
> should also fall under mass market cryptographic library which
> implements a standard algorithm [2] (Table Reference: Third Row).
> 
> [...]

Applied, thanks!

[1/1] chore: ios: add export compliance key to info.plist
      commit: 0051cac29cacfacc9ccb1fa952e942e120012e3b


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-10-02  8:39 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-09-30  8:48 [pve-devel] [PATCH pve_flutter_frontend v3] chore: ios: add export compliance key to info.plist Shan Shaji
2025-10-01 13:54 ` Thomas Lamprecht
2025-10-02  8:39 ` [pve-devel] applied: " Dominik Csapak

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal