Mooltipass hardware wallet with vault

thimbles_taxidermist · July 31, 2025, 2:52pm

I am trying to use the mooltipass wallet with a Vault appVM.
I have compiled the software: GitHub - mooltipass/moolticute: Mooltipass crossplatform daemon/tools
(currently the appvm based on fedora-41-xfce).
The device is working as it is supposed to when I am attaching it to various qubes in order to write passwords but the main issue is:

when I am running the moolticute software on the Vault AppVM to add new passwords and do configurations although I attach it with sys-usb the program doesn’t recognize it.
Any way on how to troubleshoot ?

thimbles_taxidermist · July 31, 2025, 2:58pm

The software needs some udev rules that can be found here:

github.com/mooltipass/mooltipass-udev

udev/69-mooltipass.rules

master

# udev rules for allowing console user(s) and libusb access to Mooltipass Mini devices
ACTION!="add|change", GOTO="mooltipass_end"

# console user
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="09a0", MODE="0660", SYMLINK+="mooltipass_keyboard", TAG+="uaccess", TAG+="udev-acl"
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="4321", MODE="0660", SYMLINK+="mooltipass_keyboard", TAG+="uaccess", TAG+="udev-acl"
# libusb
SUBSYSTEM=="usb", ATTRS{idVendor}=="16d0", ATTRS{idProduct}=="09a0", MODE="0660", SYMLINK+="mooltipass_device", TAG+="uaccess"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1209", ATTRS{idProduct}=="4321", MODE="0660", SYMLINK+="mooltipass_device", TAG+="uaccess"

# required for newer versions of bluez
SUBSYSTEM=="hidraw", KERNELS=="*1209:4321*", MODE="0660", SYMLINK+="mooltipass_keyboard", TAG+="uaccess", TAG+="udev-acl"

LABEL="mooltipass_end"

I tried to save them on the /etc/udev/rules.d/ but as it is an AppVM it didn’t save it on restart.
Where should I save them so they survive the restarts? (not sure if that is the actual issue though)

parulin · July 31, 2025, 3:04pm

Do it in the template or use bind dirs:

~~Or try to use /usr/local/etc instead of /etc ?~~

thimbles_taxidermist · August 1, 2025, 6:51am

Great! that seemed to be the issue.
Thanks a lot

thimbles_taxidermist · February 1, 2026, 2:32pm

for anybody else and future me:

after building moolticute for (it was a bit of a pain finding all the deps so I got the kitchen sink on debian for QT5)

you must have in a qube the binaries: moolticute and moolticuted.

Consider when downloading the repo do the following:

git clone https://github.com/mooltipass/moolticute.git --recurse-submodules
curl https://raw.githubusercontent.com/mooltipass/mooltipass-udev/master/udev/69-mooltipass.rules | tee ./69-mooltipass.rules

hopefully build it if you have all the dependencies:

sudo dnf install gcc-c++ qt5 qt5-qtwebsockets qt5-qtwebsockets-devel qt5-qttools-devel systemd-devel
mkdir build
cd build
qmake-qt5 ../Moolticute.pro
make

It didn’t work for me so I installed also the qtcreator (which is the gui) and several other packages .

Then follow up in vault for example:

sudo mkdir -p /rw/config/qubes-bind-dirs.d/
sudo touch /rw/config/qubes-bind-dirs.d/50_user.conf
sudo echo "binds+=( '/usr/lib/systemd/system/moolticuted.service' )
binds+=( '/usr/bin/moolticuted' )
binds+=( '/usr/bin/moolticute' )
binds+=( '/etc/udev/rules.d/69-mooltipass.rules' )" > /rw/config/qubes-bind-dirs.d/50_user.conf # I hope it works
sudo mkdir -pv /rw/bind-dirs/{usr/bin,usr/lib/systemd/system/,etc/udev/rules.d}
sudo cp QubesIncoming/SomeVM/moolticuted /rw/bind-dirs/usr/bin/
sudo cp QubesIncoming/SomeVM/moolticute /rw/bind-dirs/usr/bin/
sudo cp QubesIncoming/SomeVM/69-mooltipass.rules /rw/bind-dirs/etc/udev/rules.d/
sudo cp QubesIncoming/SomeVM/moolticuted.service /rw/bind-dirs/usr/lib/systemd/system/

Restart vault and run moolticuteand it should work…
The systemd service currently has some trouble working, I might check it in the future what is the bug.