Does anyone know of an iOS library that allows us to encrypt using AES128 CFB mode with not padding. Looks like commoncrypto does not support this .
Thanks
I'd suggest pushing OpenSSL into your project, if possible. A quick search for "ios openssl" returns a first hit for Easy inclusion of OpenSSL into iOS projects. See also AES interoperability between .Net and iPhone?
Beware that without padding, you'll need to feed the cipher blocks of the correct size.
Related
I am trying to find a good library to do the following:
Generate RSA public and private key pairs
Encrypt / decrypt using keys
Sign using private key / verify with public key
Generate SHA256 hashes
I tried many libraries, but I can't seem to find something simple and straightforward with all these functions. In python pycrypto covers all this, it's really strange that there doesn't seem to be something like this available for Swift.
If you are using iOS 13 or above as the base SDK for your app then you should look at CryptoKit from Apple as it should cover what you are looking for.
https://developer.apple.com/documentation/cryptokit
If you need to support devices running versions of iOS older than iOS13 then you should look at CommonCrypto (also native to Apple) but if you can afford to only support iOS13 and above then CryptoKit is far better and easier to implement.
I'm new to encrypting in iOS and i'm stuck with AES128 encryption. Is there some pre-built library (perhaps OpenSSL) which i can use easily?
If so, how do I implement it and use it? Are there tutorials?
I've found several "easy" tutorials how to build OpenSSL and import it to Xcode, but none of them worked for me. Also, it needs to be compatible with iOS4, so solution via CommonCrypto doesn't seem to be a solution (since several essential methods are only iOS 5+ compatible).
Thanks for any kind of help, i'm pulling my hair out over this :)
This is written in Obj-C and allows for AES128 encryption of NSString and NSData.
I take it back. It uses CommonCrypt.
If anyone is still interested in this question i found a solution on http://dotmac.rationalmind.net/2009/02/aes-interoperability-between-net-and-iphone/ . On this page you can download very simple obj-c classes which are compatible with iOS4 and doesn't need any 3rd party libraries.
I would like to hash a string using ripemd128 on iOS / OS X, but there does not seem to be core support for this, or any simple open source framework implementing it. Anyone has a solution?
If RIPEMD is not natively supported by the iOS SDK you can use an external library:
crypto++ For the integration with iOS you can see this page.
sphlib is a library implementing standard digest algorithms. It is written in ANSI C and should be compatible with iOS.
Is there an iOS equivalent to SecTransformRef from the Mac SecTransform.h header file? I am getting a Semantic issue where there is an unknown type name 'SecTransformRef'. It appears that the SecTransform.h file does not exist on the iOS side and I am trying to get the same functionality from the Mac side to the iOS version. The main objective at hand is client encryption and communication with Base64 encoding.
Security transforms are only available in OS X.
If you want to make symetric encryption please take a look on doc page:
https://developer.apple.com/library/mac/documentation/security/Conceptual/cryptoservices/GeneralPurposeCrypto/GeneralPurposeCrypto.html#//apple_ref/doc/uid/TP40011172-CH9-SW14
and also
https://developer.apple.com/library/mac/documentation/security/Conceptual/CertKeyTrustProgGuide/iPhone_Tasks/iPhone_Tasks.html#//apple_ref/doc/uid/TP40001358-CH208-SW9
Will apple choose to not allow an app to go to the app store if we use JSONKit to parse JSON's from our php document? I would like to use JSONSerializable but that is for ios5 and I am not going to alienate ios4 members on 3gs by doing that.
You can use JSONKit in an iPhone app. Apple will not reject it based on that.
It's using private APIs they get upset about. :)
No. You can import your own class or library to parse JSON that you want. So long as you aren't using anything within Apple API's that are undocumented, you will be more than fine. Those are all well established parsers. No worries.
Nope, assumably they are unable to tell what source files you use in your application. JSONKit is licensed under the BSD License which allows redistribution;
Redistribution and use in source and binary forms are permitted
provided that the above copyright notice...