mirror of
https://github.com/keepassxreboot/keepassxc.git
synced 2024-12-25 15:29:44 -05:00
c663b5d5fc
* Ran clang-tidy with "readability-braces-around-statements" to find missing braces around statements.
101 lines
2.7 KiB
C++
101 lines
2.7 KiB
C++
/*
|
|
* Copyright (C) 2014 Kyle Manna <kyle@kylemanna.com>
|
|
* Copyright (C) 2017 KeePassXC Team <team@keepassxc.org>
|
|
*
|
|
*
|
|
* 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 "TestGlobal.h"
|
|
#include "crypto/Crypto.h"
|
|
|
|
#include <QtConcurrentRun>
|
|
|
|
QTEST_GUILESS_MAIN(TestYubiKeyChalResp)
|
|
|
|
void TestYubiKeyChalResp::initTestCase()
|
|
{
|
|
// crypto subsystem needs to be initialized for YubiKey testing
|
|
QVERIFY(Crypto::init());
|
|
}
|
|
|
|
void TestYubiKeyChalResp::init()
|
|
{
|
|
if (!YubiKey::instance()->init()) {
|
|
QSKIP("Unable to connect to YubiKey");
|
|
}
|
|
}
|
|
|
|
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 pass.
|
|
*
|
|
* 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.reset(new YkChallengeResponseKey(slot, blocking));
|
|
}
|
|
}
|
|
|
|
void TestYubiKeyChalResp::deinit()
|
|
{
|
|
QVERIFY(YubiKey::instance()->deinit());
|
|
}
|