[BUG] SFTP support incorrectly jumping to root of server

[DeepMac]

Checks

• [X] I have read the FAQ section, searched the open issues, and still think this is a new bug.

Describe the bug you encountered:

When connecting to my account on Dreamhost via the SFTP option, I got an error about not finding a file. Sleuthing led me to realize that the "optional" directory field was not relative to my home directory in SFTP on the server, which is the same as my account home (typical /home/user path). I had set it to "/pki" because I made a sub-directory in my account for Keepass files.

Even when removing the default slash entirely from the directory field, it would jump to the root of the server. I would instead expect to be in my home directory of the account I logged in with. Once I explicitly coded the full to my home directory it worked as expected.

Since by default an SSH/SCP/SFTP server will set cwd to the home directory specified for the account logging in, there's something switch which shouldn't. Perhaps an artifact of the new library.

May or may not relate to #1026

Describe what you expected to happen:

I would instead expect to be in my home directory of the account I logged in with.

What version of Keepass2Android are you using?

1.09e-r7

Which version of Android are you on?

13

[scarlion1]

I tried everything:

• keeping the default /
• removing the default and using nothing
• ~
• ~/subdir
• /home/user
• /home/user/subdir
• probably some others

The only thing that did work, at least, was using the full path, 𝒾.ℯ. /home/user/subdir/db.kdbx.

Although, it just occurred to me that, due to java quirkiness, adding a trailing slash to the path may do the trick.  Unfortunately, I'm out of time and can't test that right now.  Does it help you at all, @DeepMac ?

[DeepMac]

That's what I had to do, just specify the entire path including the filename in the initial directory setting. Works like a charm.

I recall that some SFTP servers can be configured with chrooted perms so that a user attempting to access / will always end-up at the top of their home dir. It may be my provider doesn't do that

I suggest updating docs/FAQ to address this.