mirror of
https://github.com/keepassxreboot/keepassxc.git
synced 2024-10-01 01:26:01 -04:00
5a3ed27fed
Initialize the Crypto class before running the tests as YubiKey detection code depends on it for random data.
113 lines
2.9 KiB
C++
113 lines
2.9 KiB
C++
/*
|
|
* Copyright (C) 2014 Kyle Manna <kyle@kylemanna.com>
|
|
*
|
|
*
|
|
* This program is free software: you can redistribute it and/or modify
|
|
* it under the terms of the GNU General Public License as published by
|
|
* the Free Software Foundation, either version 2 or (at your option)
|
|
* version 3 of the License.
|
|
*
|
|
* This program is distributed in the hope that it will be useful,
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
* GNU General Public License for more details.
|
|
*
|
|
* You should have received a copy of the GNU General Public License
|
|
* along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
*/
|
|
|
|
#include "TestYkChallengeResponseKey.h"
|
|
|
|
#include <QTest>
|
|
#include <QtConcurrentRun>
|
|
|
|
#include "crypto/Crypto.h"
|
|
#include "keys/YkChallengeResponseKey.h"
|
|
|
|
QTEST_GUILESS_MAIN(TestYubiKeyChalResp)
|
|
|
|
void TestYubiKeyChalResp::initTestCase()
|
|
{
|
|
m_detected = 0;
|
|
m_key = NULL;
|
|
}
|
|
|
|
void TestYubiKeyChalResp::cleanupTestCase()
|
|
{
|
|
if (m_key)
|
|
delete m_key;
|
|
}
|
|
|
|
void TestYubiKeyChalResp::init()
|
|
{
|
|
bool result = YubiKey::instance()->init();
|
|
|
|
if (!result) {
|
|
QSKIP("Unable to connect to YubiKey", SkipAll);
|
|
}
|
|
|
|
/* Crypto subsystem needs to be initalized for YubiKey testing */
|
|
QVERIFY(Crypto::init());
|
|
}
|
|
|
|
void TestYubiKeyChalResp::detectDevices()
|
|
{
|
|
connect(YubiKey::instance(), SIGNAL(detected(int,bool)),
|
|
SLOT(ykDetected(int,bool)),
|
|
Qt::QueuedConnection);
|
|
QtConcurrent::run(YubiKey::instance(), &YubiKey::detect);
|
|
|
|
/* Need to wait for the hardware (that's hopefully plugged in)... */
|
|
QTest::qWait(2000);
|
|
QVERIFY2(m_detected > 0, "Is a YubiKey attached?");
|
|
}
|
|
|
|
void TestYubiKeyChalResp::getSerial()
|
|
{
|
|
unsigned int serial;
|
|
QVERIFY(YubiKey::instance()->getSerial(serial));
|
|
}
|
|
|
|
void TestYubiKeyChalResp::keyGetName()
|
|
{
|
|
QVERIFY(m_key);
|
|
QVERIFY(m_key->getName().length() > 0);
|
|
}
|
|
|
|
void TestYubiKeyChalResp::keyIssueChallenge()
|
|
{
|
|
QVERIFY(m_key);
|
|
if (m_key->isBlocking()) {
|
|
/* Testing active mode in unit tests is unreasonable */
|
|
QSKIP("YubiKey not in passive mode", SkipSingle);
|
|
}
|
|
|
|
QByteArray ba("UnitTest");
|
|
QVERIFY(m_key->challenge(ba));
|
|
|
|
/* TODO Determine if it's reasonable to provide a fixed secret key for
|
|
* verification testing. Obviously simple technically, but annoying
|
|
* if devs need to re-program their yubikeys or have a spare test key
|
|
* for unit tests to past.
|
|
*
|
|
* Might be worth it for integrity verification though.
|
|
*/
|
|
}
|
|
|
|
void TestYubiKeyChalResp::ykDetected(int slot, bool blocking)
|
|
{
|
|
Q_UNUSED(blocking);
|
|
|
|
if (slot > 0)
|
|
m_detected++;
|
|
|
|
/* Key used for later testing */
|
|
if (!m_key)
|
|
m_key = new YkChallengeResponseKey(slot, blocking);
|
|
}
|
|
|
|
void TestYubiKeyChalResp::deinit()
|
|
{
|
|
QVERIFY(YubiKey::instance()->deinit());
|
|
}
|