qca-2.1.1 (qt4+qt5)

[Fernando de Oliveira]

​http://download.kde.org/stable/qca/2.1.1/src/qca-2.1.1.tar.xz

​http://download.kde.org/stable/qca/2.1.1/src/qca-2.1.1.tar.xz.md5

657cc701316600199199a6b6cb2c73c9

​https://mail.kde.org/pipermail/kde-distro-packagers/2015-October/000104.html

QCA 2.1.1 (qt4+qt5)
Harald Sitter sitter at kde.org
Mon Oct 5 07:43:27 UTC 2015

New maintenance release of QCA, the cross-platform cryptography API for
Qt.

- Whole pile of cmake/build improvements to support various platforms
  better
- Merged the qt5 library separation previously released as tarball
  qca-qt5

# Qt5
This release replaces the previously separate qca-qt5 tarball.
By default QCA 2.1.1+ will build a library called libqca-qt5 iff Qt5
is found. If it is not found or CMake was called with
-DQT4_BUILD=true, Qt4 will be required and a library called libqca is
built. The two build modes install *completely* separate files to
enable installing the Qt4 and Qt5 build on the same system alongside
one another without risking that applications using QCA load an
incompatible Qt version.

To use the Qt5 version rather than the Qt4 version of QCA simply
append '-qt5' to all uses of Qca in CMake.

[bdubbs@…]

In the qca unit test for the pgp (gnupg) plugin, it asks for a pass phrase via manual input of the "Qca Test Key". Does anyone know this pass phrase? I couldn't find it in the tarball or google.

[Fernando de Oliveira]

Bruce,

No problem here, if we are talking about the same thing.

Tested with Qt4 and 5, both with similar tests results, only time differences, but of fractions of seconds. Total test time essentially define by FileWatch test.

Apparently no problem installing both in /usr all files and directores are named or located differently.

With tests included, Approximate build time = 0.7 SBU (1 SBU = 150s), built with -j8, tests with -j1.

Qt4 as in the book, no need for source setqt4.

Qt5, again without using source setqt5, but using -DCMAKE_INSTALL_PREFIX=$QT5DIR and removing -DQT4_BUILD=ON.

Tests using make test, run from the script, inside the build directory, never asked Qca Test Key:

Running tests...
Test project /tmp/qca-2.1.1/build
      Start  1: Base64
 1/24 Test  #1: Base64 ...........................   Passed    0.01 sec
      Start  2: BigInteger
 2/24 Test  #2: BigInteger .......................   Passed    0.11 sec
      Start  3: Certificate
 3/24 Test  #3: Certificate ......................   Passed    0.01 sec
      Start  4: SymmetricCipher
 4/24 Test  #4: SymmetricCipher ..................   Passed    0.06 sec
      Start  5: ClientSidePlugin
 5/24 Test  #5: ClientSidePlugin .................   Passed    0.01 sec
      Start  6: CryptographicMessageSyntax
 6/24 Test  #6: CryptographicMessageSyntax .......   Passed    0.01 sec
      Start  7: DigitalSignatureAlgorithm
 7/24 Test  #7: DigitalSignatureAlgorithm ........   Passed    0.01 sec
      Start  8: FileWatch
 8/24 Test  #8: FileWatch ........................   Passed   56.05 sec
      Start  9: Hashing
 9/24 Test  #9: Hashing ..........................   Passed    0.02 sec
      Start 10: HexadecimalConversion
10/24 Test #10: HexadecimalConversion ............   Passed    0.01 sec
      Start 11: KeyDerivationFunction
11/24 Test #11: KeyDerivationFunction ............   Passed    0.01 sec
      Start 12: KeyBundle
12/24 Test #12: KeyBundle ........................   Passed    0.01 sec
      Start 13: KeyGeneration
13/24 Test #13: KeyGeneration ....................   Passed    0.01 sec
      Start 14: KeyLength
14/24 Test #14: KeyLength ........................   Passed    0.01 sec
      Start 15: KeyStore
15/24 Test #15: KeyStore .........................   Passed    0.01 sec
      Start 16: MessageAuthenticationCode
16/24 Test #16: MessageAuthenticationCode ........   Passed    0.01 sec
      Start 17: MetaTypeUnittest
17/24 Test #17: MetaTypeUnittest .................   Passed    0.01 sec
      Start 18: PGP
18/24 Test #18: PGP ..............................   Passed    0.01 sec
      Start 19: PublicKeyInfrastructure
19/24 Test #19: PublicKeyInfrastructure ..........   Passed    0.01 sec
      Start 20: RSA
20/24 Test #20: RSA ..............................   Passed    0.01 sec
      Start 21: SecureArray
21/24 Test #21: SecureArray ......................   Passed    0.01 sec
      Start 22: StaticFunctions
22/24 Test #22: StaticFunctions ..................   Passed    0.01 sec
      Start 23: SymmetricKey
23/24 Test #23: SymmetricKey .....................   Passed    0.01 sec
      Start 24: TransportLayerSecurity
24/24 Test #24: TransportLayerSecurity ...........   Passed    0.01 sec

100% tests passed, 0 tests failed out of 24

Total Test time (real) =  56.41 sec

real	0m56.674s
user	0m0.424s
sys	0m0.126s

3,4M	../../DEST-qca-2.1.1
29M	../../qca-2.1.1
33M	total

[Fernando de Oliveira]

Forgot: in the Qt4 build, same build directory of the scripted execution, rerun tests by hand and no difference. Sometimes, my scripted builds waits for some input with a not displayed message.

[bdubbs@…]

Do you have gnupg installed? If I go to build/unittest/pgpunittest/ and run make, it just does the PGP test. When I run it, I get a graphical pop-up asking for a "Qca Test Key" pass phrase to be manually input. I cannot get that to pass because I don't know what input it wants.

[Fernando de Oliveira]

Replying to bdubbs@…:

Do you have gnupg installed?

Yes:

$ gpg --version  | head -2
gpg (GnuPG) 2.1.9
libgcrypt 1.6.4

If I go to build/unittest/pgpunittest/ and run make, it just does the PGP test. When I run it, I get a graphical pop-up asking for a "Qca Test Key" pass phrase to be manually input. I cannot get that to pass because I don't know what input it wants.

You mean make test, right?

No graphical dialogue appears. No pass phrase asked here:

$ make test
Running tests...
Test project /tmp/qca-2.1.1/build/unittest/pgpunittest
    Start 1: PGP
1/1 Test #1: PGP ..............................   Passed    0.01 sec

100% tests passed, 0 tests failed out of 1

Total Test time (real) =   0.01 sec

[bdubbs@…]

Yes, I did mean 'make test'.

No this is weird. I just went to the qt5 version of qca and get the same test results as you did... and the qt4 version passes too. I have no idea what changed.

I'll go ahead and update.

[bdubbs@…]

Fixed at revision 16697.