New issue
Advanced search Search tips

Issue 649458 link

Starred by 2 users

Issue metadata

Status: Verified
Owner: ----
Closed: Apr 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

nassh: settings are not restored after powerwash

Reported by moneta.m...@gmail.com, Sep 22 2016

Issue description

UserAgent: Mozilla/5.0 (X11; CrOS armv7l 8743.25.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.24 Safari/537.36
Platform: 8743.25.0 (Official Build) beta-channel nyan_big

Steps to reproduce the problem:
1. Install Secure Shell
2. Configure host(s) and port forwards
3. Sometime later, powerwash
4. Note that all hosts and port forwards are lost after extension is restored.

What is the expected behavior?
After the extension is restored, all defined hosts and port forwards should be syn'd back to the device (not keys or passwords).

What went wrong?
I suspect that the extension is using localStorage instead of chrome.storage / storage.sync.

WebStore page: https://chrome.google.com/webstore/detail/secure-shell/pnhechapfaindjhompbnflcldabbghjo

Did this work before? N/A 

Chrome version: 54.0.2840.24  Channel: beta
OS Version: 8743.25.0
Flash Version: Shockwave Flash 23.0 r0

These are relatively small amounts of data, but time consuming to manually reconfigure (especially with several port fort forwards per host).
 
Damnit. There's a separate backup function in options. Never mind.

Comment 2 by vapier@chromium.org, Mar 31 2017

Components: -Platform>Extensions Platform>Apps>Default>Hterm
SecureShell uses sync storage.  there was a bug in CrOS for a time wrt app data syncing.  is this still a problem ?
Status: Fixed (was: Unconfirmed)
Summary: nassh: settings are not restored after powerwash (was: Secure Shell settings are not restored after powerwash)
Status: Verified (was: Fixed)
Chrome OS 9532.0.0, 60.0.3092.0

Sign in to add a comment