Replies: 8 comments
|
Well, that probably depends on what you are interested in. Other than that, if you are running a Gitblit instance, you could run the latest nightly build to see if it is really stable enough to be released. If you use tickets, though, you shouldn't because pushing to tickets seems to have been broken. |
|
SNI: Maybe solved by a jgit upgrade. I will try to run the latest and see if it works. |
|
1.10.0 snapshot looks good to me. ed25519 seems to be preferred for now. The old workarounds |
|
Interesting find, thank you. I will have to try the upgrade in order to find some wording to put into the release notes. Didn't think of that. I wonder why I didn't not encounter that. I didn't think it would complain about a changed host key but add a new one. |
|
Can you check this code in SshDaemon again: The file ssh-ed25519-hostkey.pem doesn't show up in my gitbit base dir, but the ssh client has this type saved in known_hosts. |
|
This looks weird if you look at the code, yes, but is actually intentional. The story here is that this version of SSHD requires a certain third-party library for Ed25519 keys. Probably because BouncyCastle didn't have support yet at the time. I do hope that the future versions will be able to simply use BouncyCastle so that I can get rid of that extra library. The keys that that library creates and writes are not in a proper OpenSSH format that other tools would recognise. In turn, it cannot handle proper OpenSSH Ed25519 created keys. Which is why there is special code already created accounting for both types, hoping to be able to support the normal type in the future. In principal, you should be able to generate a Ed25519 keypair with OpenSSH, store it there under the "ssh-ed25519-hostkey" name and Gitblit should be able to pick it up and use. |
|
Thanks. Maybe add this as comment to the code. |
|
Since version 1.10.0 has been released, I am setting this topic to closed. |
Uh oh!
There was an error while loading. Please reload this page.
Originally posted by @andrm in #1419 (comment)
All reactions