rixxc/KeePassDX
1
0
Fork 0
mirror of https://github.com/Kunzisoft/KeePassDX.git synced 2025-12-04 15:49:33 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add Play service signature

Jérémy JAMET
2025-10-27 20:28:03 +01:00
parent 4ef92d2e54
commit c20438cd8b
1 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
Passkeys.md

@@ -143,25 +143,30 @@ _Local use is the easiest way and allows you to retrieve Passkeys from the servi
_You can also use your Passkeys from your phone to log in to a service from another device by bluetooth without going through the internet. This is very convenient for easily connecting to a web service on a PC, for example._
_**Please note: There are still limitations to this method, which depends on the Credential Provider API of your phone and the remote device. If the two are not compatible, the procedure will fail. Refer to the documentation for your second device for more information.**_
_**Please note: There are still limitations to this method, which depends on the Credential Provider API of your phone which uses Google Play Services and depends on the remote device. If the two are not compatible, the procedure will fail. Refer to the documentation for your second device for more information.**_
1. The KeePassDX Free build does not need to perform this operation, it validates the Play services package by default, but if you are using the **KeePassDX Libre build**, you must set **Play services as a privileged application**. If you agree to have your Passkeys transferred to this service, then verify the `com.google.android.gms` signature and set the package as a privileged application. The known signatures :
* `7C:E8:3C:1B:71:F3:D5:72:FE:D0:4C:8D:40:C5:CB:10:FF:75:E6:D8:7D:9D:F6:FB:D5:3F:04:68:C2:90:50:53`
* `D2:2C:C5:00:29:9F:B2:28:73:A0:1A:01:0D:E1:C8:2F:BE:4D:06:11:19:B9:48:14:DD:30:1D:AB:50:CB:76:78`
* `F0:FD:6C:5B:41:0F:25:CB:25:C3:B5:33:46:C8:97:2F:AE:30:F8:EE:74:11:DF:91:04:80:AD:6B:2D:60:DB:83`
* `19:75:B2:F1:71:77:BC:89:A5:DF:F3:1F:9E:64:A6:CA:E2:81:A5:3D:C1:D1:D5:9B:1D:14:7F:E1:C8:2A:FA:00`
1. On your other device (here on a Windows web browser), click the Passkey login button.
2. On your other device (here on a Windows web browser), click the Passkey login button.
<img width="800" alt="Image" src="https://github.com/user-attachments/assets/73297c17-d463-45f4-9f81-ccf70f0abc7c" />
2. Choose Android device (the first option).
3. A dialog box will ask you to activate Bluetooth. Activate it if it is not already activated, and a QR code will be displayed.
3. Choose Android device (the first option).
4. A dialog box will ask you to activate Bluetooth. Activate it if it is not already activated, and a QR code will be displayed.
<img width="400" alt="Image" src="https://github.com/user-attachments/assets/3b2045d7-1330-43f9-9d78-b3df2b43eb7b" />
4. Scan from your Android device containing KeePassDX with your QR code reader app.
5. Scan from your Android device containing KeePassDX with your QR code reader app.
5. Connect the devices (establish device trust) in the system dialog on the phone.
6. Connect the devices (establish device trust) in the system dialog on the phone.
6. A link will redirect you to KeePassDX to select the Passkey entry to use.
7. A link will redirect you to KeePassDX to select the Passkey entry to use.
Voilà! The selected entry will allow you to connect to your second device.
7. After the device trust has been established, the phone will appear the next time you try to log in with a passkey. I.e. on https://webauthn.io use the option Authenticate.
8. After the device trust has been established, the phone will appear the next time you try to log in with a passkey. I.e. on https://webauthn.io use the option Authenticate.
<img width="500" alt="Image" src="https://github.com/user-attachments/assets/be1614e4-4fd0-486d-843f-80b762c2d175" />