vt1980 wrote:Why the "NoScript" requires updates almost every time that firefox turn on.
Perhaps because the developer responds quickly to newly emergent web threats, to reported and verified bugs, and to valuable suggestions for enhancement?
vt1980 wrote:It will be much more convenient.
NoScript could go to Microsoft's policy of issuing batch updates once a month, but that leaves you vulnerable to the new threats, and with the unfixed bugs, for a long time.
Are you on the development build channel? It's the best way to go, but if the frequency annoys you, go back to latest stable releases.
Those tend to come out about every two weeks or so, although still faster if there is an emergency (known exploit in the wild).
I prefer a bit of inconvenience in return for always having the latest fixes and enhancements (development builds), but if you choose differently, that's your choice to make.
And what
dhouwn said about an actual code change in the program, as opposed to databases. Two different things. New threat, new code.
Edit: It seems you're running Fx 3.6.26, so unless that's TOR or a user-agent switcher, the updates of Firefox itself are way behind.
Last v3 was 3.6.28; ended support 24 April 2012. Current supported version is Fx 12.0.
NoScript can't protect you against any unpatched flaw in an obsolete browser. If you want best possible safety, you must expend a little time to keep things up to date.