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

--insecure flag for insecure features (local imports and local images) #7

Closed
polyjitter opened this issue Dec 13, 2016 · 1 comment
Closed

Comments

@polyjitter
Copy link

Of course, default behavior should definitely be to be as secure as possible; however, this also comes with the side effect of the inability to use local resources. When a resource is ~8MB, it may be preferable to use i t locally.

For people who desire these feature, at the cost of Electron security, a flag for such features could be helpful.

@polyjitter polyjitter changed the title --insecure flag for insecure features (local imports and local images) --insecure flag for insecure features (local imports and local images) Dec 13, 2016
@leovoel
Copy link
Owner

leovoel commented Dec 13, 2016

i don't have any strong opinions on this besides the fact that it's quite the slippery slope.

anyway, for reference,
http://electron.atom.io/docs/api/browser-window/#new-browserwindowoptions
the webSecurity option in the webPreferences object is what needs to be changed.

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

2 participants