Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Settings/Keys: keyPair backup didn't work #611

Closed
vLooz opened this issue May 8, 2015 · 11 comments
Closed

Settings/Keys: keyPair backup didn't work #611

vLooz opened this issue May 8, 2015 · 11 comments
Assignees

Comments

@vLooz
Copy link

vLooz commented May 8, 2015

what happened:
I could not backup my KeyPair from settings/keys. When I hit the 'backup'-button, a new empty tab was opened, but no key file was downloaded.
See #604 for more background

what should have happened:
The key file download should start automatically.

@let4be
Copy link

let4be commented May 8, 2015

Safari bugs ^^ this is still unresolved and I can't effectively troubleshot this problem due to absense of mac and safari

There was a huge discussion here:
eligrey/FileSaver.js#129
eligrey/FileSaver.js#12

@let4be
Copy link

let4be commented May 8, 2015

This also affects all other download actions

@let4be let4be added the blocked label May 8, 2015
@let4be
Copy link

let4be commented May 8, 2015

If I could I would just advice users to boycott bugged safari that doesn't follow accepted standards

@vLooz
Copy link
Author

vLooz commented May 8, 2015

:D humm... Many apple users would be quite upset. We can recommend to use another browser though.

Still the basic functions should work on every of the big browsers (considering safari a big browser here), imo.

@let4be
Copy link

let4be commented May 8, 2015

There was a workaround but need to think how to properly apply it and not break currently used download method which FileSaver.js offers

@hyzhak do you have mac to test this?

@mlooz
Copy link

mlooz commented May 8, 2015

I have access to an old mac. What needs to be tested?

@vviikk
Copy link

vviikk commented May 10, 2015

we cant. unless we send info to the server this is impossible for a locally generated JS file in safari. and Apple aren't gonna fix this problem very soon. maybe, never. so we should focus on informational messages.
we can say due to security concerns we dont sent any data to the Lavaboom server. Hence, you can either use a browser like "chome" or "firefox"

@vLooz
Copy link
Author

vLooz commented May 11, 2015

The most important info for the user is that key generation might take a while on a safari browser. I think thats the main thing we need to write on a note screen. We can provide a low-key "learn more" for the tech-savvy to open a new tab with more information.

@paulhugel
Copy link

I have mac with Safari and 100Mbit down and 5bit uplink
I have Apple Remote Desktop and Parallels Window7 Ultimate

If instructed can perform specific requested function and corresponding Console Log and if available Full Report
Would be helpful to know What System Diagnostic Report or can capture all messages for given time during requested function action and specific System Diagnostic Report can be captured.
osx 10 10 3
safari 8 06 macintosh

@paulhugel
Copy link

Hope This does not complicate Settings/Keys: keyPair backup didn't work #611

Went to Settings-->Security--> Backup keys
output of screen capture with developer console view (no error reported ?)

next screen capture is snipet of new tab opened after initiating backup keys
export keys safari macintosh
safari keyring backup snipet new tab opened

@let4be
Copy link

let4be commented May 12, 2015

So, after reading the whole eligrey/FileSaver.js#12

I consider displaying a warning for each save action for all Safari users - it has a ton of inconsistences in this area. Can't be fixed effectively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants