[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #27427 [Applications/Tor Browser]: [PATCH] Fix NoScript IPC for about:blank by whitelisting messages
#27427: [PATCH] Fix NoScript IPC for about:blank by whitelisting messages
-------------------------------------------------+-------------------------
Reporter: rustybird | Owner:
| arthuredelstein
Type: defect | Status:
| needs_review
Priority: Very High | Milestone:
Component: Applications/Tor Browser | Version:
Severity: Normal | Resolution:
Keywords: TorBrowserTeam201809R, | Actual Points:
tbb-8.0.1-can |
Parent ID: | Points:
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by ma1):
Replying to [comment:12 ma1]:
>
> Currently all the message metadata, also the name, is meant to be
confined in a ```__meta``` (notice the double underscore) object, which
always includes a "name" property, like
>
>
> {{{
> message.__meta = {
> name: "start",
> recipientInfo: {},
> //... possibly other properties in future
> }
> }}}
Of course, since this is an extensible mechanism which will allow us to
pack as much metadata as we need in one single place, it's meant to be
stable and not to change in any foreseeable future.
So, if the Tor Browser can start using __meta.name both on the receiving
and the sending end, I'm gonna get rid of the "legacy" redundant
_messageName property in one of the next releases.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27427#comment:13>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs