by Questor » Tue Oct 23, 2018 1:54 am
Why should NoScript Developers be forced to make NoScript software changes caused by unannounced TOR staff Browser mods? NoScript worked fine with early Tor/NoScript v60 editions and now, NoScript per-site permissions fail to work after Tor is closed - due to undisclosed mods by TOR staff... I do not think that TOR devs should force experienced TOR users into a new TOR upgrade without full disclosure that TOR has reduced integration with NoScript due to undisclosed changes by TOR Staff.
No software security is perfect and I always use the latest version commercial Anti-Virus/Malware software, but this TOR/NoScript software combo enables me to have somewhat better control of websites cookies, Javascripts and Java Apps that may try to load on my computer and could be misused harvest my private info. I specifically use TOR and NoScript together as an additional security/privacy method to help block websites from running undisclosed JavaScript/Java code, Cookies, and Tracking software without my knowledge or permission. IMHO, other webBrowsers that complete with TOR/NoScript do not have the same nor as good a set of Browser controls that help regulate unauthorized Apps, Tracking, Cookies, Adware, or Malware software.
Our family's personal & tax refund info on private online company databases have been hacked several times in the past year through several online companies. Fortunately, these online data breaches regarding our personal info were soon discovered and we did not suffer any loss to our reputation or finances. The TOR/NoScript software combo helps detect malware/virus/tracking attempts whenever I visit a website, while it notifies me and lets me choose which Apps or Cookies I will allow. The info theft we experienced did not occur through TOR or NoScript, but I really want TOR Staff to restore this added security preference that allows me to auto-run TOR/NoScript together without my having to always reimport/reconfigure site permissions after TOR starts.
These undisclosed TOR s/w mods implemented by TOR Staff reduce the functionality of NoScript and cause me to take extra manual steps and added time to re-configure NoScript to work correctly like earlier TOR v60 versions. It seems these NoScript site permissions problems started to occur within the past several months and apparently caused by Tor staff software changes that were not adequately disclosed in advance to the public and/or possibly not tested properly.
This surprise/undisclosed TOR/NoScript problem also shows TOR Staff's lack of communication or concern to inform the general public in advance about major changes that could affect other TOR-compatible software. I wonder if TOR Browser updates are now being released too quickly without adequate testing by TOR staff and/or volunteers.
The NoScript per-site permissions problem seems to have a simple solution... As discussed by others, TOR devs could include a pull-down menu choice within TOR Menus that allow experienced users to use a sliding bar to enable/disable NoScript access and/or JavaScript access. The default setting could be set to enable JavaScript, but allow experienced users like me the slide-bar choice to temporarily disable JavaScript or when I also want to run NoScript.
Why should NoScript Developers be forced to make NoScript software changes caused by unannounced TOR staff Browser mods? NoScript worked fine with early Tor/NoScript v60 editions and now, NoScript per-site permissions fail to work after Tor is closed - due to undisclosed mods by TOR staff... I do not think that TOR devs should force experienced TOR users into a new TOR upgrade without full disclosure that TOR has reduced integration with NoScript due to undisclosed changes by TOR Staff.
No software security is perfect and I always use the latest version commercial Anti-Virus/Malware software, but this TOR/NoScript software combo enables me to have somewhat better control of websites cookies, Javascripts and Java Apps that may try to load on my computer and could be misused harvest my private info. I specifically use TOR and NoScript together as an additional security/privacy method to help block websites from running undisclosed JavaScript/Java code, Cookies, and Tracking software without my knowledge or permission. IMHO, other webBrowsers that complete with TOR/NoScript do not have the same nor as good a set of Browser controls that help regulate unauthorized Apps, Tracking, Cookies, Adware, or Malware software.
Our family's personal & tax refund info on private online company databases have been hacked several times in the past year through several online companies. Fortunately, these online data breaches regarding our personal info were soon discovered and we did not suffer any loss to our reputation or finances. The TOR/NoScript software combo helps detect malware/virus/tracking attempts whenever I visit a website, while it notifies me and lets me choose which Apps or Cookies I will allow. The info theft we experienced did not occur through TOR or NoScript, but I really want TOR Staff to restore this added security preference that allows me to auto-run TOR/NoScript together without my having to always reimport/reconfigure site permissions after TOR starts.
These undisclosed TOR s/w mods implemented by TOR Staff reduce the functionality of NoScript and cause me to take extra manual steps and added time to re-configure NoScript to work correctly like earlier TOR v60 versions. It seems these NoScript site permissions problems started to occur within the past several months and apparently caused by Tor staff software changes that were not adequately disclosed in advance to the public and/or possibly not tested properly.
This surprise/undisclosed TOR/NoScript problem also shows TOR Staff's lack of communication or concern to inform the general public in advance about major changes that could affect other TOR-compatible software. I wonder if TOR Browser updates are now being released too quickly without adequate testing by TOR staff and/or volunteers.
The NoScript per-site permissions problem seems to have a simple solution... As discussed by others, TOR devs could include a pull-down menu choice within TOR Menus that allow experienced users to use a sliding bar to enable/disable NoScript access and/or JavaScript access. The default setting could be set to enable JavaScript, but allow experienced users like me the slide-bar choice to temporarily disable JavaScript or when I also want to run NoScript.