github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-09 19:54:19 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

encryptionexport licensing iOS? #100

New Issue
Closed
opened 2025-11-07 08:26:24 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-07 08:26:24 -06:00
Owner
Copy Link

Originally created by @petervnv on GitHub (Oct 14, 2017).

Hi,
I noticed in the info.plist file that you marked the app as needing export compliance docs from the BIS:

ITSAppUsesNonExemptEncryption

However, you state on the website that bitwarden uses only CommonCrypto API in iOS https://help.bitwarden.com/article/what-encryption-is-used/

According to recent changes in Apple and US policy, if you're only using iOS crypto than your app qualifies now as exempt. https://stackoverflow.com/questions/2135081/does-my-application-contain-encryption/40391664#40391664

So my question is why the export compliance key in info.plist? Does bitwarden use anything more than CommonCrypto in the iOS app?

Cheers,
Peter

Originally created by @petervnv on GitHub (Oct 14, 2017). Hi, I noticed in the info.plist file that you marked the app as needing export compliance docs from the BIS: <key>ITSAppUsesNonExemptEncryption</key> <true/> However, you state on the website that bitwarden uses only CommonCrypto API in iOS https://help.bitwarden.com/article/what-encryption-is-used/ According to recent changes in Apple and US policy, if you're only using iOS crypto than your app qualifies now as exempt. https://stackoverflow.com/questions/2135081/does-my-application-contain-encryption/40391664#40391664 So my question is why the export compliance key in info.plist? Does bitwarden use anything more than CommonCrypto in the iOS app? Cheers, Peter
GiteaMirror commented 2025-11-07 08:26:25 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Oct 14, 2017):

We weren't aware of the policy change. We only use CommonCrypto so I suppose we can remove this. When we first launched the app this wasn't the case. We'll look into it more.

@kspearrin commented on GitHub (Oct 14, 2017): We weren't aware of the policy change. We only use CommonCrypto so I suppose we can remove this. When we first launched the app this wasn't the case. We'll look into it more.
GiteaMirror commented 2025-11-07 08:26:25 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Oct 14, 2017):

I found the following docs when attempting to contact apple support about this:

screen shot 2017-10-14 at 11 35 27 am

Seems we still need it?

@kspearrin commented on GitHub (Oct 14, 2017): I found the following docs when attempting to contact apple support about this: ![screen shot 2017-10-14 at 11 35 27 am](https://user-images.githubusercontent.com/1190944/31576954-e6d9d9f2-b0d3-11e7-8b37-4ec104177059.png) Seems we still need it?
GiteaMirror commented 2025-11-07 08:26:25 -06:00
Author
Owner
Copy Link

@petervnv commented on GitHub (Oct 14, 2017):

Hmm, yeah that's pretty confusing and seems to contradict the info on stackoverflow. Welcome to bureaucracy hell.
I guess the question is what is BIS approval? They no longer allow the "encryption registration" option on SNAP-R, so it seems you just need to send them an annual report but no longer need to register:

https://stackoverflow.com/questions/2135081/does-my-application-contain-encryption/40391664#40391664
"Specifically, they note:

Encryption Registrations no longer required – some of the information from the registration now goes into the Supp. No. 8 to Part 742 report.

This means you may need to send an annual report to BIS, but you don't need to register and you can note when submitting your app that it is exempt."

@petervnv commented on GitHub (Oct 14, 2017): Hmm, yeah that's pretty confusing and seems to contradict the info on stackoverflow. Welcome to bureaucracy hell. I guess the question is what is BIS approval? They no longer allow the "encryption registration" option on SNAP-R, so it seems you just need to send them an annual report but no longer need to register: https://stackoverflow.com/questions/2135081/does-my-application-contain-encryption/40391664#40391664 "Specifically, they note: Encryption Registrations no longer required – some of the information from the registration now goes into the Supp. No. 8 to Part 742 report. This means you may need to send an annual report to BIS, but you don't need to register and you can note when submitting your app that it is exempt."
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#100
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?