sftp connection with default rsa-keygen generated privatekey

[bpstrngr]

could be that i'm just missing something, but it is a valid private key file actually.

App Version:
latest

Affected Device(s):
Samsung note 10 lite with Android 13.0

Describe the bug
invalid privatekey after passphrase input

To Reproduce
Steps to reproduce the behavior:

1. add a new sftp server and provide private key path (termux home directory wasn't accessible so i copied it to storage/emulated/0/Download/id_rsa and chmod 700-ed it)
2. select the server in the fike explorer sidebar and privide passphrase on prompt
3. see error message "invalid privatekey: [B@dd2exxd"

Expected behavior
successful authentication

[massivemadness]

I guess I'm just using outdated library that can't handle your key.
If you know how the algorithm works you can help me figure it out 😄 (1, 2, 3, 4, 5)
I can make an experimental build for you if you have time to test it

[bpstrngr]

ugh, i'm not much of a cryptographer but i might try to look into it. the file was last updated in 2019 and i do see "RSA" mentioned so seems more like a bug than a missing feature due to outdatedness. thanks for the hint though, i suppose i'd need to figure out how to build it myself if i am to begin. did you think of patching/forking jsch, or intercepting it with some error handling?

[massivemadness]

There's a fork that is being updated, but I could try to fully switch to sshj 🤔
Anyway I'll text you here when the build will be ready

[massivemadness]

Hi @bpstrngr, try this build - 4588280564

[bpstrngr]

i checked out the build, issue persists. :/

[massivemadness]

I just checked it, should be fixed now (4620884875)

[segln]

Maybe you should generate PEM format key, executing ssh-keygen with -m pem option.
But you have to remove .pem extension. See #180 (comment) .

[massivemadness]

Fixed in v2023.1.4