Only happens over SSH/SCP using IOProtocolExt, and only with the desktop
client (v2.34 for Windows, Win7 x64).
Opening and saving exactly the same database locally takes ~1 second.
Opening and saving exactly the same database over SSH/SCP, using the
Android client KeePass2Android, also takes ~1 second.
The database is just ~45KB and contains 56 entries.
Copying and saving that file to/from the same remote server, using
SCP/SSH from the command line on the same machine, is instantaneous.
All software that might interfere with the process has been disabled
(firewall, antivirus, etc.).
I've tried alternately enabling and disabling such options as "Verify
written file after saving" and "Use file transactions for writing
databases", with no effect.
Why is KeePass struggling here?
Thanks.
Last edit: Homer 2016-10-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I didn't keep an exact record, but IIRC I've been using KeePass since v2.31 (via Chocolatey), and all versions exhibited exactly the same problem. The pressures of work kept me from reporting sooner.
The "-debug" switch shows a lot of output, none of which looks much like errors to my untrained eye. Sadly I can't copy and paste it, as the output window doesn't allow text selection. I could post screenshots, unless there's a way to redirect Windows' stderr (if it has such a thing) to a file.
Let me know if there's anything specific you need.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Only happens over SSH/SCP using IOProtocolExt, and only with the desktop
client (v2.34 for Windows, Win7 x64).
Opening and saving exactly the same database locally takes ~1 second.
Opening and saving exactly the same database over SSH/SCP, using the
Android client KeePass2Android, also takes ~1 second.
The database is just ~45KB and contains 56 entries.
Copying and saving that file to/from the same remote server, using
SCP/SSH from the command line on the same machine, is instantaneous.
All software that might interfere with the process has been disabled
(firewall, antivirus, etc.).
I've tried alternately enabling and disabling such options as "Verify
written file after saving" and "Use file transactions for writing
databases", with no effect.
Why is KeePass struggling here?
Thanks.
Last edit: Homer 2016-10-05
See this screencapture.
Does it happen with other versions of KeePass?
cheers, Paul
I didn't keep an exact record, but IIRC I've been using KeePass since v2.31 (via Chocolatey), and all versions exhibited exactly the same problem. The pressures of work kept me from reporting sooner.
The "-debug" switch shows a lot of output, none of which looks much like errors to my untrained eye. Sadly I can't copy and paste it, as the output window doesn't allow text selection. I could post screenshots, unless there's a way to redirect Windows' stderr (if it has such a thing) to a file.
Let me know if there's anything specific you need.
Correction, it must have been since v2.32, since that is the earliest version supported by IOProtocolExt.
I've just tested version 2.32 now, with the same results.
Redirecting stderr and stdout under Windows works like this:
keepass.exe >stderr.log 2>stdout.log -debug database options
Unfortunately that produces zero-byte files.
Here's some screenshots instead.
That's me opening the database, modifying an entry then saving it.
Last edit: Homer 2016-10-05
I switched to FTP (i.e. stopped using IOProtocolExt), and this resolved the issue.
Thanks for letting us know.
cheers, Paul