InformAction Forums

About two weeks ago, I took a NoScript update. Since then, 1Password no longer submits website passwords correctly.

Instead of populating username/password fields and hitting enter, 1Password just populates the fields--but never submits.

I didn't see anything in these forums that discusses a solution, though a discussion on the 1Password site does talk about the problem--and suggests that NoScript folks might have an answer.

I'm currently running Mac OS 10.7.2, Firefox 8.0.1, 1Password 3.8.10 and NoScript 2.2.2rc3

Thanks
Snakeears

If the other people have specific ideas, by all means, post them.

I don't use 1Password; rather I use Password Safe, which presently is Windows/Linux only, although I believe Mac versions are in the works. The advantage being that it does not rely on a web site, but is stored and operated entirely on your own machine. So there is no web scripting to block or unblock - it's done locally (from the machine). -- Just saw that the "cloud" is only an *option* on 1Password. Which are you using: local or cloud-based?

Password Safe is also free and open-source.

NOTE: Not an endorsement; a free-speech opinion based on personal experience only. I have no connection to Password Safe, personally or financially, except that I have had a bit of Internet contact with cryptographer Bruce Schneier, who designed the encryption for Pasword Safe. Since I can't control what the program developers do, or how you use it, I cannot be held liable or responsible for your use of it. (Pesky lawyer.)

In the meantime, when this error occurs, please open Firefox Tools > Web Develper > Error Console. Click the red "Error" icon. Copy and paste all red Error messages here, please.
Also click the blue "Messages" icon, and look for any that are pertinent to NoScript (usually start with [NOSCRIPT]. Paste here also, please.
And what scripts show up in the NoScript menu as allowed, and which show as blocked? Other entries? (Blocked objects?)

Thanks.

Thanks for your insight Tom.

I checked the FF console and didn't see anything NoScript-related in the console... but did see some 1Password entries. That got me thinking so I double-checked some 1P settings. Turns out the one that governs autosubmit got cleared. I am chalking the problem up to operator error.

To answer your 1P question, I use it locally. Not sure if the 1P cloud option is for backups or for active use. Anyway, I totally agree with you about the dubiousness of cloud-based storage of such information.

Thanks again.

Snakeears

snakeears wrote:Thanks for your insight Tom.

I checked the FF console and didn't see anything NoScript-related in the console... but did see some 1Password entries. That got me thinking so I double-checked some 1P settings. Turns out the one that governs autosubmit got cleared. I am chalking the problem up to operator error.

To answer your 1P question, I use it locally. Not sure if the 1P cloud option is for backups or for active use. Anyway, I totally agree with you about the dubiousness of cloud-based storage of such information.

Thanks again.

Snakeears

Thanks for reporting back. Will mark this as "Resolved". (Would mark it as "Invalid", meaning not a NS bug, but one user took that as an insult. Marked one as "Closed" once, and someone else changed that to "Invalid". ... we need to have a meeting and agree on terminology. )

Re: Backups: Absolutely. But to *your own* external media -- USB Flash drive, external HD, CD/DVD, whatever. No worries about it being lost/stolen with PWS; the db still can't be opened without the master pw, at least within our lifetimes, even with NSA's array. (Strong master pw, of course.)

Wtih PWSafe, the only file that needs to be backed up is the always-encrypted database of entries (decrypted only on-the-fly in RAM), which for my current 64 entries, including "challenge questions", alternate browser (always start the browser sandboxed when clicking to browse from PWS) etc., is a measly 16k. Slide it onto a Flash drive after any changes. If everything crashes, HD dies, whatever, just reinstall the tiny (2MB) app, then replace the default password file with your backup copy. Good to go instantly.

I wrote for myself a little DOS batch script that backs up this and a few other necessities, like the Fx profile folder, with two clicks and thirty seconds or so. I don't speak Mac, although I understand it's heavily Unix-based, so surely you could do something similar?

And you're very welcome. Cheers.