Import errors with KeePass 1.0 CSV #1098

Closed
opened 2026-04-06 01:34:22 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @Artim96 on 6/17/2024

Subject of the issue

Import errors with KeePass 1.0 CSV format

Deployment environment

  • vaultwarden version: v1.30.5
  • Install method: .deb files compiled with the guide from dionysius

  • Clients used: web vault, v2024.5.0

  • Reverse proxy and version: Nginx 1.26.1

  • MySQL/MariaDB or PostgreSQL version: psql (PostgreSQL) 15.6 (Debian 15.6-0+deb12u1)

  • Other relevant details:

Steps to reproduce

  • exported selection of passwords with KeePass 2.47 as KeePass 1.0 CSV for import at Organization level
  • create organization
  • create folder MyVault in organization
  • go to tools -> import data
  • select organization, default collection and KeePassX CSV format -> Is it even the same format? KeePassX has been abandoned almost a decade ago, KP2BW seems to be non-functional (or at least the installation guide has been edited in a way that figuring out how to install isn't feasible)

Expected behaviour

obvious

Actual behaviour

Error message in the web vault only says that nothing was imported

Troubleshooting data

Many entries like this:

[2024-06-17 11:00:02.743][tungstenite::protocol][TRACE] Received message Binary Data<length=3>
[2024-06-17 11:00:02.743][tokio_tungstenite][TRACE] /home/debian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-tungstenite-0.20.1/src/lib.rs:243 WebSocketStream.with_context
[2024-06-17 11:00:02.743][tungstenite::protocol][TRACE] Sending frame: Frame { header: FrameHeader { is_final: true, rsv1: false, rsv2: false, rsv3: false, opcode: Data(Binary), mask: None }, payload: [2, 145, 6] }
[2024-06-17 11:00:02.744][tungstenite::protocol::frame][TRACE] writing frame
<FRAME>
final: true
reserved: false false false
opcode: BINARY
length: 5
payload length: 3
payload: 0x029106
*Originally created by @Artim96 on 6/17/2024* <!-- # ### NOTE: Please update to the latest version of vaultwarden before reporting an issue! This saves you and us a lot of time and troubleshooting. See: * https://github.com/dani-garcia/vaultwarden/issues/1180 * https://github.com/dani-garcia/vaultwarden/wiki/Updating-the-vaultwarden-image # ### --> <!-- Please fill out the following template to make solving your problem easier and faster for us. This is only a guideline. If you think that parts are unnecessary for your issue, feel free to remove them. Remember to hide/redact personal or confidential information, such as passwords, IP addresses, and DNS names as appropriate. --> ### Subject of the issue Import errors with KeePass 1.0 CSV format ### Deployment environment <!-- ========================================================================================= Preferably, use the `Generate Support String` button on the admin page's Diagnostics tab. That will auto-generate most of the info requested in this section. ========================================================================================= --> <!-- The version number, obtained from the logs (at startup) or the admin diagnostics page --> <!-- This is NOT the version number shown on the web vault, which is versioned separately from vaultwarden --> <!-- Remember to check if your issue exists on the latest version first! --> * vaultwarden version: v1.30.5 <!-- How the server was installed: Docker image, OS package, built from source, etc. --> * Install method: .deb files compiled with the guide from [dionysius](https://github.com/dionysius/vaultwarden-deb) * Clients used: web vault, v2024.5.0 * Reverse proxy and version: Nginx 1.26.1 * MySQL/MariaDB or PostgreSQL version: psql (PostgreSQL) 15.6 (Debian 15.6-0+deb12u1) * Other relevant details: ### Steps to reproduce - exported selection of passwords with KeePass 2.47 as KeePass 1.0 CSV for import at Organization level - create organization - create folder MyVault in organization - go to tools -> import data - select organization, default collection and KeePassX CSV format -> Is it even the same format? KeePassX has been abandoned almost a decade ago, KP2BW seems to be non-functional (or at least the installation guide has been edited in a way that figuring out how to install isn't feasible) ### Expected behaviour obvious ### Actual behaviour Error message in the web vault only says that nothing was imported ### Troubleshooting data Many entries like this: ``` [2024-06-17 11:00:02.743][tungstenite::protocol][TRACE] Received message Binary Data<length=3> [2024-06-17 11:00:02.743][tokio_tungstenite][TRACE] /home/debian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tokio-tungstenite-0.20.1/src/lib.rs:243 WebSocketStream.with_context [2024-06-17 11:00:02.743][tungstenite::protocol][TRACE] Sending frame: Frame { header: FrameHeader { is_final: true, rsv1: false, rsv2: false, rsv3: false, opcode: Data(Binary), mask: None }, payload: [2, 145, 6] } [2024-06-17 11:00:02.744][tungstenite::protocol::frame][TRACE] writing frame <FRAME> final: true reserved: false false false opcode: BINARY length: 5 payload length: 3 payload: 0x029106 ```
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/vaultwarden#1098