|Issue 4643||SSH key is broken on schema upgrade|
|Starred by 4 users||Reported by org...@gmail.com, Sep 27||Back to list|
Affected Version: 2.13 What steps will reproduce the problem? 1. Upgrade from 2.12 to 2.13 What is the expected output? All SSH keys should be imported properly. What do you see instead? Some of the keys are not. Please provide any additional information below. The initial import of my keys looks like this (in All-Users.git). I replaced all the addresses and characters in the key: https://gist.github.com/orgads/ac48122677014253562e4193e5bb613a Notice one of the lines is split into 4 lines. All of these 4 are considered invalid. I might have pasted this key once from somewhere with multiple lines, although I can't find any evidence for \n in the corresponding 2.12 DB entry.
Might have been caused by https://github.com/gerrit-review/gerrit/commit/07952c069abd75abd6d33e58561307d86e0cabb9
But i have no idea how to fix it, or if that was intentional.
Hi, I feel that we saw the same issue for several people in my company. Their ssh key was working correctly, but then after the upgrade of Gerrit from 2.12 to 2.13, there were like 3, 4 other keys and they were not considered valid. Are you working on this issue ? They could access Gerrit by re-putting their keys, but that was weird ^^"
RFC change uploaded: https://gerrit-review.googlesource.com/#/c/91815/ but I haven't tested with a live server yet. I need to find a way to get a 2.12 server running with SSH keys containing line breaks.
|► Sign in to add a comment|