QCA - AES 128

[XerXi]

Hi all,

I would like to cypher some data with AES-128. I know that exists "QCA library":http://delta.affinix.com/qca/ , but I don't know how to begin.
I've downloaded "qca-2.0.3.tar.bz2" and "qca-ossl-2.0.0-beta3.tar.bz2" (because in its capability AES is listed), but I don't know if it is all I need.

Could anyone guide/help me?

Thank you very much!

[goetz]

You must unpack qca-2.0.3.tar.bz2 and compile the sources. It provides you the base framework for QCA. Do the same with qca-ossl-2.0.0-beta3.tar.bz2. For the latter you must have the OpenSSL development packages installed. For the rest, follow the INSTALL and README documents inside the packages.

[XerXi]

Thank you for reply.

I unpack qca-2.0.3.tar.bz2 and follow the instruction in INSTALL file but I get this error:

Console
@

D:\qt\qca-2.0.3>configure
Configuring Qt Cryptographic Architecture (QCA) ...
Verifying Qt 4 build environment ... fail

Reason: There was an error compiling 'conf'. See conf.log for details.

Be sure you have a proper Qt 4.0 build environment set up. This means not
just Qt, but also a C++ compiler, a make tool, and any other packages
necessary for compiling C++ programs.

If you are certain everything is installed, then it could be that Qt 4 is not
being recognized or that a different version of Qt is being detected by
mistake (for example, this could happen if %QTDIR% is pointing to a Qt 3
installation). At least one of the following conditions must be satisfied:

1. --qtdir is set to the location of Qt
2. %QTDIR% is set to the location of Qt

This program will use the first one it finds to be true, checked in the above
order.

Config File

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation. All rights reserved.

"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\nmake.exe" -f Makefile.Debug

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation. All rights reserved.

D:\qt\qt-everywhere-opensource-src-4.7.1\bin\moc.exe -DUNDER_CE -DWINCE -D_WINDOWS -D_UNICODE -DUNICODE -D_WIN32 -DQT_NO_PRINTER -DQT_NO_PRINTDIALOG -DARMV4I -D_ARMV4I_ -Darmv4i -D_ARM_ -DARM -D_M_ARM -DARM -D__arm__ -DQ_OS_WINCE_WM -DQT_NO_PRINTER -DQT_NO_PRINTDIALOG -D_WIN32_WCE=0x502 -DQT_WINCE_GESTURES -DHAVE_MODULES -DQT_DLL -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_IWMMXT -DQT_THREAD_SUPPORT -DQT_NO_DYNAMIC_CAST -I"....\qt-everywhere-opensource-src-4.7.1\include\QtCore" -I"....\qt-everywhere-opensource-src-4.7.1\include" -I"....\qt-everywhere-opensource-src-4.7.1\include\ActiveQt" -I"debug" -I"....\qt-everywhere-opensource-src-4.7.1\mkspecs\default" -D_MSC_VER=1500 conf4.cpp -o debug\conf4.moc
cl -c -nologo -Zm200 -Zc:wchar_t- -DDEBUG -D_DEBUG -Zi -MDd -EHs-c- -W3 -w34100 -w34189 -DUNDER_CE -DWINCE -D_WINDOWS -D_UNICODE -DUNICODE -D_WIN32 -DQT_NO_PRINTER -DQT_NO_PRINTDIALOG -DARMV4I -D_ARMV4I_ -Darmv4i -D_ARM_ -DARM -D_M_ARM -DARM -D__arm__ -DQ_OS_WINCE_WM -DQT_NO_PRINTER -DQT_NO_PRINTDIALOG -D_WIN32_WCE=0x502 -DQT_WINCE_GESTURES -DHAVE_MODULES -DQT_DLL -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_IWMMXT -DQT_THREAD_SUPPORT -DQT_NO_DYNAMIC_CAST -I"....\qt-everywhere-opensource-src-4.7.1\include\QtCore" -I"....\qt-everywhere-opensource-src-4.7.1\include" -I"....\qt-everywhere-opensource-src-4.7.1\include\ActiveQt" -I"debug" -I"....\qt-everywhere-opensource-src-4.7.1\mkspecs\default" -Fodebug\ &0x40;C:\DOCUME~1\a172886\LOCALS~1\Temp\nmB28.tmp
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\cl.EXE"' : return code '0xc0000135'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files\Microsoft Visual Studio 9.0\VC\bin\nmake.exe"' : return code '0x2'
Stop.
@

