The fix is only for RSA keys and ed25519 keys are not found or accepted.
However, I suspect that the problem is not that of PCManFM but of
another component. That might be bug #1393531
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This seems to be fixed in vivid. The steps to test it are.
1 set up a machine with openssh-server and disallow password
authentication. Then set up access using keys.
2. try connecting from the client machine using PCManFM and the URI for
the remote machine: sftp://u...@server.example.org/
PCM
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
The key is already added to the other machine and the text utility
sftp(1) works just fine with the key while in the same session PCManFM
does not. What is the way to get verbose logging output from PCManFM?
Running it in the terminal with no options provides no extra output when
the login fails.
This is not a PCManFM issue, you should add your key into
~/.ssh/authorized_keys file on another machine and PCManFM cannot help
you with that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1227305
Ti
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1227305
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s