Closed Bug 963488 Opened 10 years ago Closed 10 years ago

Remove nfc-manager permission from the browser

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(blocking-b2g:1.4+)

RESOLVED DUPLICATE of bug 969217
blocking-b2g 1.4+

People

(Reporter: arroway, Assigned: gwagner)

References

Details

(Keywords: sec-low, Whiteboard: [systemsfe])

The browser app should have the nfc-manager permission, since it allows an app to receive broadcasted messages from Chrome such as "nfc-manager-send-file", "nfc-manager-tech-discovered". Only the System app should have the nfc-manager permission to handle these messages.
^^--- "The browser app should NOT have"
Epic fail with copy/paste :/, thx for the correction
Keywords: sec-low
 1.HandleVisibiltyChange() provides the Browser visibility information.
 Whenever enter into browser, document.hidden becomes false. Here I am adding the
 PeerHandler() to onpeerready.

 2.If we exit from the Browser, document.hidden becomes true, onpeerready becomes null.

 3.But the same time, while transfer URI data, Shrinking is enabled over the
 BrowserApplication,  document.hidden becomes true. I could not differentiate
 two different Normal exit and Shrink UI exit.
 
 Here I am doing additional checking along with "nfc-manager-tech-state"
saminath: Applications (even certified applications like the browser) should not have any need for nfc-manager permissions. NFC Manager is a System App function, that routes system level NFC messages and events to all other NFC enabled applications installed in the FirefoxOS platform.

The browser needs read or write permisison only in the applicaiton manifest to support nfc:

readonly or readwrite.

 "permissions": {
   "nfc": { "access": "readwrite" }
 }

https://wiki.mozilla.org/WebAPI/WebNFC#NDEF_P2P_Push_Example
blocking-b2g: --- → 1.4?
Garner, can you guys take this bug?
blocking-b2g: 1.4? → 1.4+
Flags: needinfo?(dgarnerlee)
Whiteboard: [systemsfe]
I can take a look if he is busy. Sami?

I'm looking at the new browser dependence on shared/js/util.js, which is a bug that isn't checked in yet.
Flags: needinfo?(dgarnerlee) → needinfo?(s.x.veerapandian)
Assignee: nobody → anygregor
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Flags: needinfo?(s.x.veerapandian)
You need to log in before you can comment on or make changes to this bug.