The following revision refers to this bug:
  https://chromium.googlesource.com/apps/libapps/+/238a505a7f204e37ad03ef7a7b2f5c669d454fb1

commit 238a505a7f204e37ad03ef7a7b2f5c669d454fb1
Author: Mike Frysinger <vapier@chromium.org>
Date: Thu Jan 04 22:23:05 2018

nassh: parse out fingerprint from ssh:// URIs

We don't actually add it to the known key database, but we at least
parse it out so it's otherwise handled correctly.

BUG=chromium:706536

Change-Id: I0ce6cc97ca42b1fd94a1bae8b3f583dbaf1c00c4
Reviewed-on: https://chromium-review.googlesource.com/846385
Reviewed-by: Brandon Gilmore <varz@google.com>
Tested-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/238a505a7f204e37ad03ef7a7b2f5c669d454fb1/nassh/js/nassh_command_instance_tests.js
[modify] https://crrev.com/238a505a7f204e37ad03ef7a7b2f5c669d454fb1/nassh/js/nassh_command_instance.js

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot