From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Shan Shaji <s.shaji@proxmox.com>
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] [PATCH pve_flutter_frontend v2] chore: ios: add export compliance key to info.plist
Date: Fri, 26 Sep 2025 11:21:27 +0200 [thread overview]
Message-ID: <f1ccba2c-8d53-4673-b1d0-f6194176db9f@proxmox.com> (raw)
In-Reply-To: <20250925123243.25940-1-s.shaji@proxmox.com>
I'm not a lawyer, but are you sure we are compliant with this?
the https client will use encryption, so it's not like we don't use
encryption at all. (Especially with the cupertino_http package)
I guess this is exempt, but having some reference for that (aside
some medium/reddit post) would be nice.
At least some kind of rationale in the commit would be good.
(IMHO 'we don't use proprietary encryption' is not a good reason
when also 'standard encryption' falls under the export regulation...)
@Thomas, what do you think?
On 9/25/25 2:32 PM, Shan Shaji wrote:
> Every time when a new build is uploaded to appstoreconnect, the export
> compliance [0] status needs to be manually selected. Since there are no
> proprietary encryptions used in the app in-order to avoid manually
> filling the export compliance add `ITSAppUsesNonExemptEncryption` [1]
> to `Info.plist`.
>
> - [0] https://developer.apple.com/help/app-store-connect/manage-app-information/overview-of-export-compliance
> - [1] https://developer.apple.com/documentation/security/complying-with-encryption-export-regulations
>
> References:
> - https://medium.com/@thibault.jamet/navigating-export-compliance-a-flutter-developers-journey-to-the-app-store-ce7a5328f37d
> - https://developer.apple.com/help/app-store-connect/reference/export-compliance-documentation-for-encryption
> - https://www.reddit.com/r/FlutterDev/comments/1elm705/comment/lgyk31y/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
>
> Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
> ---
> changes since v1:
> - Fixed broken link inside commit message.
>
> 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>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-09-26 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 12:32 Shan Shaji
2025-09-26 9:21 ` Dominik Csapak [this message]
2025-09-26 9:51 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1ccba2c-8d53-4673-b1d0-f6194176db9f@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.shaji@proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox