# KeepassXC HMAC problems caused by Firejail?

**URL:** <https://onlykey.discourse.group/t/keepassxc-hmac-problems-caused-by-firejail/543>\
**Category:** Hardware Password Manager\
**Created:** [November 19, 2021, 10:53pm UTC](https://onlykey.discourse.group/t/keepassxc-hmac-problems-caused-by-firejail/543 "2021-11-19T22:53:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![9Syd85](https://avatars.discourse-cdn.com/v4/letter/9/97f17d/32.png) [@9Syd85](https://onlykey.discourse.group/u/9Syd85)\
**Post date:** [November 19, 2021, 10:53pm UTC](https://onlykey.discourse.group/t/keepassxc-hmac-problems-caused-by-firejail/543/1 "2021-11-19T22:53:49Z")

</div>

Attempting to use OnlyKey 2.1.1 HMAC challenge-response for KeepassXC 2.6.6 on Linux Mint 20.1. The OnlyKey app works just fine, but KeepassXC doesn’t recognize the presence of the OnlyKey. When I refresh the list of hardware, nothing. Searching the forum I see a few others in the same boat.

I discovered that the only way I can get KeepassXC to recognize the OnlyKey is by running the flatpak version from the command line outside of Firejail protection.

```auto
flatpak run org.keepassxc.KeePassXC

```

That’s fine I guess, but inconvenient. Is there a way that I can tweak the Firejail profile to allow connecting to the OnlyKey?

---

<div class="post-metadata">

**Author:** ![t11](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@t11](https://onlykey.discourse.group/u/t11)\
**Post date:** [November 22, 2021, 2:14pm UTC](https://onlykey.discourse.group/t/keepassxc-hmac-problems-caused-by-firejail/543/2 "2021-11-22T14:14:47Z")

</div>

Do you have the OnlyKey UDEV rule added? There is an issue here that seems to resolve the same issue with Yubikey - [Firejail app cannot communicate with my Yubikey · Issue #1176 · netblue30/firejail · GitHub](https://github.com/netblue30/firejail/issues/1176)

---

<div class="post-metadata">

**Author:** ![9Syd85](https://avatars.discourse-cdn.com/v4/letter/9/97f17d/32.png) [@9Syd85](https://onlykey.discourse.group/u/9Syd85)\
**Post date:** [November 22, 2021, 11:50pm UTC](https://onlykey.discourse.group/t/keepassxc-hmac-problems-caused-by-firejail/543/3 "2021-11-22T23:50:14Z")

</div>

Thanks for finding that thread!

I copied /etc/firejail/keepassxc.profile to ~/.config/firejail/keepassxc.profile and then commented out the following lines. KeepassXC is able to detect the OnlyKey now.

```auto
#protocol unix,netlink
#private-dev

```