Firefox3/Security Review Template - Revision history

Lakrits at 17:44, 1 October 2014

2014-10-01T17:44:45Z

← Older revision		Revision as of 17:44, 1 October 2014
Line 44:		Line 44:

	== Review comments ==		== Review comments ==


			[[Category:Wikipage templates]]

Dveditz at 00:48, 18 November 2010

2010-11-18T00:48:10Z

← Older revision		Revision as of 00:48, 18 November 2010
Line 2:		Line 2:
	''Describe the goals and objectives of the feature here.''		''Describe the goals and objectives of the feature here.''

	;Background links		Background links
	* feature-tracking bug links		* feature-tracking bug links
	* specs or design docs		* specs or design docs

Jesse at 00:11, 4 December 2008

2008-12-04T00:11:29Z

← Older revision		Revision as of 00:11, 4 December 2008
Line 21:		Line 21:

	== Module interactions ==		== Module interactions ==
	* What other modules are used (REQUIRES in the makefile, interfaces)		* What other modules are used (REQUIRES in the makefile, interfaces)?

	== Data ==		== Data ==
	* What data is read or parsed by this feature		* What data is read or parsed by this feature?
	* What is the output of this feature		* What is the output of this feature?
	* What storage formats are used		* What storage formats are used?

	== Reliability ==		== Reliability ==

Jesse: /* Security and Privacy */

2008-12-04T00:10:11Z

Security and Privacy

← Older revision		Revision as of 00:10, 4 December 2008
Line 8:		Line 8:
	== Security and Privacy ==		== Security and Privacy ==
	* Is this feature a security feature? If it is, what security issues is it intended to resolve?		* Is this feature a security feature? If it is, what security issues is it intended to resolve?
	* What potential security issues in your feature have you already considered and ~~mitigated~~?		* What potential security issues in your feature have you already considered and addressed?
	* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?		* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?
	* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.		* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.

Jesse: /* Security and Privacy */

2008-12-04T00:09:02Z

Security and Privacy

← Older revision		Revision as of 00:09, 4 December 2008
Line 7:		Line 7:

	== Security and Privacy ==		== Security and Privacy ==
	* What security issues ~~do you address~~ in your ~~project~~?		* Is this feature a security feature? If it is, what security issues is it intended to resolve?
			* What potential security issues in your feature have you already considered and mitigated?
	* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?		* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?
	* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.		* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.

Dolske: /* Security and Privacy */ Add Private Browsing note.

2008-10-19T08:29:21Z

Security and Privacy: Add Private Browsing note.

← Older revision		Revision as of 08:29, 19 October 2008
Line 10:		Line 10:
	* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?		* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?
	* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.		* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.
			* How are transitions in/out of Private Browsing mode handled?

	== Exported APIs ==		== Exported APIs ==

Dveditz at 19:25, 13 August 2008

2008-08-13T19:25:14Z

← Older revision		Revision as of 19:25, 13 August 2008
Line 41:		Line 41:
	* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?		* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?

	== ~~Post-review~~ comments ==		== Review comments ==

Dveditz at 18:51, 13 August 2008

2008-08-13T18:51:33Z

← Older revision		Revision as of 18:51, 13 August 2008
Line 1:		Line 1:

	== Overview ==		== Overview ==
	''Describe the goals and objectives of the feature here.''		''Describe the goals and objectives of the feature here.''
Line 37:		Line 36:
	* What are its on-going maintenance requirements (e.g. Web links, perishable data files)?		* What are its on-going maintenance requirements (e.g. Web links, perishable data files)?

	== Relationships to other projects ~~- are~~ there related projects in the community? ==		== Relationships to other projects ==
			Are there related projects in the community?
	* If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?		* If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?
	* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?		* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?

	== Post-review comments ==		== Post-review comments ==

Dveditz: Added placeholder section heading for review comments

2008-08-13T18:50:30Z

Added placeholder section heading for review comments

← Older revision		Revision as of 18:50, 13 August 2008
Line 1:		Line 1:
	~~__NOTOC__~~
	== Overview ==		== Overview ==
	''Describe the goals and objectives of the feature here.''		''Describe the goals and objectives of the feature here.''
Line 31:		Line 31:
	* Can its files be corrupted by failures? Does it clean up any locks/files after crashes?		* Can its files be corrupted by failures? Does it clean up any locks/files after crashes?

	== ~~configuration~~ ==		== Configuration ==
	* Can the end user configure settings, via a UI or about:config? Hidden prefs? Environment variables?		* Can the end user configure settings, via a UI or about:config? Hidden prefs? Environment variables?
	* Are there build options for developers? [#ifdefs, ac_add_options, etc.]		* Are there build options for developers? [#ifdefs, ac_add_options, etc.]
Line 40:		Line 40:
	* If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?		* If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?
	* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?		* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?

			== Post-review comments ==

Dveditz at 18:01, 23 July 2008

2008-07-23T18:01:18Z

← Older revision		Revision as of 18:01, 23 July 2008
Line 3:		Line 3:
	''Describe the goals and objectives of the feature here.''		''Describe the goals and objectives of the feature here.''

	Background links		;Background links
	* feature-tracking bug links		* feature-tracking bug links
	* specs or design docs		* specs or design docs


	== Security and Privacy ==		== Security and Privacy ==
Line 12:		Line 11:
	* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?		* Is system or subsystem security compromised in any way if your project's configuration files / prefs are corrupt or missing?
	* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.		* Include a thorough description of the security assumptions, capabilities and any potential risks (possible attack points) being introduced by your project.

	== Exported APIs ==		== Exported APIs ==
	* Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.)		* Please provide a table of exported interfaces (APIs, ABIs, protocols, UI, etc.)
Line 18:		Line 18:
	* Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully?		* Are the externally visible interfaces documented clearly enough for a non-Mozilla developer to use them successfully?
	* Does it change any existing interfaces?		* Does it change any existing interfaces?

			== Module interactions ==
			* What other modules are used (REQUIRES in the makefile, interfaces)

			== Data ==
			* What data is read or parsed by this feature
			* What is the output of this feature
			* What storage formats are used

	== Reliability ==		== Reliability ==
	* What failure modes or decision points are presented to the user?		* What failure modes or decision points are presented to the user?
	* Can its files be corrupted by failures? Does it clean up any locks/files after crashes?		* Can its files be corrupted by failures? Does it clean up any locks/files after crashes?

	~~== Installation, Upgrade/Downgrade/Sidegrade, and platform requirements ==~~
	* Does it equally support all Tier-1 platforms?
	* Does is have a hardware requirement (or increase minimum requirements)?
	* Does it require changes to the installer?
	* Does it impact updates?
	*list the expected behavior of this feature/function when Firefox is upgraded to a newer minor release, downgraded by installation of an earlier revision, or re-installed (same version)

	== configuration ==		== configuration ==
Line 34:		Line 36:
	* What ranges for the tunable are appropriate? How are they determined?		* What ranges for the tunable are appropriate? How are they determined?
	* What are its on-going maintenance requirements (e.g. Web links, perishable data files)?		* What are its on-going maintenance requirements (e.g. Web links, perishable data files)?

	== Relationships to other projects - are there related projects in the community? ==		== Relationships to other projects - are there related projects in the community? ==
	* If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?		* If so, what is the proposal's relationship to their work? Do you depend on others' work, or vice-versa?
	* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?		* Are you updating, copying or changing functional areas maintained by other groups? How are you coordinating and communicating with them? Do they "approve" of what you propose?