Security/B2G/Browser API - Revision history

Lakrits at 16:48, 1 October 2014

2014-10-01T16:48:24Z

← Older revision		Revision as of 16:48, 1 October 2014
Line 7:		Line 7:
	\|SecTrackerFSA=no		\|SecTrackerFSA=no
	}}		}}
	[[Category:~~WebApi~~]]		[[Category:Web APIs]]

	This is a proposal for a Browser API and a new HTML element called "<browser>", which is similar to an iframe but allows the implementation of a fully featured web browser as a web app. As it currently stand, this is implemented as an attribute of the existing iframe tag (<iframe mozbrowser> however this may change eventually (bug		This is a proposal for a Browser API and a new HTML element called "<browser>", which is similar to an iframe but allows the implementation of a fully featured web browser as a web app. As it currently stand, this is implemented as an attribute of the existing iframe tag (<iframe mozbrowser> however this may change eventually (bug

Ptheriault at 02:17, 9 January 2013

2013-01-09T02:17:17Z

← Older revision		Revision as of 02:17, 9 January 2013
Line 9:		Line 9:
	[[Category:WebApi]]		[[Category:WebApi]]

			This is a proposal for a Browser API and a new HTML element called "<browser>", which is similar to an iframe but allows the implementation of a fully featured web browser as a web app. As it currently stand, this is implemented as an attribute of the existing iframe tag (<iframe mozbrowser> however this may change eventually (bug

	This is a proposal for a Browser API and a new HTML element called "<browser>", which is similar to an iframe but allows the implementation of a fully featured web browser as a web app.

	===Background===		===Background===
Line 27:		Line 25:
	Source:		Source:
	* http://mxr.mozilla.org/mozilla-central/source/dom/browser-element		* http://mxr.mozilla.org/mozilla-central/source/dom/browser-element

			===Architecture===
			At its core, the browser creates a special type of iframe

	===Data Flow Diagram===		===Data Flow Diagram===

Ptheriault at 01:04, 30 December 2012

2012-12-30T01:04:28Z

← Older revision		Revision as of 01:04, 30 December 2012
Line 8:		Line 8:
	}}		}}
	[[Category:WebApi]]		[[Category:WebApi]]



			This is a proposal for a Browser API and a new HTML element called "<browser>", which is similar to an iframe but allows the implementation of a fully featured web browser as a web app.

	===Background===		===Background===
	Goals		Goals
	* Provide support so that a Browser can be implemented as a Web App		* Provide support so that a Browser can be implemented as a Web App
	* ~~Implemented as new type of~~ iframe ~~which provides limited cross-origin access so that a page embedding this iframe can act~~ like a ~~web~~ browser.		* Makes the iframe appear like a top-level browser window to the embedded content
	* ~~Being implemented with a minimal set~~ of ~~APIs to~~		* Provide an API for parent page to manipulate and listen for changes of the embedded content's state.

	Specification:		Specification:
	* https://wiki.mozilla.org/WebAPI/BrowserAPI		* https://wiki.mozilla.org/WebAPI/BrowserAPI
Line 18:		Line 24:
	* https://bugzilla.mozilla.org/show_bug.cgi?id=693515		* https://bugzilla.mozilla.org/show_bug.cgi?id=693515
	Pages:		Pages:
			* https://developer.mozilla.org/en-US/docs/DOM/Using_the_Browser_API
	Source:		Source:
			* http://mxr.mozilla.org/mozilla-central/source/dom/browser-element

	===Data Flow Diagram===		===Data Flow Diagram===


	===Answered Questions===		===Answered Questions===
	===Open Questions===		===Open Questions===

Ptheriault at 07:32, 3 May 2012

2012-05-03T07:32:12Z

← Older revision		Revision as of 07:32, 3 May 2012
Line 43:		Line 43:
	** Modal dialogs in the browser frame must not block parent page		** Modal dialogs in the browser frame must not block parent page

	Untrusted web page content not segregated sufficiently from Web Apps Shared resources between untrusted content (i.e. page loaded in the mozbrowser) and the installed apps		*Untrusted web page content not segregated sufficiently from Web Apps
	** Cookies?		** Shared resources between untrusted content (i.e. page loaded in the mozbrowser) and the installed apps. Cookies?
	** Other Origin based resource access (local storage, Indexed DB)		** Other Origin based resource access (local storage, Indexed DB)
	** DoS attacks against the phone (mitigated by seperate process, but what about spamming functions which result in IPDL messages back to the B2G process? Especially for messages that result in costly functions)		** DoS attacks against the phone (mitigated by seperate process, but what about spamming functions which result in IPDL messages back to the B2G process? Especially for messages that result in costly functions)

Ptheriault at 07:29, 3 May 2012

2012-05-03T07:29:59Z

← Older revision		Revision as of 07:29, 3 May 2012
Line 47:		Line 47:
	** Other Origin based resource access (local storage, Indexed DB)		** Other Origin based resource access (local storage, Indexed DB)
	** DoS attacks against the phone (mitigated by seperate process, but what about spamming functions which result in IPDL messages back to the B2G process? Especially for messages that result in costly functions)		** DoS attacks against the phone (mitigated by seperate process, but what about spamming functions which result in IPDL messages back to the B2G process? Especially for messages that result in costly functions)
			** Permissions (what prevents a page loaded at sms.gaiamobile.org from getting SMS permissions?)

			*Untrusted page might gain access to create an <iframe mozbrowser>

	** Permissions (what prevents a page loaded at sms.gaiamobile.org from getting SMS permissions?)
	*Untrusted page might gain access to create an <iframe mozbrowser>
	*Access to the local device (this is probably a b2g wide question)		*Access to the local device (this is probably a b2g wide question)
	* file:// etc		** file:// etc
	* loopback address/network address?		** loopback address/network address?

	===Authorization Model===		===Authorization Model===

Ptheriault at 07:28, 3 May 2012

2012-05-03T07:28:54Z

← Older revision		Revision as of 07:28, 3 May 2012
Line 7:		Line 7:
	\|SecTrackerFSA=no		\|SecTrackerFSA=no
	}}		}}
	[Category:WebApi]]		[[Category:WebApi]]
	===Background===		===Background===
	Goals		Goals
