On Wed, Aug 26, 2020 at 12:28 PM Mike Frysinger <
vap...@chromium.org> wrote:
>
> On Wed, Aug 26, 2020 at 3:17 PM John Stultz <
john....@linaro.org> wrote:
>>
>> On Wed, Aug 26, 2020 at 11:43 AM Mike Frysinger <
vap...@chromium.org> wrote:
>> >
>> > unfortunately this is all outside of our control in both regards :(. Chrome manages the update/corruption/repair cycle, as well as what happens to synced settings when you hit the repair button.
>> >
>> > i saw the same thing with my SSH apps, but not SSH extensions. i suspect a bug in Chrome handling of apps. have you installed the extension variant ?
>> > -mike
>>
>> Sorry, I might have used the wrong terminology. I was in
>> chrome://extensions/ when I hit repair, but it is listed in the apps
>> subsection of that page.
>
>
> your terminology is fine. based on your description, you are using the app variant. please migrate to the extension instead.
>
https://chrome.google.com/webstore/detail/iodihamcpbpeioajjeobimgagajmlibd
>
https://chromium.googlesource.com/apps/libapps/+/HEAD/nassh/doc/app-to-ext-migration.md
>
Ok. I was aware the Chrome Apps were going away, but it wasn't obvious
I would need to migrate to the extension. It's a bit confusing, and
seemingly duplicative, so users may need help realizing they should
switch.
>> You mention Chrome manages, it, but is the "corruption/repair" cycle
>> normal to see? I just want to make sure it not likely something funky
>> on one of my systems or something in my config that is tripping it? I
>> get a little paranoid with something as important as ssh security-wise
>> acts "strange". :)
>
>
> it is not normal. i can't think of a reason why it should happen at all in CrOS if the logic was written correctly.
>
> please file feedback using Alt+Shift+i whenever you see such a corruption event.
Ok. So far it has been after updates every time.
thanks
-john