dlech / KeeAgent

ssh agent plugin for KeePass 2.x
http://lechnology.com/software/keeagent
Other
537 stars 35 forks source link

Issue loading ed25519 keys on Fedora 28 #235

Closed thecjharries closed 6 years ago

thecjharries commented 6 years ago

I was interested in generating some new keys and testing out upgrading some of the boxes I support. At the moment, KeeAgent won't load any ed25519 keys. It fills the comment box with <Error loading key from attachment>, similar to #190.

$ cat /etc/fedora-release
Fedora release 28 (Twenty Eight)
$ dnf list keepass
Last metadata expiration check: 7:46:23 ago on Sun 20 May 2018 02:21:25 AM CDT.
Installed Packages
keepass.x86_64                                    2.38-4.fc28                                    @fedora
$ mono --version
Mono JIT compiler version 4.8.0 (Stable 4.8.0.520/8f6d0f6 Wed Sep 20 21:27:10 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
    TLS:           __thread
    SIGSEGV:       normal
    Notifications: epoll
    Architecture:  amd64
    Disabled:      none
    Misc:          softdebug 
    LLVM:          supported, not enabled.
    GC:            sgen
$ ls ~/Downloads/KeeAgent*
~/Downloads/KeeAgent_v0.10.1.zip

To verify the issue, I tried several things:

I'm new to debugging KeePass. I know what I've provided isn't a lot to go on. Are there logs I can attach that would be useful? Is there I should try to fix it myself (e.g. updating things, which I've done; this is a completely fresh install of everything). A bit later in the week I can build a Vagrant box to see if I can duplicate the issue elsewhere.

dlech commented 6 years ago

Can you upload an example key that causes this issue?

thecjharries commented 6 years ago

This is interesting. I can't duplicate the bug anymore. This is the key I was using before. It does not have a passphrase.

-----BEGIN OPENSSH PRIVATE KEY-----
b3BlbnNzaC1rZXktdjEAAAAABG5vbmUAAAAEbm9uZQAAAAAAAAABAAAAMwAAAAtzc2gtZW
QyNTUxOQAAACDB65AXTa+8d8mbXPBTvwYDGn8wZ5QuMQGiDBXcQpji0QAAAKAj9R1lI/Ud
ZQAAAAtzc2gtZWQyNTUxOQAAACDB65AXTa+8d8mbXPBTvwYDGn8wZ5QuMQGiDBXcQpji0Q
AAAED+75kcrQjmi3liVQTQcTiC2eTWBPg+7C8/9ik1BiPa1cHrkBdNr7x3yZtc8FO/BgMa
fzBnlC4xAaIMFdxCmOLRAAAAHGNqaGFycmllc0BneGMtZmVkb3JhLTI4LndvdHcB
-----END OPENSSH PRIVATE KEY-----

However, I can't reproduce this now. I tried reloading the key and it works. I generated a proper key with a passphrase and that worked too. Between now and then I noticed I was pointing to the wrong file in $SSH_AUTH_SOCK, but I haven't changed anything else. Pointing to the wrong file again didn't cause the issue.

Chalk this up to something I must have done. I'm closing the issue. Thanks for taking the time to respond. I really appreciate the work you've done with this project. I'm sorry I reported an error on my end.