Line 23:		Line 23:
	===Open Questions===		===Open Questions===
	*Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?		*Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?
	*~~Will there~~ be ~~any~~ tab ~~support for V1 (guessing no~~?)		*What will new window behavior be? (new tab?)
			*


	===Threat Model===		===Threat Model===
Line 42:		Line 41:
	*Frame related issues		*Frame related issues
	** Must handle frame-busting code correctly		** Must handle frame-busting code correctly
			** Modal dialogs in the browser frame must not block parent page

	Untrusted web page content not segregated sufficiently from Web Apps Shared resources between untrusted content (i.e. page loaded in the mozbrowser) and the installed apps		Untrusted web page content not segregated sufficiently from Web Apps Shared resources between untrusted content (i.e. page loaded in the mozbrowser) and the installed apps
	** Cookies?		** Cookies?
	** Other Origin based resource access (local storage, Indexed DB)		** Other Origin based resource access (local storage, Indexed DB)
			** DoS attacks against the phone (mitigated by seperate process, but what about spamming functions which result in IPDL messages back to the B2G process? Especially for messages that result in costly functions)


	** Permissions (what prevents a page loaded at sms.gaiamobile.org from getting SMS permissions?)		** Permissions (what prevents a page loaded at sms.gaiamobile.org from getting SMS permissions?)
	*Untrusted page might gain access to create an <iframe mozbrowser>		*Untrusted page might gain access to create an <iframe mozbrowser>

Ptheriault at 07:21, 3 May 2012

2012-05-03T07:21:12Z

← Older revision		Revision as of 07:21, 3 May 2012
Line 22:		Line 22:
	===Answered Questions===		===Answered Questions===
	===Open Questions===		===Open Questions===
	Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?		*Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?
			*Will there be any tab support for V1 (guessing no?)



	===Threat Model===		===Threat Model===
	Threat vectors:		Threat vectors:

	*Untrusted content escaping the <iframe mozbrowser> element		*Untrusted content escaping the <iframe mozbrowser> element
	**~~javascript~~ references to items not inside the iframe		**Javascript references to items not inside the iframe
	**~~attacking~~ local web apps through shared resources (are there any?)		**Attacking local web apps through shared resources (are there any?)
			**Causing the parent frame to navigate
			** Obtaining the permissions of the parent frame, ie being able to act like a browser
			***Impact is minimal is API is kept limited - not sure if this will be possible

	*Normal Browser Security controls weakened or not present		*Normal Browser Security controls weakened or not present
	** URL Bar behavior? (need to expose SSL information)		** URL Bar behavior? (need to expose SSL information)

	*Frame related issues		*Frame related issues
	** Must handle frame-busting code correctly		** Must handle frame-busting code correctly


	Untrusted web page content not segregated sufficiently from Web Apps Shared resources between untrusted content (i.e. page loaded in the mozbrowser) and the installed apps		Untrusted web page content not segregated sufficiently from Web Apps Shared resources between untrusted content (i.e. page loaded in the mozbrowser) and the installed apps
	** Cookies?		** Cookies?

Ptheriault at 07:16, 3 May 2012

2012-05-03T07:16:39Z

@@ Line 24: / Line 24: @@
 Will there be a separate cookie store for <iframe mozbrowser>, or will they be shared?
 ===Threat Model===
 ===Authorization Model===
 *Implicit: An app will need to granted the browser permission
 ===Implementation Requirements===
 *Many, TBD.

Ptheriault at 03:34, 3 May 2012

2012-05-03T03:34:04Z

@@ Line 7: / Line 7: @@
 |SecTrackerFSA=no
 }}
-https://bugzilla.mozilla.org/show_bug.cgi?id=693515
+[Category:WebApi]]
+===Background===
-https://etherpad.mozilla.org/BrowserAPISec
+Goals
+* Provide support so that a Browser can be implemented as a Web App
-[[Category:B2G]]
+* Implemented as new type of iframe which provides limited cross-origin access so that a page embedding this iframe can act like a web browser.

Ptheriault: Created page with "{{SecTracker |Component=Browser API }} {{SecTrackerItem |Sectrackerstatus=OK |Simpyn=No |SecTrackerFSA=no }} https://bugzilla.mozilla.org/show_bug.cgi?id=693515 https://etherp..."

2012-04-15T09:43:23Z

Created page with "{{SecTracker |Component=Browser API }} {{SecTrackerItem |Sectrackerstatus=OK |Simpyn=No |SecTrackerFSA=no }} https://bugzilla.mozilla.org/show_bug.cgi?id=693515 https://etherp..."

New page

{{SecTracker
|Component=Browser API
}}
{{SecTrackerItem
|Sectrackerstatus=OK
|Simpyn=No
|SecTrackerFSA=no
}}
https://bugzilla.mozilla.org/show_bug.cgi?id=693515

https://etherpad.mozilla.org/BrowserAPISec

[[Category:B2G]]