canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,776
edits
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{SecReviewInfo | {{SecReviewInfo | ||
|SecReview name=Windows 8 Metro Firefox | |SecReview name=Windows 8 Metro Firefox | ||
|SecReview target= | |SecReview target=<bugzilla> | ||
{ | |||
"id":"744928,771271,762344,747347" | |||
} | |||
</bugzilla> | |||
https://wiki.mozilla.org/Firefox/Windows_8_Integration | https://wiki.mozilla.org/Firefox/Windows_8_Integration | ||
https://wiki.mozilla.org/Firefox/Metro | https://wiki.mozilla.org/Firefox/Metro | ||
| Line 46: | Line 47: | ||
The user can switch tabs without the URL bar showing. | The user can switch tabs without the URL bar showing. | ||
Questions for security: | Questions for security: | ||
# Are there any times that a URL bar should be shown? | |||
# We don't currently have a lock icon or other indication that the user is on a secure site. This is not yet implemented but there is a bug posted for it. Is this a blocker for landing anywhere? | |||
# We don't currently have a notification that the user is on a partially secure site. Same questions. | |||
# We don't currently display certificate information about a secure site | |||
# Is there any places that you think the URL bar should be shown that I haven't mentioned (and possibly forgot to mention)? | |||
# Is it a concern that a malicious page could be designed to look like our URL bar and fake the user visiting different sites? Is there any way to prevent that? | |||
|SecReview threat brainstorming=* creating a window (if an attacker can somehow do it) might end up creating a window on the desktop (not in the Metro view) - we might create a widget but Metro will stop a Win32 window from showing up (IIUC) | |SecReview threat brainstorming=* creating a window (if an attacker can somehow do it) might end up creating a window on the desktop (not in the Metro view) - we might create a widget but Metro will stop a Win32 window from showing up (IIUC) | ||
* exploiting Metro process would lead to accessing WinRT APIs as well as win32 APIs, but WinRt APIs are usually more restricted than win32 apis anyways | * exploiting Metro process would lead to accessing WinRT APIs as well as win32 APIs, but WinRt APIs are usually more restricted than win32 apis anyways | ||
| Line 68: | Line 69: | ||
* dev team:: telemetry data on who is turning on prefs for addons/extenions | * dev team:: telemetry data on who is turning on prefs for addons/extenions | ||
* dev team:: review exthandler code | * dev team:: review exthandler code | ||
}} | }} | ||