Compliance with export requirements and AES256 in iPhone

My application uses the AES256 algorithm to encrypt data. When I am ready to submit my application to the App Store, its request

Export laws require that products containing encryption be properly authorized for export.

Does your product have encryption or does it use encryption or access to it from another source, such as iOS or Mac OS X?

When I sent applications with Sha1 in the previous time, I selected a NoMy application that contains, uses or encrypts access for any purpose other than authentication or anti-virus protection. What should I do if my application contains the AES256 algorithm.

+5
source share
2 answers

It depends on how you use this encryption in your application, in my case I used aes to create a secure HTTP call, and I did not need to authorize it for export, so if you didn’t do this the last time, t authorize, I think you do not need to know this (if you give encryption the same use in both cases)

+1
source

It is true that your use of encryption is important, but you can still start from the Bureau of Industry and Security website or call BIS, contact support 202-482-0707 and get advice.

, AES HTTP- , .

+1

All Articles