Any Idea?

Thanks!!!!

[EDIT: code markup for log outpu, Volker]

[goetz]

Seem that this part of the error message might get you further:

bq. If you are certain everything is installed, then it could be that Qt 4 is not
being recognized or that a different version of Qt is being detected by
mistake (for example, this could happen if %QTDIR% is pointing to a Qt 3
installation).  At least one of the following conditions must be satisfied: 
 1) --qtdir is set to the location of Qt
 2) %QTDIR% is set to the location of Qt

[XerXi]

The Qt version is Qt 4.7.1 for WinCE and I've seted an environment "QTDIR" variable with its location.....
Is Qt for WinCE compatible, it isn't?

Thank you

[goetz]

I have no idea if it's supported for WinCE, maybe the maintainer(s) of QCA can help you with that.

[XerXi]

I don't find any contact of support in QCA:http://delta.affinix.com page...

So, does anyone know if QCA:http://delta.affinix.com is compatible with Qt 4.7.1 for WinCE??

I've surfed to this page "http://delta.affinix.com/platform/":http://delta.affinix.com/platform/ and I've found another problem... Seems that QCA is available until Visual Studio 2005 and I'm developing on 2008 version.

Has anyone worked with these conditions?

Desktop Machine
Windows XP SP3
Visual Studio 2008 Professional
Qt 4.7.1 for WinCE
Add-in plugin
Intel® Core™2 Duo CPU E6550 @2.33GHz, 3,23 GB of RAM

Device Machine
Windows Mobile 6.5 Professional
Casio IT-800 —> Marvell® PXA320 624MHz

Any help?

Thanks a lot

[XerXi]

Hello again,

I've downloaded "qca-2.0.1-mingw" and executed "installwin.bat". It seems works because in "$QTDIR\mkspecs\features" there is a "crypto.prf". Inside of this file:

@QCA_INCDIR = "D:\qt\qca-2.0.1-mingw\include\QtCrypto"
QCA_LIBDIR = "D:\qt\qca-2.0.1-mingw\lib"

prepend this file with QCA_INCDIR/QCA_LIBDIR definitions

NOTE: any changes made to this file need to be tracked in qcm/qca.qcm

CONFIG *= qt

if we are including crypto.prf from the qca tree (and not utilizing it as

an installed qmake CONFIG feature), then point to the tree. this allows our

qca tree apps to build before qca itself is installed.

exists($$PWD/qca.pro) {
QCA_INCDIR = $$PWD/include
QCA_LIBDIR = $$PWD/lib
}

LINKAGE =

on mac, if qca was built as a framework, link against it

mac: {
framework_dir = $$QCA_LIBDIR
exists($$framework_dir/qca.framework) {
#QMAKE_FRAMEWORKPATH *= $$framework_dir
LIBS += -F$$framework_dir
INCLUDEPATH += $$framework_dir/qca.framework/Headers
LINKAGE = -framework qca
}
}

else, link normally

isEmpty(LINKAGE) {
INCLUDEPATH += $$QCA_INCDIR/QtCrypto
LIBS += -L$$QCA_LIBDIR
LINKAGE = -lqca
CONFIG(debug, debug|release) {
windows:LINKAGE = -lqcad
mac:LINKAGE = -lqca_debug
}
}

LIBS += $$LINKAGE
@

The variables on top of the file are correct. Now, I don't know what is the next step. If I add to my code: @#include <QtCrypto>@ When I compile this error is printed: @fatal error C1083: Cannot open include file: 'QtCrypto': No such file or directory@

Any Idea?

Thanks!!!

[goetz]

Try adding this to your .pro file:

@
CONFIG += crypto
@

This adds the QCA capabilities to your project.

[XerXi]

It doesn't work.

I'm new in Qt so I don't know if I must do something more. I only added the line what you said.

[goetz]

I don't have any further idea. QCA is not in use in my projects anymore (we once used it for the Qt3 version of our project).

[trungnh102]

Hello XerXi
Did you solved your problem ?
I've try to install QCA for Nokia QT SDK many times.
It doesn't work.
It is too difficult to install a snap-in

[XerXi]

Hello trungnh102,

No. I used "wincrypt.h" library for c++.

Sorry

[rileo8]

Hi,

i know that is not qt related..but can you me an example of how you use wincrypt.h for aes crypt/decrypt?