-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitwarden Android Beta (2024.12.0 (19597)) fails to sync with SSH keys #5322
Comments
Vaultwarden doesn't have anything special for this except that it returns the json blob exactly as received. It probably means the stored data is not valid i think. But i haven't checked it. Does the fingerprint show in the desktop client? |
Yes, on desktop client with Linux and Windows SSH key features (add, list, edit, etc...) works well. |
Could you check the database for this specific key and what is in the data column? |
Here is the data for the SSH key row.
|
Not sure how your export was done because of the double Ill have to check my self how this is returned to the client then. |
I've corrected it by changing the export format. |
You could try to install the dev version of the Android client which should output the request and response data of the http call. Which in turn should show if the data is there or not. |
I completely wiped all SSH key rows from the database and reimported keys, and the symptoms disappeared. |
hi there. I'm having the same problem and I've found the cause of it here's a log from the app:
turns out that either way, I don't think it makes sense for the backend to allow such keys, since clients will reject anything that appears to be an invalid key |
The problem is, that we actually do not care what the data object is and how this is formed. The main reason for us to not care on what the clients are sending as data blob, is that new features or additions which are done via that data blob will just work out-of-the-box, without us having to update it every time. It has the downside of these kind of issue. What we currently do is fix the output of the sync. But, yes this is because of the clients not sending the correct data back to the server, and could be a faulty client indeed. |
If any of the mandatory ssh-key json data values are not a string or are an empty string, this will break the mobile clients. This commit fixes this by checking if any of the values are missing or invalid and converts the json data to `null`. It will ensure the clients can sync and show the vault. Fixes dani-garcia#5343 Fixes dani-garcia#5322 Signed-off-by: BlackDex <black.dex@gmail.com>
* Refactor the uri match change Refactored the uri match fix to also convert numbers within a string to an int. If it fails it will be null. Signed-off-by: BlackDex <black.dex@gmail.com> * Fix ssh-key sync issues If any of the mandatory ssh-key json data values are not a string or are an empty string, this will break the mobile clients. This commit fixes this by checking if any of the values are missing or invalid and converts the json data to `null`. It will ensure the clients can sync and show the vault. Fixes #5343 Fixes #5322 Signed-off-by: BlackDex <black.dex@gmail.com> --------- Signed-off-by: BlackDex <black.dex@gmail.com>
Vaultwarden Support String
Your environment (Generated via diagnostics page)
EXPERIMENTAL_CLIENT_FEATURE_FLAGS=ssh-key-vault-item,ssh-agent
Config & Details (Generated via diagnostics page)
Show Config & Details
Environment settings which are overridden: ADMIN_TOKEN
Config:
Vaultwarden Build Version
v1.32.7
Deployment method
Official Container Image
Custom deployment method
No response
Reverse Proxy
nginx/1.27.2
Host/Server Operating System
Linux
Operating System Version
6.12.4-arch1-1 x86_64 GNU/Linux
Clients
Android
Client Version
Android Beta 2024.12.0 (19597)
Steps To Reproduce
Expected Result
Sync success
Actual Result
Sync failed
Logs
Bitwarden Android Beta:
adb logcat
logThe log reports
Network Error: https://api.bitwarden.com/sync
but I'm connecting to Vaultwarden so that can be ignored.Screenshots or Videos
No response
Additional Context
Details
Bitwarden Android Beta requires
ciphers.sshKey.keyFingerprint
, but Vaultwarden's/api/sync
does not return this property.This bug does not occur if the SSH key is not in the vault.
Vaultwarden's SSH key feature works well with the Desktop client.
The text was updated successfully, but these errors were encountered: