Comments (11)
If the password needs to be set only once and never needs to change, why can't
a random string of characters used for the password? This password could be
created when the extension is first enabled and it would then be stored with
the rest of the extension's settings. Since settings get saved across extension
updates, I think this would fix the problem of the password file getting reset
on an update too.
Original comment by kevman3000
on 9 Sep 2010 at 4:26
from notscripts.
Manual password entry is currently required because of the asynchronous nature
of the Google Chrome extensions API and the requirement that we must have
access to the encryption password right when a page loads. The portion of
NotScripts that uses the encryption password is the content script and for a
normal extension, it would use a chrome.extension.sendRequest(...) to retrieve
the password and updated settings from the portion of the extension where it
resides since content scripts are sandboxed from everything else.
chrome.extension.sendRequest(...) is does not return the needed values until
some portion of the scripts on a webpage have already run. The password file is
loaded by the content script before it runs it's code because we state to do
that always in the extension manifest. However, a Google Chrome extension does
not have permission to write to disk directly and cannot self edit it's
extension files.
Apple Safari has a canLoad(...) function that returns immediately and is well
suited to solve this problem. I'm hoping that Google allows canLoad(...) to
slip into Webkit so I can simplify NotScripts. Until the, we will have to wait
and see.
Original comment by [email protected]
on 9 Sep 2010 at 7:14
from notscripts.
Original comment by [email protected]
on 9 Sep 2010 at 7:14
- Changed state: Accepted
from notscripts.
[deleted comment]
from notscripts.
Please help resolve the password requirement issue by starring this Chromium
bug report:
http://code.google.com/p/chromium/issues/detail?id=54257
Original comment by [email protected]
on 27 Sep 2010 at 4:08
from notscripts.
The path on Linux is incorrect for my machine (ubuntu). I had to uninstall the
plugin to post this comment.
Original comment by [email protected]
on 2 Mar 2011 at 8:09
from notscripts.
It seems that I found a solution to this issue. By using programmatic
injection, I was able to provide the ENCRYPTION_KEY to the content scripts
without declaring it in a file. Take a look at the attached diff.
It's not 100% perfect at the moment, since blockAfter.js is broken (and I
didn't want to spend even more time unbreaking it). But as a proof of concept,
it seems to be working nicely.
Original comment by [email protected]
on 20 Apr 2012 at 2:26
Attachments:
from notscripts.
Just to clarify, the brokenness is related only to the fact that (at least for
me right now), the content scripts declared as document_start seem to be run
before the programmatic injection. So blockAfter.js is run before
blockStart.js. But that's it, the whole thing still seems to run before the DOM
is fully constructed, and before on-page scripts run.
Original comment by [email protected]
on 20 Apr 2012 at 2:29
from notscripts.
I have looked through the NotScript source files and determined it would be
easy for the author to allow for setting the password in the extension's
LocalStorage. It appears the author may not have known how to have content
scripts communicate with the extension backend to make this possible, but then
at some later point the author did figure out how to do this but never
incorporated it into the password mechanism.
But a more fundamental flaw is that the password should not be required at all,
as the reason it is required is to allow it to expose extension data to
websites without the websites being able to read it (but they can easily delete
it, on purpose or by accident). I will post a separate issue about my findings.
Original comment by megazzt
on 11 Jul 2012 at 2:45
from notscripts.
The instructions do not include password configuration for Chromebook
instllations of chrome, where OS access is quite likely limited for most users.
I like the cut of megazzt's jib; LocalStorage seems the way to go.
In the meantime, this extension appears unusable for the majority of Chromebook
users.
Original comment by [email protected]
on 28 Oct 2013 at 12:24
from notscripts.
I have Notscripts loaded on all my Chrome browsers, but I was very sad that it
cannot run on my Chromebook. I feel like I'm naked when I go to websites with
all their scripts running...
Original comment by [email protected]
on 5 Sep 2014 at 7:51
from notscripts.
Related Issues (20)
- Doesn't appear to be working properly with newest chromium/ubuntu 13.10
- Treats iframe as parent domain
- New Chrome Installation won't allow access to whitelisted sites
- Cannot find notscripts extension for Version 34.0.1808.0 canary
- I can't reposition photos on Facebook while NotScripts is enabled.
- windows scripting error
- Location of password file is incorrect for Google Chrome Unstable
- blank page when creat a new tab
- regexps in whitelist
- Feature - Separate whitelist/blacklist for External Scrips
- NotScripts icon dissapearing
- Cant unblock pages since upgrade HOT 1
- Not workingt on Chrome Canary Build 64bit
- wowinterface.com won't load with Notscripts
- Plugin repeatedly deaktivated
- Does not run on Chromebook
- Page does not load
- Can't run the "CHANGE__PASSWORD__HERE.js" file. Similar to Issue 173(windows scripting error)
- Enter one-line summary HOT 4
- Fails to list all scripts
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from notscripts.