5 ms·
I think I remember reading that if you're using Apple's APIs and frameworks (like their builtins for HTTPS) then you don't need to go through this rigmarole.
by madeofpalk 11y ago
I think I remember reading that if you're using Apple's APIs and frameworks (like their builtins for HTTPS) then you don't need to go through this rigmarole.
- rosser 11y agoFrom the screen shot of Apple's app submission: "Select yes even if your app is only utilizing the encryption available in iOS or OSX."
- madeofpalk 11y agoI've always interpreted "(ii) your app uses, accesses, implements or incorporates encryption for authentication only" as our uses cases for using HTTPS and thus said that I am exempt.
- deleted 11y ago[deleted]
- vbezhenar 11y agoUnless you are using HTTPS with NULL encryption algorithm, your bytes are encrypted and decrypted, so it's not "authentication only". I think that you can use NULL encryption algorithm and in this case only authentication will be performed. But I'm not sure that standard library will allow to use this algorithm.
- weddpros 11y agoIn that case, simply saving a file would also count as encryption now, since iOS devices are encrypted...