nassh: Change the order of gnubbyd extension ids
Reported by
ag...@chromium.org,
Nov 7
|
|||
Issue descriptionChrome Version : 70.0.3538.77 What steps will reproduce the problem? When two gnubbyd extension (dev,prod) are installed, we can't predict which on will be used. What is the expected result? It should be in order, dev then prod e.q extension (dev): klnjmillfildbbimkincljmfoepfhjjj extension: lkjlajklkdhaneeelolkfgbpikkgnkpk app (dev): dlfcjilkjfhdnfiecknlnddkmmiofjbg app: beknehfpfkghjoafdifaflglpjkojoco component extension (built-in): kmendfapggjehodndflmmgagdbamhnfd What happens instead? Currently nassh.GoogleRelay.findGnubbyExtension picks the first available gnubbyd extension.
,
Nov 7
,
Nov 13
The following revision refers to this bug: https://chromium.googlesource.com/apps/libapps/+/7565fc1aec962c5d5250747a3f50971633ad5bc0 commit 7565fc1aec962c5d5250747a3f50971633ad5bc0 Author: Mike Frysinger <vapier@chromium.org> Date: Tue Nov 13 04:40:18 2018 nassh: prefer certain versions of gnubbyd The gnubbyd team prefers we prefer specific gnubbyd versions rather than the current algorithm of "whichever responds first". List the order, and then check the results based on that. Bug: chromium:902588 Change-Id: Ibd379ce3ed8a360fc971caddc3e0484c7a2988ab Reviewed-on: https://chromium-review.googlesource.com/c/1322509 Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Vitaliy Shipitsyn <vsh@google.com> [modify] https://crrev.com/7565fc1aec962c5d5250747a3f50971633ad5bc0/nassh/js/nassh_google_relay.js
,
Nov 13
it'll be fixed for the 0.10 release |
|||
►
Sign in to add a comment |
|||
Comment 1 by vapier@chromium.org
, Nov 7Status: Available (was: Unconfirmed)
Summary: nassh: Change the order of gnubbyd extension ids (was: Change the order of gnubbyd extension ids)