Mooltipass Mini BLE (delivered September 23rd 2022)
mooltipass user guide: https://raw.githubusercontent.com/mooltipass/minible/master/MooltipassMiniBLEUserManual.pdf
moolticute repo: https://github.com/mooltipass/moolticute
moolticute install guide: https://github.com/mooltipass/moolticute/blob/master/README.md
moolticute build steps: https://github.com/mooltipass/moolticute/blob/master/README.md#how-to-build
I created a minified distributable. Just pull that repo instead of doing the slow runbook below. This saves about an hour of download/install and 5GB of unnecessary QT disk usage: https://bitbucket.org/di0/moolticute
get latest release source code for moolticute: https://github.com/mooltipass/moolticute/releases
create QT user account
download QT open-source version (~5GB) https://www.qt.io/download-qt-installer
run qt-installer
- on successful install:
- run QT Creator
QT Creator >> open project Moolticute.pro
from the moolticute release source code folder
- when prompted, choose “Desktop QT MinGW 64-bit” as the compiler
- (do not choose the VSCC compiler – it won’t compile this project)
- click [Configure Project]
in the lower left corner
- click the monitor >> Debug >> gui (this should build and run the project)
At this point, if the gui shows, the app should “install” itself to the system
- installing itself should add the required service and app to windows startup
- (this requires restart)
- after restart, you should notice that the chrome browser extension now shows:
- “Open Mooltipass App” which is clickable, instead of:
- “Open Mooltipass App (No installed app)” which is disabled (greyed out)
- “Open Mooltipass App” which is clickable, instead of:
While running the app through QT creator is great, we need to be able to run the moolticute.exe
outside of the IDE. If you experience errors on startup, look below.
A successful build of the project through QT Creator should target one folder above the project folder containing Moolticute.pro
:
- for instance, if the project folder is:
~\Downloads\moolticute-0.55.13-testing\
- then the build output (exe’s) will be in:
~\Downloads\build-Moolticute-Desktop_Qt_6_3_2_MinGW_64_bit-Debug\debug\
- double click
moolticute.exe
from build output folder - results in several error messages about Qt*.dll cannot be found
- system cannot find the QT dependencies on system startup or if running the .exes from the build output folder.
- manually add QT binaries to system PATH environment variable as described here (make sure to choose the “mingw” binaries, since that’s the compiler we used)
- in my case:
C:\qt\6.3.2\mingw_64\bin
- open command prompt
qmake –version
- if that shows output, then double clicking the
moolticute.exe
from file explorer should work now - if the .exe runs, then system startup should result in a system tray icon for moolticute
- power off device
- kill moolticute
- power on device
- use webauthn provider like DuoMobile for "Security Key" authentication
- observe that "Time Not Set" shows on the device
- device must be connected to moolticute after powering on to set time for TOTP
- run moolticute and connect device
- try to authenticate with DuoMobile again
- this time it should work fine