> I redid the code to use simple static bytes:
>
>       byte iv[16];
>
>       byte bKey[32];
>
>       memcpy(iv, binIv.constData(), sizeof(iv));
>
>       memcpy(bKey, binKey.constData(), sizeof(bKey));
>
>
>       CFB_Mode<AES>::Encryption e(bKey, 32, iv, 1);
>
>
>       FileSource src((const char *)inFilename.toUtf8().constData(), true,
>
>               new StreamTransformationFilter(e, //STF
>
>                       new Base64Encoder(
>
>                               new FileSink((const char 
> *)outFilename.toUtf8().constData())
>
>                               , false
>
>                       )
>
>               ) //STF
>
>       );
>
>
> Same issue. However, if I comment out the lines with //STF, so that it just 
> removes the STF and just does a base64 encode, the code works. Which makes me 
> think that it's specific to the STF. It is doing something because the phone 
> gets hot. At which point I wonder if the issue is with architecture or 
> packaging. I have created a fat library:
>
>
> $ xcrun -sdk iphoneos lipo -info libcryptopp-ios.a
> Architectures in the fat file: libcryptopp-ios.a are: armv7 x86_64 arm64
>
>
Hmmm... I cannot duplicate it. I just tried again on iOS 6.0 and 8.1.

For iOS, I test using two jail broken devices: (1) iPad2 running 8.1 and 
(2) iPad3 running iOS 6.0. I cross compile it according to 
https://www.cryptopp.com/wiki/IOS_%28Command_Line%29 . I SCP cryptest.exe, 
TestVectors/ and TestData/ to the device. I then SSH into the device, and 
execute the tests.

Jeff

-- 
-- 
You received this message because you are subscribed to the "Crypto++ Users" 
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at 
http://www.cryptopp.com.
--- 
You received this message because you are subscribed to the Google Groups 
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to