This problem is occurring because the test script was written on a system
with OpenSSH 6.8 (or greater) installed.  Notice the 2nd bullet point under
"New Features" on the following page:

http://www.openssh.com/txt/release-6.8

Older versions of OpenSSH used a hexed MD5 hash for fingerprints while 6.8
and greater use a Base64-encoded SHA256 hash (with the hash algorithm
prepended).  Unfortunately, I don't think any amount of "normalizing" will
fix this issue.

On Mon, Feb 1, 2016 at 3:36 PM, Dominik Perpeet <[email protected]> wrote:

> Exactly. Stef was referring to the normalize function here:
> https://github.com/cockpit-project/cockpit/blob/0a0250e8118c47ced529772758d49d6c5a60924f/pkg/users/test-list-public-keys.sh#L8
>
> Parsing text output is always problematic and has been an issue in the
> past, hence the normalization function.
>
> Maybe you can adjust it to work with the new output.
>
> -Dominik
>
>
> On 02/01/2016 09:32 PM, Jared Sutton wrote:
>
> It looks like "ssh-keygen -l -f <authorized_keys_file>" produces different
> output on wily (expected output) vs vivid (unexpected output)...
>
> [image: Inline image 1]
>
> On Mon, Feb 1, 2016 at 9:49 AM, Stef Walter <[email protected]>
> wrote:
>
>> Looks like the tests produce different output than are expected.
>>
>> Perhaps some changes are necessary to the normalize() function in
>> test-list-public-keys.sh file?
>> _______________________________________________
>> cockpit-devel mailing list
>> [email protected]
>>
>> https://lists.fedorahosted.org/admin/lists/[email protected]
>>
>
>
>
> _______________________________________________
> cockpit-devel mailing 
> [email protected]https://lists.fedorahosted.org/admin/lists/[email protected]
>
>
>
> _______________________________________________
> cockpit-devel mailing list
> [email protected]
>
> https://lists.fedorahosted.org/admin/lists/[email protected]
>
>
_______________________________________________
cockpit-devel mailing list
[email protected]
https://lists.fedorahosted.org/admin/lists/[email protected]

Reply via email to