[GH-ISSUE #1605] keepassxc: Challenge-Response field is greyed out unless 'private-dev' and 'protocol' are disabled #1074

New issue

Closed

opened 2026-05-05 07:25:07 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 07:25:07 -06:00

Owner

Originally created by @Ryujinra on GitHub (Oct 14, 2017).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1605

KeepassXC has a challenge-response field for unlocking the database with a hardware token. That field is greyed out and authentication is not possible unless protocol and private-dev are commented out in keepassxc.profile (then behaviour is as expected).

Originally created by @Ryujinra on GitHub (Oct 14, 2017). Original GitHub issue: https://github.com/netblue30/firejail/issues/1605 KeepassXC has a challenge-response field for unlocking the database with a hardware token. That field is greyed out and authentication is not possible unless protocol and private-dev are commented out in keepassxc.profile (then behaviour is as expected).

gitea-mirror

2026-05-05 07:25:07 -06:00

closed this issue
added the
duplicate
label

gitea-mirror commented

2026-05-05 07:25:11 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Oct 14, 2017):

See https://github.com/netblue30/firejail/issues/1553#issuecomment-329915153

@SkewedZeppelin commented on GitHub (Oct 14, 2017): See https://github.com/netblue30/firejail/issues/1553#issuecomment-329915153

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#1074

No description provided.

Rows
Columns