My iOS app wants to encrypt the transfer of data that is sensitive to the user name and password on the server.
Backstage is PHP, in the online search some programs, seemingly AES is also more reliable. But I iOS encryption to see the results and PHP encrypted results are different ...
Now there is no more mature this open source scheme, can let obj-c and PHP encrypted transmission of
Reply content:
My iOS app wants to encrypt the transfer of data that is sensitive to the user name and password on the server.
Backstage is PHP, in the online search some programs, seemingly AES is also more reliable. But I iOS encryption to see the results and PHP encrypted results are different ...
Now there is no more mature this open source scheme, can let obj-c and PHP encrypted transmission of
What we are doing now is this:
Client
Add the time parameter to each requested URL. The parameters in the URL are sorted.
This URL is then MD5. Stitch this MD5 as the last parameter (sign) to the URL at the end.
Service side
After the request is received, MD5 the URL that removed the last parameter. The resulting MD5 and MD5 in the parameters are matched. If the match is successfully returned, if it is unsuccessful, 500
Encryption
With the AES
Simple login encryption can consider the previous packaged OAuth, while OAuth's Achilles heel is token fear of theft.
To completely guarantee the security of the transmission is complex, a AES can not be done. Symmetric encryption (AES) is the least secure, then asymmetric, Diffie-hellman key exchange for anti-man attacks, digital signatures and digital certificates, and so on. Want to be absolutely safe read the Apple cryptoservices, Portal: https://developer.apple.com/library/i ... The second chapter describes the principle of encryption
Spit Groove: Anyway, netease mobile phone port Interface on the simple password forget MD5, to the service side than the next ...
HTTPS
What do you eat?