InformAction Forums

After NoScript was updated to 1.9.1.11, I've been unable to log-in to the AT&T wireless website (the log-in sequence hangs, never finishes loading). I have att.com whitelisted, and have even tried disabling XSS in NoScript with no luck.

There is also an issue with a XSS alert about liveperson.com when visiting the AT&T website. Telling NoScript to do an unsafe reload, redirects you from the AT&T website to a blank (invalid) liveperson.com link.

Rolling back to 1.9.1.07 fixed the problem, so the issue was introduced in some revision after that.

I just logged in to my AT&T GoPhone account with no trouble at all, not even allowing any scripting. Checked my balance, etc. ... with NoScript 1.9.1.1

Exact URL of the login?
What scripts are showing in the menu, and which are you allowing and not allowing?

XSS alert: Open Firefox Tools > Error Console, click the red icon "Errors" at the top, and copy/paste them here, please? (right-click each one, click "copy").

Hmm, this is weird. I just updated from 1.9.1.07 back to 1.9.1.11 and now I'm not having a problem with logging-in or seeing any XSS alerts. Also when clicking on the tray icon, liveperson.com now shows up as a domain when visiting https://www.wireless.att.com/olam/login ... to=welcome while before it didn't and was producing an XSS alert instead. I do remember seeing something like 15+ errors in the error console when I saw it happen the first time, but unfortunately I didn't save them at that time.

The process I went through:
NoScript auto updated to 1.9.1.11, ATT.com log-in wasn't working and there was a liveperson.com XSS alert > disabled XSS & restarted Firefox still not working but now no XSS alert (obviously, since I disabled it)> Disabled NoScript restarted Firefox, was working > Installed NoScript 1.9.1.07, was working > Re-enabled XSS & restarted Firefox, was working with no XSS alert > updated to 1.9.1.11 once again just now and was also working.

All I can think of is for whatever reason NoScript 1.9.1.11 didn't update itself properly the first time (producing broken behavior), while the second time it did update correctly and fixed itself...

I'll keep my eye on it and see if I can reproduce the problem again over the next few days. If not, I guess it must have been some weird fluke.

Thanks, we'll mark this as Resolved for now.

If it happens again, please try the General Troubleshooting Instructions, which will help to isolate any extension conflicts, corrupt extension files, etc.

Thanks again for letting us know.