Opened 4 months ago

Last modified 7 weeks ago

#2536 new defect

Different between Noscript effect in TBB and I2P Browser

Reported by: anonymous maybe Owned by: Meeh
Priority: major Milestone: undecided
Component: apps/browser Version: 0.9.40
Keywords: Cc: idk
Parent Tickets: #2527 Sensitive: no

Description

If you install noscript plugin in I2P Browser , and check as well Tor Browser Bundle there are differences , because Noscript has direct effect on TBB preferences while in I2P Browser has only the plugin level effect (same as normal firefox)

This is as well effecting Browser Security Level options (about:preferences#privacy) , as in TBB when you change it from safe → safer → safest it has direct effect as well on Noscript behavior. While in I2P Browser its meaningless because it has no direct effect.

Solutions:

  • Either fix I2P Browser and make it behave the same way as TBB
  • Or Remove Security Level option because it has no effect on the browser

(Check the uploaded image)

Subtickets

Attachments (1)

browsererror5.png (85.0 KB) - added by anonymous maybe 4 months ago.

Download all attachments as: .zip

Change History (3)

Changed 4 months ago by anonymous maybe

Attachment: browsererror5.png added

comment:1 Changed 4 months ago by Meeh

Yea correct, the Security Level you mention there is something I've yet to implement for us in our i2pbutton, I know torbutton has it. They also has another javascript file which the filename has caught my attention (not yet had time to read the file content) named " noscript-control.js" found here: https://gitweb.torproject.org/torbutton.git/tree/src/modules

In terms of security level it's also a file in the last link named "security-prefs.js" which I assume has relation to this, and also this https://gitweb.torproject.org/torbutton.git/tree/src/chrome/locale/en-US/securityLevel.properties

comment:2 Changed 7 weeks ago by Meeh

Sensitive: unset

The https://github.com/mikalv/i2pbutton/blob/master/src/modules/noscript-control.js file has been added to i2pbutton and should be shipped with the next version.

Note: See TracTickets for help on using tickets.