MozillaWiki - User contributions [en]

Modules/Other

2022-12-13T13:08:43Z

Dimi:

Firefox/Features/Form Autofill

2022-05-31T10:04:30Z

Dimi: Add See Also section

== Introduction ==

Form Autofill saves users time and effort when making online purchases by storing their personal information in a profile and automatically populating form fields when the user requires it.

Our objective is to increase user engagement, satisfaction and retention for frequent online shoppers (those who make an online purchase at least once per month). We believe this can be achieved by enabling users to complete forms and “check out” in e-commerce flows as quickly and securely as possible.

* Chat Channel: [https://matrix.to/#/!mwXGiacuROcLToavBH:mozilla.org/$vCratOt4HM-zjhXNVSlMNsf-Eibn0aeclVlUfED0N4Q?via=mozilla.org&via=t2bot.io #form-autofill]
* Mailing list: [mailto:autofill@lists.mozilla.org autofill@lists.mozilla.org]
* Bugzilla Component: [https://mzl.la/2zuJKyc Toolkit::Form Autofill] ([https://bugzilla.mozilla.org/enter_bug.cgi?product=Toolkit&component=Form%20Autofill new bug])
* Report website compatibility issues: [https://bugzilla.mozilla.org/show_bug.cgi?id=1405266 meta bug]
* Preferences: <code>extensions.formautofill.*</code>
* Code: [https://searchfox.org/mozilla-central/source/browser/extensions/formautofill/ browser/extensions/formautofill/] [https://firefox-source-docs.mozilla.org/browser/extensions/formautofill/docs/index.html Development documentation]
* Test pages: https://luke-chang.github.io/autofill-demo/

== Planning ==
* [https://docs.google.com/document/d/1Rk6SIH_O_wab1CsphHhuwmvT8gXCG-D0B0ki0R3dmC4/edit?ts=577b1d52#heading=h.ifofy8kjhyvh Product Requirements]
* UX Specs: [https://mozilla.invisionapp.com/share/AP8TFZ22G Address Autofill] [https://mozilla.invisionapp.com/share/7ZA4WEK9W Credit Card Autofill]
* [https://mozilla.invisionapp.com/share/MQ8J8K4CE#/screens/222029808 Old Visual Design Spec]
* [https://wiki.mozilla.org/QA/form_autofill Test plan]
* [https://docs.google.com/document/d/1QtyaF0rGqTtqxl1hcIhD-X_i1vNCPJO9Xo10CosdLCg/edit Meeting Notes]

=== Child Pages ===
{{Special:PrefixIndex/{{{1|{{FULLPAGENAME}}}}}/|stripprefix=1}}

== Feature Availability ==
=== Nightly ===
* Address Autofill: Available for all users in en-US builds (with US/CA/DE addresses [see <code>extensions.formautofill.addresses.supportedCountries</code>]).
* Credit Card Autofill: Available for all users in the following locales: US, CA, UK, DE, FR.

=== Beta ===
* Address Autofill: Available for users using an en-US build and located in the US with US addresses.
* Credit Card Autofill: Available for all users in the following locales: US, CA, UK, DE, FR.

=== Release ===
* Address Autofill: Rolled out to users using an en-US build and located in the US with US addresses.
* Credit Card Autofill: Available for all users in the following locales: US, CA, UK, DE, FR.

=== For Testing ===

If you would like to test these features but don't meet the conditions above, you can manually turn them on by modifying the following prefs via about:config and then '''restart Firefox'''.

* <code>extensions.formautofill.creditCards.supported</code>: on
* <code>extensions.formautofill.creditCards.enabled</code>: true
* <code>extensions.formautofill.creditCards.supportedCountries</code>: (add your country for GeoIP and the saved country)
* <code>extensions.formautofill.addresses.supported</code>: on
* <code>extensions.formautofill.addresses.enabled</code>: true
* <code>extensions.formautofill.addresses.supportedCountries</code>: (add your country for GeoIP and the saved country)

== Implementation ==
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=%22%5Bform%20autofill%22 All open bugs]
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20%22%5Bform%20autofill%22 All bugs]

Releases:
* [[Firefox/Features/Form Autofill/MVP]]
* [[Firefox/Features/Form Autofill/V2]]
* [[Firefox/Features/Form Autofill/Credit Cards | 2020 Credit card Autofill work]]

=== Platform Dependencies ===
* [https://bugzilla.mozilla.org/buglist.cgi?quicksearch=sw%3A%22%5Bform%20autofill%22%20-product:Firefox%20-product:Toolkit Bug List]
<bugzilla>
{
"quicksearch": "sw:'[form autofill:M' -product:Firefox -product:Toolkit",

"include_fields": "id, summary, status, resolution, assigned_to, whiteboard, cf_last_resolved",
"order": "resolution, cf_last_resolved"
}
</bugzilla>

[[Category:Firefox]]

== See Also ==
{{subpagelist}}

Firefox/Features/Form Autofill/Debugging

2022-05-31T10:01:44Z

Dimi: Created page with "= Gathering Debug Logs = [https://drive.google.com/file/d/1P94qZvQc3FkLiwhrmEYTSweCGt09ef97/preview Follow the instructions in this video] or the written steps in both section..."

= Gathering Debug Logs =
[https://drive.google.com/file/d/1P94qZvQc3FkLiwhrmEYTSweCGt09ef97/preview Follow the instructions in this video] or the written steps in both sections below.
== Enable Debug Logging ==

<ol>
<li>Enter "about:config" in the URL bar.</li>
<li>You may see a warning screen cautioning you about changing advanced preferences. Click the button to ignore the warning.</li>
<li>Set '''extensions.formautofill.loglevel''' pref to '''Debug'''
<li>
Make sure '''''all''''' of the following prefs are set to 'true'. (Find a pref by entering its name in the "Filter" box at the top of the page. Toggle its value by either clicking the ⇌ (Toggle) icon or double-clicking the line.)
<blockquote>devtools.browserconsole.contentMessages devtools.browserconsole.filter.error devtools.browserconsole.filter.warn devtools.browserconsole.filter.info devtools.browserconsole.filter.log devtools.browserconsole.filter.debug </blockquote>
</li>
</li>
<li>Restart Firefox</li>
</ol>

== View the Logging ==
# To view the logging, open the [https://developer.mozilla.org/en-US/docs/Tools/Browser_Console '''Browser''' Console] and/or Browser Content Toolbox (for logs related to in-page stuff) from the Tools → Web Developer menu. If you don't see these, follow the instructions on the MDN page to enable it.
#* '''Note that the above consoles are different than the Web Console that you use for regular web development.'''
# Make sure the log level toggles ("Errors", "Warnings", "Logs", …, "Debug") are all enabled in the Browser Console. "CSS" should ideally be disabled.
# Load the problematic web and reproduce the issue in in the browser. You might see messages in the Browser Console like:
FormAutofillContent: identifyAutofillFields: <nowiki>https://www.google.com</nowiki>
FormAutofillHandler: Creating new credit card section with flowId

To copy/save the logs, right-click in an open area of the console and choose "Save all Messages to File" or choose "Copy all Messages" depending on which you prefer. Include them as an '''attachment''' on your bug report, not in the body of a comment.

Modules/Other

2019-01-16T13:36:00Z

Dimi: update the source directory of URL Classifier

<noinclude>
'''Only module owners may edit this page.'''

They may:

* update any information about their module except the name of the owner
* add or remove sub-modules
* change the owner of a sub-module
* add emeritus owners or peers

Other changes, including changes of module owner or addition/removal of modules, must be agreed with the Module Ownership Module group, probably via a discussion in [https://www.mozilla.org/about/forums/#governance mozilla.governance].
</noinclude>
{{Module
|name=Add-on SDK
|description=The SDK and APIs that add-on developers can use to create extensions for Firefox and other applications
|owner=[mailto:gozala@mozilla.com Irakli Gozalishvili]
|peers=Alex Poirot, Brian Warner, Dietrich Ayala, Drew Willcoxon, Myk Melez, Will Bamberg
|forum=http://groups.google.com/group/mozilla-labs-jetpack
|source_dirs=https://github.com/mozilla/addon-sdk
|url=https://wiki.mozilla.org/Jetpack
|components=Add-on SDK
}}

{{Module
|name=Android Background Services
|description=Native Android services, including those bundled with Fennec: Sync, Product Announcements, Snippets, Updater, etc.
|owner=[mailto:rnewman@mozilla.com Richard Newman]
|peers=[mailto:nalexander@mozilla.com Nick Alexander], [mailto:liuche@mozilla.com Chenxia Liu], [mailto:jwillcox@mozilla.com James Willcox]
|forum=mozilla.dev.platforms.mobile
|source_dirs=https://github.com/mozilla-services/android-sync
|url=https://wiki.mozilla.org/Android/Services
|components=[https://bugzilla.mozilla.org/enter_bug.cgi?product=Android%20Background%20Services Android Background Services]
}}

{{Module
|name=BrowserID
|description=(a) Server Code, (b) Server deployment (during labs / prototype phase); and (c) *navigator.id.* API across Mozilla codebases (desktop, mobile, WebRT,..)
|owner=Ben Adida
|peers=Mike Hanson, Lloyd Hilaiel, Jonas Sicking, Jed Parsons
|source_dirs=
BrowserID server code: https://github.com/mozilla/browserid,
BrowserID server deployment: https://browserid.org, mozilla-central client code: toolkit/identity, dom/identity
|forum=https://lists.mozilla.org/listinfo/dev-identity
}}

{{Module
|name=ChatZilla
|description=IRC client
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:samuel@sieb.net Samuel Sieb], [mailto:silver@warwickcompsoc.co.uk James Ross]
|group=dev-apps-chatzilla
|source_dirs=extensions/irc/
|url=http://chatzilla.hacksrus.com/
|components=Other Applications::ChatZilla
}}

{{Module
|name=Composer
|description=Editor/Composer
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook], [mailto:smfr@smfr.org Simon Fraser], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-tech-editor
|source_dirs=editor/
|url=http://www.mozilla.org/editor
|components=Composer
}}

{{Module
|name=Content Services Infrastructure
|description=A set of data services that allow for content to be served and measured
|owner=[mailto:nanjiang@mozilla.com Nan Jiang]
|peers=[mailto:tspurway@mozilla.com Tim Spurway]
|peersemeritus=[mailto:dougt@mozilla.org Doug Turner], [mailto:olivier@olivieryiptong.com Olivier Yiptong]
|source_dirs=https://github.com/mozilla/onyx, https://github.com/mozilla/splice, https://github.com/mozilla/infernyx, https://github.com/mozilla/learnyx
|url=https://wiki.mozilla.org/Tiles
|components=Content Services
}}

{{Module
|name=DevTools
|description=Mozilla Developer Tools
|owner=[mailto:pbrosset@mozilla.com Patrick Brosset], [mailto:jwalker@mozilla.com Joe Walker]
|peers=[mailto:prouget@mozilla.com Paul Rouget], [mailto:past@mozilla.com Panagiotis Astithas], [mailto:mratcliffe@mozilla.com Mike Ratcliffe], [mailto:vporof@mozilla.com Victor Porof], [mailto:fitzgen@mozilla.com Nick Fitzgerald], [mailto:jblandy@mozilla.com Jim Blandy], [mailto:apoirot@mozilla.com Alex Poirot], [mailto:bgrinstead@mozilla.com Brian Grinstead], [mailto:jryans@gmail.com J. Ryan Stinnett], [mailto:janx@linux.com Jan Keromnes],[mailto:ntim.bugs@gmail.com Tim Nguyen], [mailto:jsantell@mozilla.com Jordan Santell], [mailto:ttromey@mozilla.com Tom Tromey], [mailto:jsnajdr@gmail.com Jaroslav Šnajdr], [mailto:lclark@mozilla.com Lin Clark], [mailto:jlaster@mozilla.com Jason Laster], [mailto:odvarko@gmail.com Jan 'Honza' Odvarko], [mailto:jdescottes@mozilla.com Julian Descottes], [mailto:gtatum@mozilla.com Greg Tatum], [mailto:gl@mozilla.com Gabriel Luong], [mailto:chevobbe.nicolas@gmail.com Nicolas Chevobbe], [mailto:ystartsev@mozilla.com Yulia Startsev], [mailto:sole@mozilla.com Soledad Penadés], [mailto:jwajsberg@mozilla.com Julien Wajsberg], [mailto:rcaliman@mozilla.com Razvan Caliman], [mailto:mtigley@mozilla.com Micah Tigley], [mailto:sfink@mozilla.com Steve Fink] (heapsnapshot code)
|peersemeritus=Mihai Șucan, Rob Campbell, Heather Arthur, Anton Kovalyov, Brandon Benvie, Eddy Bruel, James Long, Matteo Ferretti
|group=dev-developer-tools
|source_dirs=devtools
|url=https://wiki.mozilla.org/DevTools
|components=Firefox::Developer Tools
}}

{{Module
|name=Directory SDK
|description=Tools and SDKs for accessing LDAP Directories.
|owner=[mailto:mcs@pearlcrescent.com Mark C. Smith]
|peers=[mailto:anton.bobrov@sun.com Anton Bobrov], [mailto:richm@stanfordalumni.org Rich Megginson]
|group=dev-tech-ldap
|source_dirs=directory/
|url=http://www.mozilla.org/directory
|components=Directory
}}

{{Module
|name=DOM Inspector
|description=An extension that allows the user to inspect and edit the DOM of documents being displayed.
|owner=[mailto:sdwilsh@shawnwilsher.com Shawn Wilsher]
|peers=[mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=
|source_dirs=extensions/inspector/, layout/inspector/
|url=
|components=Other Applications::DOM Inspector
}}

{{Module
|name=Firefox for Android (Fennec)
|description=Mobile Web Browser
|owner=[mailto:snorp@mozilla.com James Willcox (:snorp)], [mailto:sebastian@mozilla.com Sebastian Kaspari (:sebastian) ]
|peers=[mailto:rnewman@mozilla.com Richard Newman (:rnewman)], [mailto:liuche@mozilla.com Chenxia Liu (:liuche)], [mailto:nalexander@mozilla.com Nick Alexander (:nalexander)], [mailto:mcomella@mozilla.com Michael Comella (:mcomella)], [mailto:gkruglov@mozilla.com Grisha Kruglov (:grisha)], [mailto:maliu@mozilla.com Max Liu (:maliu)], [mailto:nechen@mozilla.com Nevin Chen (:nechen)], [mailto:jchu@mozilla.com Julian Chu (:walkingice)]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=mobile/
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for Android
}}

{{Module
|name=Firefox for iOS (Fennec)
|description=Mobile Web Browser
|owner=[mailto:sarentz@mozilla.com Stefan Arentz]
|peers=[mailto:bnicolson@mozilla.com Brian Nicholson], [mailto:rnewman@mozilla.com Richard Newman], [mailto:sleroux@mozilla.com Steph Leroux], [mailto:etoop@mozilla.com Emily Toop], [mailto:jhugman@mozilla.com James Hugman]
|group=https://mail.mozilla.org/listinfo/mobile-firefox-dev
|source_dirs=https://github.com/mozilla/firefox-ios
|url=https://wiki.mozilla.org/Fennec
|components=Firefox for iOS
}}

{{Module
|name=Firefox Accounts
|description=The Firefox Accounts identity provider and the integration of user-data services tied to a Firefox account. Where this work overlaps with existing modules (FX front-end, FX Android front-end, FXOS), design and code reviews from all relevant module owners will be required.
|owner=[mailto:rfkelly@mozilla.com Ryan Kelly]
|peers=[mailto:stomlinson@mozilla.com Shane Tomlinson], [mailto:vlad.filippov@gmail.com Vlad Filippov], [mailto:pbooth@mozilla.com Phil Booth], [mailto:vbudhram@mozilla.com Vijay Budhram]
|group=
|source_dirs=https://github.com/mozilla/fxa-auth-server, https://github.com/mozilla/fxa-content-server, https://github.com/mozilla/fxa-oauth-server, https://github.com/mozilla/fxa-profile-server, https://github.com/mozilla/browserid-verifier, https://github.com/mozilla/fxa-js-client
|mailing list=https://mail.mozilla.org/listinfo/dev-fxacct
|url=https://wiki.mozilla.org/Identity/FirefoxAccounts
}}

{{Module
|name=Firefox for Metro
|description=Touch-screen-friendly browser for Windows
|owner=[mailto:jmathies@mozilla.com Jim Mathies], [mailto:mbrubeck@mozilla.com Matt Brubeck]
|peers=Allison Naaktgeboren, Brian Bondy, Marina Samuel, Mark Finkle, Rodrigo Silveira, Sam Foster, [https://mozillians.org/en-US/u/TimAbraldes/ Tim Abraldes]
|forum=https://mail.mozilla.org/listinfo/metro
|source_dirs=browser/metro
|url=https://wiki.mozilla.org/Firefox/Metro
|components=Firefox for Metro
}}

{{Module
|name=Loop aka Firefox Hello
|description=Voice and Video Collaboration System
|owner=[mailto:standard8@mozilla.com Mark Banner]
|peers=[mailto:abr@mozilla.com Adam Roach], [mailto:dmose@mozilla.com Dan Mosedale], [mailto:nperriault@mozilla.com Nicolas Perriault], [mailto:jaws@mozilla.com Jared Wein], [mailto:mdeboer@mozilla.com Michael de Boer], [mailto:tarek@mozilla.com Tarek Ziadé], [mailto:alexis@mozilla.com Alexis Metaireau], [mailto:natim@mozilla.com Rémy Hubscher], [mailto:mlepatre@mozilla.com Mathieu Leplatre], [mailto:fernando@mozilla.com Fernando Jiménez], [mailto:borja.salguero@telefonica.com Borja Salguero], [mailto:jaoo@tid.es Jose Antonio Olivera]
|forum=https://lists.mozilla.org/listinfo/dev-media (mozilla.dev.media)
|source_dirs=browser/components/loop, https://github.com/mozilla-services/loop-server, https://github.com/mozilla-b2g/firefoxos-loop-client
|url=https://wiki.mozilla.org/Loop
|components=Loop::Client, Loop::Server, Loop::General, Firefox OS::Gaia::Loop
}}

{{Module
|name=Mozilla Location Service (MLS)
|description=The Mozillla Location Service provides a service to position your device based on cell and wireless information.
|owner=[mailto:hschlichting@mozilla.com Hanno Schlichting]
|peers=
|peersemeritus=Victor Ng (2013-2014), Graydon Hoare (2014)
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/ichnaea
|url=https://location.services.mozilla.com
|components=Mozilla Services :: Location, https://github.com/mozilla/ichnaea/issues
}}

{{Module
|name=Mozilla Stumbler ("MozStumbler")
|description=The Mozilla Stumbler (MozStumbler) collects wireless network information for crowd-sourcing location positioning with Mozilla Location Service (MLS).
|owner=Garvan Keeley
|peers=[mailto:vng@mozilla.com Victor Ng], [mailto:dougt@mozilla.com Doug Turner], [mailto:cpeterson@mozilla.com Chris Peterson]
|forum=mozilla.dev.geolocation
|source_dirs=https://github.com/mozilla/MozStumbler
|url=https://location.services.mozilla.com
|components=https://github.com/mozilla/MozStumbler/issues
}}

{{Module
|name=Sync
|description=Firefox Sync client
|owner=[mailto:mconnor@mozilla.com Mike Connor]
|peers=[mailto:rnewman@mozilla.com Richard Newman], [mailto:gps@mozilla.com Gregory Szorc], Philipp von Weitershausen
|group=
|source_dirs=services/sync/
|url=https://wiki.mozilla.org/Services/Process/Code_Review
|components=Sync
}}

{{Module
|name=Party Tool
|description=PHP-based party tool used for Firefox Party
|owner=[mailto:rflint@ryanflint.com Ryan Flint]
|peers=Mike Morgan, [mailto:reed@reedloden.com Reed Loden]
|group=dev-apps-webtools
|source_dirs=webtools/partytool/
|url=http://wiki.mozilla.org/Webtools:PartyTool
|components=
}}

{{Module
|name=Penelope
|description=Eudora-like functionality and theme added to Thunderbird.
|owner=Jeff Beckley
|peers=
|group=
|source_dirs=penelope/
|url=https://wiki.mozilla.org/Penelope
|components=Penelope
}}

{{Module
|name=Popcorn.js
|description=Popcorn.js is an HTML5 media framework written in JavaScript for filmmakers, web developers, and anyone who wants to create time-based interactive media on the web.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:david.humphrey@senecacollege.ca David Humphrey], [mailto:scott.downe@gmail.com Scott Downe], [mailto:rick@bocoup.com Rick Waldron]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/popcorn-js/
|url=[http://www.popcornjs.org/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/63272-popcornjs/overview
}}

{{Module
|name=Popcorn Maker
|description=An SDK for authoring Popcorn projects.
|owner=[mailto:brett@mozillafoundation.org Brett Gaylor]
|peers=[mailto:ben@mozillafoundation.org Ben Moskowitz], [mailto:bobby@mozillafoundation.org Robert Richter]
|group=dev-popcorn
|source_dirs= https://github.com/mozilla/butter/
|url=[http://mozillapopcorn.org/popcorn-maker/ Project Home Page], [https://webmademovies.lighthouseapp.com/projects/65733-butter/overview Issue Tracker]
|components=https://webmademovies.lighthouseapp.com/projects/65733-butter/overview
}}

{{Module
|name=Rhino
|description=JavaScript interpreter/compiler implemented in Java
|owner=[mailto:greg@apigee.com Greg Brail]
|peers=[mailto:norrisboyd@gmail.com Norris Boyd], [mailto:szegedia@freemail.hu Attila Szegedi]
|group=dev-tech-js-engine
|source_dirs=js/rhino/
|url=http://www.mozilla.org/rhino/
|components=Rhino
}}

{{Module
|name=Screenshots
|description=Code relating to Screenshots functionality, both client (eg. Firefox) and server.
|owner=[mailto:ianb@mozilla.com Ian Bicking]
|peers=[mailto:jhirsch@mozilla.com Jared Hirsch], [mailto:bchen@mozilla.com Barry Chen], [mailto:pdahiya@mozilla.com Punam Dahiya]
|source_dirs=browser/extensions/screenshots
|components=Firefox::Screenshots, Cloud Services::Server: Screenshots
}}

{{Module
|name=Standalone Composer
|description=Standalone editor/composer based on mozilla/toolkit
|owner=[mailto:daniel@glazman.org Daniel Glazman]
|peers=[mailto:brade@comcast.net Kathy Brade], [mailto:neil@parkwaycc.co.uk Neil Rashbrook]
|group=dev-tech-editor,dev-apps-other
|source_dirs=composer/
|url=http://www.mozilla.org/editor/, http://www.nvu.com/, http://glazman.org/weblog/dotclear/index.php?Nvu
|components=
}}

{{Module
|name=URL Classifier
|description=Database and list-based classification of URL resources,
such as Tracking Protection and SafeBrowsing.
|owner=[mailto:dlee@mozilla.com Dimi Lee] (client), [mailto:lcrouch@mozilla.com Luke Crouch] (server)
|peers=[mailto:gcp@mozilla.com Gian-Carlo Pascutto] (client)
|ownersemeritus=François Marier
|peersemeritus=Henry Chang, Ryan Tilder
|group=mozilla.dev.platform
|source_dirs=toolkit/components/url-classifier, netwerk/url-classifier, https://github.com/mozilla-services/shavar
|url=
https://wiki.mozilla.org/Phishing_Protection, https://wiki.mozilla.org/Security/Tracking_protection, https://wiki.mozilla.org/Security/Application_Reputation
|components=
}}

{{Module
|name=Venkman
|description=JavaScript Debugger frontend
|owner=[mailto:rginda@hacksrus.com Rob Ginda]
|peers=[mailto:brendan@mozilla.org Brendan Eich], [mailto:gijskruitbosch@gmail.com Gijs Kruitbosch], [mailto:shaver@mozilla.org Mike Shaver], [mailto:silver@warwickcompsoc.co.uk James Ross], [mailto:timeless@mozdev.org Josh 'timeless' Soref]
|group=dev-apps-js-debugger
|source_dirs=extensions/venkman/
|url=http://www.mozilla.org/projects/venkman
http://www.hacksrus.com/~ginda/venkman/
|components=Other Applications::Venkman JS Debugger
}}

Security/Download Protection

2018-09-06T08:54:01Z

Dimi: update Telemetry section based on recent changes

== Description ==

This feature protects users against malware downloads. It is based on [[Security/Safe Browsing|Safe Browsing]].

See [[Security/Features/Application_Reputation_Design_Doc]] for implementation details.

== Prefs ==

* <tt>browser.safebrowsing.downloads.enabled</tt>: enables application reputation checks for downloaded files
* <tt>browser.safebrowsing.downloads.remote.enabled</tt>: enables remote lookups (requires the previous pref)
* <tt>browser.safebrowsing.downloads.remote.timeout_ms</tt>: timeout for the remote lookups
* <tt>browser.safebrowsing.downloads.remote.url</tt>: server endpoint for remote lookups
* <tt>browser.safebrowsing.malware.enabled</tt>: enables malware checks (required by application reputation)
* <tt>browser.safebrowsing.provider.google.lists</tt>: list of tables coming from the Google Safe Browsing service
* <tt>urlclassifier.downloadAllowTable</tt>: list of trusted certificates which suppress remote lookups (Windows-only)
* <tt>urlclassifier.downloadBlockTable</tt>: list of URLs serving malware binaries

== Engineering ==
Product/Component: '''Toolkit/Safe Browsing'''

* [https://bugzilla.mozilla.org/show_bug.cgi?id=662819 Tracking bug]

Most of the code lives in <tt>toolkit/components/downloads/ApplicationReputation.cpp</tt>. The lookup is requested from within [https://searchfox.org/mozilla-central/rev/d67ef71097da4d1aa344c9d9c672e49a7228e765/toolkit/components/jsdownloads/src/DownloadIntegration.jsm#468-482 toolkit/components/jsdownloads/src/DownloadIntegration.jsm].

Upstream list of file extensions:
* Shipped to Chrome via a "File Type Policies" Chrome extension (see <tt>chrome://components</tt>)
* [https://github.com/fmarier/safebrowsing-tools/blob/master/parse-filetypes.py Binary protobuf extractor]
* [https://cs.chromium.org/chromium/src/chrome/browser/resources/safe_browsing/download_file_types.asciipb Source protobuf]

=== Tests ===

Here are the download protection specific tests:

./mach test toolkit/components/reputationservice/test/

Also relevant are the [[Security/Safe_Browsing#Tests|Safe Browsing tests]].

== QA ==

* [http://testsafebrowsing.appspot.com Test page]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1250329 Meta QA bug for Safe Browsing]

To turn on debugging output, export the following environment variable:

MOZ_LOG_FILE=/tmp/apprep.log
MOZ_LOG="ApplicationReputation:5"

== Telemetry ==

'''Alerts are sent to [https://mail.mozilla.org/listinfo/safebrowsing-telemetry safebrowsing-telemetry@mozilla.org].'''
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2018-09-04&keys=__none__!__none__!__none__&max_channel_version=nightly%252F63&measure=APPLICATION_REPUTATION_BINARY&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2018-08-09&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_BINARY]: whether the file examined by download protection is a binary type
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2018-09-04&keys=__none__!__none__!__none__&max_channel_version=nightly%252F63&measure=APPLICATION_REPUTATION_BINARY_ARCHIVE&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2018-08-09&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_BINARY_ARCHIVE]: whether the binary file examined by download protection is dmg, rar or zip
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-06-06&keys=__none__!__none__!__none__&max_channel_version=nightly%252F49&measure=APPLICATION_REPUTATION_LOCAL&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_LOCAL]: results of the local checks (whitelist and blacklist)
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-08-20&keys=__none__!__none__!__none__&max_channel_version=nightly%252F51&measure=APPLICATION_REPUTATION_REMOTE_LOOKUP_TIMEOUT&min_channel_version=nightly%252F51&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-08-20&table=0&trim=1&use_submission_date=0 APPLICATION_REPUTATION_REMOTE_LOOKUP_TIMEOUT]: whether or not a client timed out while contacting the remote lookup server
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-06-06&keys=__none__!__none__!__none__&max_channel_version=nightly%252F49&measure=APPLICATION_REPUTATION_SERVER&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_SERVER]: whether the response from the remote server was valid, invalid (failed to parse as a protobuf) or failed in some other way
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2018-09-04&keys=__none__!__none__!__none__&max_channel_version=nightly%252F63&measure=APPLICATION_REPUTATION_SERVER_2&min_channel_version=null&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2018-08-09&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_SERVER_2]: a more detailed version of APPLICATION_REPUTATION_SERVER with network status
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-06-06&keys=__none__!__none__!__none__&max_channel_version=nightly%252F49&measure=APPLICATION_REPUTATION_SERVER_VERDICT&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_SERVER_VERDICT]: results (verdict) we got back from the remote server lookup
* [https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-06-06&keys=__none__!__none__!__none__&max_channel_version=nightly%252F49&measure=APPLICATION_REPUTATION_SHOULD_BLOCK&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 APPLICATION_REPUTATION_SHOULD_BLOCK]: whether or not a download has been blocked due to an application reputation lookup (local or remote)

== Documentation ==

* [[Security/Features/Application_Reputation_Design_Doc]]
* [https://mana.mozilla.org/wiki/display/FIREFOX/Application+Reputation Google API documentation] (internal access only)
* [http://www.internetsociety.org/doc/camp-content-agnostic-malware-protection Content-Agnostic Malware Protection] (paper describing how the whole system is implemented)
* [https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/safe_browsing/csd.proto&q=csd&sq=package:chromium&l=229 Chromium source code]
* [http://monica-at-mozilla.blogspot.co.nz/2014/07/download-files-more-safely-with-firefox.html Announcement blog post]

Security/Safe Browsing/V4 Implementation

2017-05-24T08:24:55Z

Dimi: /* M8 (2017/8/7) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
# '''browser.safebrowsing.temporary.take_v4_completion_result''' to '''true'''
you can turn on v4 feature (while v2 is still up and running).

If you want to get rid of v2 and use v4 only, you could also set the following preferences to empty string
# '''browser.safebrowsing.provider.google.lists''' to '''""'''
then you are ready to go!

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M5 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (2017/4/18) ==
=== Deliverables ===
# Caching
# Enable both V4 and V2 on Nightly 55

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M7 (2017/6/12) ==
=== Deliverables ===
# V4 only in Nightly 56

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

== M8 (2017/8/7) ==
=== Deliverables ===
# V4 only in Nightly 57
# V4 enabled but result ignored in Beta 56
# Plan for V4 integration tests

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M8 Dashboard for M8 bugs]

== M9 (2017/09/25) ==
=== Deliverables ===
# V4 only in Nightly 58 (riding the trains!)
# V4 enabled but result ignored on Beta 57

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M9 Dashboard for M9 bugs]

== M10 (2017/11/27) ==
=== Deliverables ===
# V4 only in Beta 58

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M10 Dashboard for M10 bugs]

== M11 (2018/01/16) ==
=== Deliverables ===
# V4 only in Release 58

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M11 Dashboard for M11 bugs]

Security/Safe Browsing/V4 Implementation

2017-02-15T07:02:36Z

Dimi: /* Try it on! */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
# '''browser.safebrowsing.temporary.take_v4_completion_result''' to '''true'''
you can turn on v4 feature (while v2 is still up and running).

If you want to get rid of v2 and use v4 only, you could also set the following preferences to empty string
# '''browser.safebrowsing.provider.google.lists''' to '''""'''
then you are ready to go!

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M5 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (2017/4/17) ==
=== Deliverables ===
# Caching
# Enable V4 and only use V4 on Nightly 56 !!!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M7 (2017/6/12) ==
=== Deliverables ===
# V4 enabled on Nightly 57
# V4 enabled but result ignored on Aurora 56

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

== M8 (2017/8/7) ==
=== Deliverables ===
# V4 enabled on Aurora 57(also in Nightly 58)
# V4 enabled but result ignored on Beta 56

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M8 Dashboard for M8 bugs]

== M9 (2017/10/2) ==
=== Deliverables ===
# V4 enabled on Beta 57(Aurora 58, Nightly 59)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M9 Dashboard for M9 bugs]

== M10 (2017/11/27) ==
=== Deliverables ===
# V4 enabled on Release 57 ｡:.ﾟヽ(*´∀`)ﾉﾟ.:｡

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M10 Dashboard for M10 bugs]

Security/Safe Browsing/V4 Implementation

2017-02-09T09:03:23Z

Dimi:

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
you can turn on v4 feature (while v2 is still up and running).

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M5 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (2017/4/17) ==
=== Deliverables ===
# Caching
# Enable V4 and only use V4 on Nightly 56 !!!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M7 (2017/6/12) ==
=== Deliverables ===
# V4 enabled on Nightly 57
# V4 not active on Aurora 56

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

== M8 (2017/8/7) ==
=== Deliverables ===
# V4 enabled on Aurora 57(also in Nightly 58)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M8 Dashboard for M8 bugs]

== M9 (2017/10/2) ==
=== Deliverables ===
# V4 enabled on Beta 57(Aurora 58, Nightly 59)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M9 Dashboard for M9 bugs]

== M10 (2017/11/27) ==
=== Deliverables ===
# V4 enabled on Release 57 ｡:.ﾟヽ(*´∀`)ﾉﾟ.:｡

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M10 Dashboard for M10 bugs]

Security/Safe Browsing/V4 Implementation

2017-02-09T09:01:06Z

Dimi:

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
you can turn on v4 feature (while v2 is still up and running).

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M5 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M55 Dashboard for M55 bugs]

== M6 (2017/4/17) ==
=== Deliverables ===
# Caching
# Enable V4 and only use V4 on Nightly 56 !!!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M56 Dashboard for M56 bugs]

== M7 (2017/6/12) ==
=== Deliverables ===
# V4 enabled on Nightly 57
# V4 not active on Aurora 56

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M57 Dashboard for M57 bugs]

== M8 (2017/8/7) ==
=== Deliverables ===
# V4 enabled on Aurora 57(also in Nightly 58)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M58 Dashboard for M58 bugs]

== M9 (2017/10/2) ==
=== Deliverables ===
# V4 enabled on Beta 57(Aurora 58, Nightly 59)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M59 Dashboard for M59 bugs]

== M10 (2017/11/27) ==
=== Deliverables ===
# V4 enabled on Release 57 ｡:.ﾟヽ(*´∀`)ﾉﾟ.:｡

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M60 Dashboard for M60 bugs]

Security/Safe Browsing/V4 Implementation/Dashboard

2017-02-09T09:00:13Z

Dimi:

= Dashboard for SafeBrowsing v4 =

== M0 ==
<bugzilla>
{
"whiteboard": "#sbv4-m0",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M1 ==
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M2 ==
<bugzilla>
{
"whiteboard": "#sbv4-m2",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M3 ==
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M4 ==
<bugzilla>
{
"whiteboard": "#sbv4-m4",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M5 ==
<bugzilla>
{
"whiteboard": "#sbv4-m5",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M6 ==
<bugzilla>
{
"whiteboard": "#sbv4-m6",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M7 ==
<bugzilla>
{
"whiteboard": "#sbv4-m7",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

Security/Safe Browsing/V4 Implementation/Dashboard

2017-02-09T08:06:32Z

Dimi: /* M55 */

= Dashboard for SafeBrowsing v4 =

== M0 ==
<bugzilla>
{
"whiteboard": "#sbv4-m0",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M1 ==
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M2 ==
<bugzilla>
{
"whiteboard": "#sbv4-m2",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M3 ==
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M4 ==
<bugzilla>
{
"whiteboard": "#sbv4-m4",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M55 ==
<bugzilla>
{
"whiteboard": "#sbv4-m5",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M56 ==
<bugzilla>
{
"whiteboard": "#sbv4-m6",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M57 ==
<bugzilla>
{
"whiteboard": "#sbv4-m7",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

Security/Safe Browsing/V4 Implementation/Dashboard

2017-02-09T08:05:59Z

Dimi: /* M55 */

= Dashboard for SafeBrowsing v4 =

== M0 ==
<bugzilla>
{
"whiteboard": "#sbv4-m0",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M1 ==
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M2 ==
<bugzilla>
{
"whiteboard": "#sbv4-m2",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M3 ==
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M4 ==
<bugzilla>
{
"whiteboard": "#sbv4-m4",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M55 ==
<bugzilla>
{
"whiteboard": "#sbv4-m5", "#sbv4-m55"
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M56 ==
<bugzilla>
{
"whiteboard": "#sbv4-m6",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M57 ==
<bugzilla>
{
"whiteboard": "#sbv4-m7",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

Security/Safe Browsing/V4 Implementation

2017-02-09T07:02:17Z

Dimi:

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
you can turn on v4 feature (while v2 is still up and running).

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M55 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M55 Dashboard for M55 bugs]

== M56 (2017/4/17) ==
=== Deliverables ===
# Caching
# Enable V4 and only use V4 on Nightly 56 !!!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M56 Dashboard for M56 bugs]

== M57 (2017/6/12) ==
=== Deliverables ===
# V4 enabled on Nightly 57
# V4 not active on Aurora 56

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M57 Dashboard for M57 bugs]

== M58 (2017/8/7) ==
=== Deliverables ===
# V4 enabled on Aurora 57(also in Nightly 58)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M58 Dashboard for M58 bugs]

== M59 (2017/10/2) ==
=== Deliverables ===
# V4 enabled on Beta 57(Aurora 58, Nightly 59)

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M59 Dashboard for M59 bugs]

== M60 (2017/11/27) ==
=== Deliverables ===
# V4 enabled on Release 57 ｡:.ﾟヽ(*´∀`)ﾉﾟ.:｡

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M60 Dashboard for M60 bugs]

Security/Safe Browsing/V4 Implementation

2017-02-09T06:51:45Z

Dimi: /* M6 (Deadline TBD) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
you can turn on v4 feature (while v2 is still up and running).

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M55 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M55 Dashboard for M55 bugs]

== M56 (2017/4/17) ==
=== Deliverables ===
# Caching
# Enable V4 and only use V4 on nightly !!!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M56 Dashboard for M56 bugs]

== M7 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

Security/Safe Browsing/V4 Implementation/Dashboard

2017-02-09T06:47:13Z

Dimi:

= Dashboard for SafeBrowsing v4 =

== M0 ==
<bugzilla>
{
"whiteboard": "#sbv4-m0",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M1 ==
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M2 ==
<bugzilla>
{
"whiteboard": "#sbv4-m2",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M3 ==
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M4 ==
<bugzilla>
{
"whiteboard": "#sbv4-m4",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M55 ==
<bugzilla>
{
"whiteboard": "#sbv4-m5",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M56 ==
<bugzilla>
{
"whiteboard": "#sbv4-m6",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M57 ==
<bugzilla>
{
"whiteboard": "#sbv4-m7",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

Security/Safe Browsing/V4 Implementation

2017-02-09T06:45:23Z

Dimi: /* M5 (Deadline TBD) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Try it on! =
V4 has been function ready (but pref'ed off) since Bug 1312339 was resolved. By changing preferences
# '''urlclassifier.malwareTable''' to '''goog-phish-shavar,goog-phish-proto,test-phish-simple'''
# '''urlclassifier.phishTable''' to '''goog-malware-shavar,goog-malware-proto,goog-unwanted-shavar,goog-unwanted-proto,test-malware-simple,test-unwanted-simple'''
# '''browser.safebrowsing.provider.google4.gethashURL''' to '''https://safebrowsing.googleapis.com/v4/fullHashes:find?$ct=application/x-protobuf&key=%GOOGLE_API_KEY%'''
you can turn on v4 feature (while v2 is still up and running).

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M55 (2017/3/6) ==
=== Deliverables ===
# Enable v4 completion on nightly but ignore the result
# Add V4 table for Download protection.
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M55 Dashboard for M55 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Fennec
# Download protection
# Make v2 testcases can also test v4

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M7 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

Security/Safe Browsing/V4 Implementation/Dashboard

2016-12-14T00:54:41Z

Dimi:

Security/Safe Browsing/V4 Implementation/Dashboard

2016-12-14T00:53:59Z

Dimi:

= Dashboard for SafeBrowsing v4 =

== M0 ==
<bugzilla>
{
"whiteboard": "#sbv4-m0",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M1 ==
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M2 ==
<bugzilla>
{
"whiteboard": "#sbv4-m2",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M3 ==
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M4 ==
<bugzilla>
{
"whiteboard": "#sbv4-m4",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M5 ==
<bugzilla>
{
"whiteboard": "#sbv4-m5",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

== M6 ==
<bugzilla>
{
"whiteboard": "#sbv4-m6",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}

== M7 ==
<bugzilla>
{
"whiteboard": "#sbv4-m7",
"include_fields": "id, summary, priority, status, resolution, assigned_to",
"order": "status, assigned_to"
}
</bugzilla>

Security/Safe Browsing/V4 Implementation

2016-12-14T00:50:20Z

Dimi:

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (2017/1/23) ==
=== Deliverables ===
# Enable update by default
# Fix crashes and regressions

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Fennec
# Download protection
# Make v2 testcases can also test v4

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M7 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

Security/Safe Browsing/V4 Implementation

2016-12-14T00:46:37Z

Dimi: /* M7(Deadline TBD) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Fennec
# Download protection
# Make v2 testcases can also test v4

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M7 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M7 Dashboard for M7 bugs]

Security/Safe Browsing/V4 Implementation

2016-12-14T00:46:17Z

Dimi: /* M5(Deadline TBD) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Fennec
# Download protection
# Make v2 testcases can also test v4

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

Security/Safe Browsing/V4 Implementation

2016-12-14T00:45:27Z

Dimi: /* M5 (Deadline TBD) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''goog-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Fennec
# Download protection
# Make v2 testcases can also test v4

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

Security/Safe Browsing/V4 Implementation

2016-10-21T07:23:52Z

Dimi: /* Deliverables */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''googpub-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M2 Dashboard for M2 bugs]

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Anything else

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

Security/Safe Browsing/V4 Implementation

2016-10-21T07:23:05Z

Dimi: /* M6 (Deadline TBD) */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''googpub-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Anything else

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M6 Dashboard for M6 bugs]

Security/Safe Browsing/V4 Implementation

2016-10-21T07:22:37Z

Dimi: /* Bugs */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''googpub-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Anything else

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

Security/Safe Browsing/V4 Implementation

2016-10-21T07:20:15Z

Dimi: /* Bugs */

= Quick Links =
* [[Security/Safe_Browsing/V4_Implementation/Dashboard|Dashboard]]
* [https://bugzilla.mozilla.org/showdependencytree.cgi?id=1167038&hide_resolved=1 Bug Dependency Tree]

= Introduction =
Safe Browsing v4 is designed to reduce network bandwidth and disk storage (mainly for mobile devices). The usage of partial URL hashes (aka prefixes) and complete hashes remains the same but the way we get those prefixes and complete hashes is changed. The update and hash completion API will be based on protobuf and content compression (in additional to HTTP compression) is introduced. For further information, see https://developers.google.com/safe-browsing/v4 (The public specification is not complete. For example, the protobuf is not mentioned.)

= Design and Implementation =
To have v2 and v4 run in parallel, we must carefully refactor some core components like '''ListManager''' and '''HashCompleter'''. Instead of having a master preference to switch between v2 and v4, we take the "table name driven" approach. The plan is to add a separate provider called '''google4''', which owns v4 tables: '''goog-phish-proto''', '''goog-unwanted-proto''' and '''goog-malware-proto'''. The suffix "-proto" indicates that the table should be updated and completed via protobuf. Besides, the new provider google4 has its own '''updateURL''' and '''gethashURL'''. You can consider '''google4''' yet another provider like '''mozilla'''.

When '''ListManager''' and '''HashCompleter''' (and any other related components like ProtocolParser) sees table names suffixed by "-proto", they would behave differently. For example, in '''listmanager.js''', while making update request for table '''goog-phish-proto''', ''nsIUrlClassifier.makeUpdateRequestV4'' will be called to build a v4 specific request. (See {{Bug|1264885}} and {{Bug|1275507}} for more information.)

= Using custom API key =
We are required to have a API key to access google services like geolocation and safe browsing. The nightly/beta/aurora/release Firefox builds will have a proper API key associated with mozilla. However, if you are using the Firefox built on your own, the API key will be substituted with "no-google-api-key", which is apparently not available. There are a couple of ways to use a working API key for Safe Browsing. The most recommended way is to prepare a key file and add the path to mozconfig:

# Obtain a Safe Browsing google API key from https://console.developers.google.com
#* If you don't know how to get a API key, buy hchang@mozilla.com a beer and ask him :p
# Create a key file which only contains the API key.
# Add "ac_add_options --with-google-api-keyfile=/path/to/your/keyfile" to mozconfig
# Rebuild and check if config.status has something like 'MOZ_GOOGLE_API_KEY': b'AIzaSooxxxxoxoxoxoxooxx'

= Milestones =

== M0 (2016/7/31) ==
=== Deliverables ===
# Send v4 update request on time
# Parse v4 update response but not store to disk
# Use v4 request backoff settings
# v2 will still be up and running

=== Notes ===
# v4 table download/update will be opt-in.
# To test M0 features, modify the following preferences:
#* '''urlclassifier.malwareTable''' ==> Add ''goog-malware-proto'' and ''goog-unwanted-proto''
#* '''urlclassifier.phishTable''' ==> Add ''googpub-phish-proto''

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M0 Dashboard for M0 bugs]

== M1 (2016/9/30) ==
=== Deliverables ===
# Store v4 tables to disk (including fixed and variable length prefixes)
# Store table states
# Split v4 tables to different directory per provider

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M1 Dashboard for M1 bugs]

=== Workweek in Vancouver ===
# Etherpad: https://public.etherpad-mozilla.org/p/sbv4yvr

== M2 (TBC, maybe 10/15) ==
The intention of M2 is to push the date where we "enable v4 list update on nightly by default" to two weeks later because we have identified some issues and lacks in M0 and M1 in Vancouver SBv4 work week. The target date is the end of second week in October.

=== Deliverables ===
# {{Bug|1305486}} to enable v4 table update on nightly by default (The most important!)
# {{Bug|1305567}} so that we won't get 400 error while doing list update. (landed)
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update. (under review)
# {{Bug|1305801}} to store v4 list to disk. (landed)
# {{Bug|1305484}} to store v4 list states to disk rather than preference.

== M3 (Right before Hawaii Workweek) ==
=== Deliverables ===
# Check v4 prefixes (in addition to v4) but ignore the result
# v2/v4 prefix matching consistency telemetry (e.g. v2/v4 should both 'have' or 'not have' certain URL hash)
## Be careful of the variable length prefixes: it's possible to get a 32-bit prefix match for <tt>foo.com</tt> in V2 and no match on V4 because that entry uses a 48-bit prefix instead

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M4 (Deadline TBD) ==
=== Deliverables ===
# Do and use v4 complete hashes (in addition to v2) but ignore the result
# v2/v4 URL hash matching consistency telemetry

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M3 Dashboard for M3 bugs]

== M5 (Deadline TBD) ==
=== Deliverables ===
# Cache
# Anything else

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M4 Dashboard for M4 bugs]

== M6 (Deadline TBD) ==
=== Deliverables ===
# Enable v4 by default!

=== Bugs ===
[https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation/Dashboard#M5 Dashboard for M5 bugs]

TPE CONNECTIVITY GROUP/2015-12-30

2015-12-30T02:29:14Z

Dimi: /* Dimi Lee */

= Meeting Info =
* Time: 2015/12/30 (Wed), 10:30 AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Thomas, Tim, Yoshi, Winnie

= Agenda =
# Weekly update

= Weekly Status Update =
== Dimi Lee ==
*{{Bug|1220950}}
**Adding tests for checking signed package should not share data with other package or web content. '''update code'''

*{{Bug|1188822}}
**Make service-workers/service-worker/fetch-request-resources.https.html pass. '''on-going'''

*{{Bug|1205288}}
**implement and test fetch spec changes for blob scheme with non-GET method. '''on-going'''

== Ethan Tseng ==

== Henry Chang ==

== Jonathan Hao ==

== Thomas Nguyen ==

== Tim Huang ==
* {{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Implemented the Upnp service discovery.
** Test and debug the functionality of Upnp service discovery.

* {{Bug|1230037}} - [OTA] [Wi-Fi] Separate Gecko and Gonk layers in Wi-Fi module
** Studying other modules that nearly support the future of gonk, e.g. bt, nfc.
** Contemplating that how we implement the future of gonk in Wifi.

== Winnie Sun ==

== Yoshi Huang ==
* {{Bug|1195930}} - Use origin in QuotaManager
** ongoing

= About MozAOSP Project =
* Slides of draft design
** https://docs.google.com/a/mozilla.com/presentation/d/1XLVXHEfGRY_zaZT3cmd0f678_e6SvjqqEXSznTe81_4/edit?usp=sharing

= Offsite Team Meeting =

TPE CONNECTIVITY GROUP/2015-12-30

2015-12-30T02:28:19Z

Dimi: /* Dimi Lee */

= Meeting Info =
* Time: 2015/12/30 (Wed), 10:30 AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Thomas, Tim, Yoshi, Winnie

= Agenda =
# Weekly update

= Weekly Status Update =
== Dimi Lee ==
*Bug 1220950
**Adding tests for checking signed package should not share data with other package or web content. '''update code'''

*Bug 1188822
**Make service-workers/service-worker/fetch-request-resources.https.html pass. '''on-going'''

*Bug 1205288
**implement and test fetch spec changes for blob scheme with non-GET method. '''on-going'''

== Ethan Tseng ==

== Henry Chang ==

== Jonathan Hao ==

== Thomas Nguyen ==

== Tim Huang ==
* {{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Implemented the Upnp service discovery.
** Test and debug the functionality of Upnp service discovery.

* {{Bug|1230037}} - [OTA] [Wi-Fi] Separate Gecko and Gonk layers in Wi-Fi module
** Studying other modules that nearly support the future of gonk, e.g. bt, nfc.
** Contemplating that how we implement the future of gonk in Wifi.

== Winnie Sun ==

== Yoshi Huang ==
* {{Bug|1195930}} - Use origin in QuotaManager
** ongoing

= About MozAOSP Project =
* Slides of draft design
** https://docs.google.com/a/mozilla.com/presentation/d/1XLVXHEfGRY_zaZT3cmd0f678_e6SvjqqEXSznTe81_4/edit?usp=sharing

= Offsite Team Meeting =

TPE CONNECTIVITY GROUP/2015-11-11

2015-11-11T02:39:31Z

Dimi: /* Dimi Lee */

= Meeting Info =
* Time: 2015/11/11 (Wed), 11AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Thomas, Tim, Yoshi, Winnie

= Agenda =
# Weekly status update
# Ari meeting at Mozlando and his Taipei visit (tentatively week of Jan 18)

= Weekly Status Update =
== Dimi Lee ==
* ''' Done & Working in Progress '''
# {{bug|1217367}} - Service workers update algorithm optimization. '''working'''
# {{bug|1207068}} - Implement ExtendableMessageEvent interface. '''land inbound'''
# Prepare sharing
- Smart Pointer : nsComPtr, RefPtr, nsAutoRef, UniquePtr, nsAutoPtr, nsCountedRef
- String : nsA(C)String, ns(C)String, nsAuto(C)String, nsDependentString, NS_LITERAL_STRING
- Warning and debug : NS_WARN_xxx NS_ENSURE_xxx, MOZ_ASSERT, ...
- Some MBTF utility : DebugOnly<> , Maybe<>, unused

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1220950}} - Adding tests for checking signed package should not share data with other package or web content. '''ni?paul'''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181390}} - fire install and activate events on service worker
# {{bug|1179064}} - Ensure that service worker code for signed packages is contained within the package

== Ethan Tseng ==

== Henry Chang ==

== Jonathan Hao ==

== Thomas Nguyen ==

== Tim Huang ==
*{{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** The implementation of the Bonjour service discovery is almost done for gecko.
** Sent a mail to Flyweb team to get in touch.
*{{Bug|1209654}} - [Cost Control] Data alert doesn't match reported usage
** The patch submitted and acquired R+.

== Winnie Sun ==

== Yoshi Huang ==

TPE CONNECTIVITY GROUP/2015-11-04

2015-11-04T03:04:10Z

Dimi: /* Dimi Lee */

= Meeting Info =
* Time: 2015/11/4 (Wed), 11AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Thomas, Tim, Yoshi, Winnie

= Agenda =
# Weekly status update

= Weekly Status Update =
== Dimi Lee ==
* ''' Done & Working in Progress '''
# {{bug|1214593}} - Remove service worker periodic updater. '''land'''
# {{bug|1220950}} - Adding tests for checking signed package should not share data with other package or web content. '''ni?paul'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181390}} - fire install and activate events on service worker
# {{bug|1179064}} - Ensure that service worker code for signed packages is contained within the package

== Ethan Tseng ==
* {{Bug|1217594}} - Cookies are lost when switching recent Nightlies
** {{Bug|1165267}} - Use OriginAttributes for nsCookieService ('''RESOLVED FIXED''')
** {{Bug|1220570}} - Potential cookie lost while downgrading from Aurora 44 to 43 (waiting for review)
** {{Bug|1220361}} - Add test case for Cookie database migration to new schema versions (patch in progress)
* {{Bug|1213827}} - CSP frame-ancestors breaks firefox os apps (I can reproduce it on Simulator in lastest Nightly, but not on desktop and device. Low priority for now)
* What I will do:
** Post 2.5 planning
** Training material
** Prepare for Orlando work week
** CSP bugs for NSec

== Henry Chang ==
Attend Web Summit.

== Jonathan Hao ==
Attend Web Summit.

== Thomas Nguyen ==
* {{Bug|1136512}} - Sony Z3C - nfcd should build with Z3 compatiable libnfc-nci library
** Extensive tests are required, pending
** {{Bug|1216473}} - [Aries] Mifare Classic is not fully supported in Aries, reading this kind of tag could disable RF occasionally

* {{Bug|976457}} - B2G NFC: API for supporting NFC_A tags
** Ongoing

* {{Bug|884478}} - NFC MiFare Ultralight Tag Support
** Ongoing

== Tim Huang ==
*{{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Referencing the service discovery of AOSP.
** Implementing ...

*{{Bug|1217717}} - Turn off airplane mode from settings, the wifi will be toggled on/off alternately
** Spent some time on finding the root cause of this problem.
** Opened a follow up {{Bug|1221068}} on providing enabling and disabling states in mozWifiManager for gaia.

== Winnie Sun ==

== Yoshi Huang ==
* {{Bug|1209162}} - Create OriginAttributes subtypes for different uses and define conversion routines between them
** Adding PrincipalOriginAttributes and DocShellOriginAttributes base on bholley's patch and jonas' comments.
** Now working on adding NeckoOriginAttributes.

TPE CONNECTIVITY GROUP/2015-10-21

2015-10-21T02:59:22Z

Dimi: /* Dimi Lee */

= Meeting Info =
* Time: 2015/10/21 (Wed), 11AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Thomas, Tim, Winnie, Yoshi

= Agenda =
# Weekly status update
# Feedback of stand-up meeting
# 2.5 blockers and root cause analysis
#* Dashboard: http://charts.mozilla.org/fxos/blockers.html#project=1.4,2.0,2.1,2.2,2.5
# Initiative of Orlando WW

= Weekly Status Update =
== Dimi Lee ==
* ''' Done & Working in Progress '''
# {{bug|1207727}} - Rework updating service workers according to the latest spec. '''writing testcases, address comment'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181390}} - fire install and activate events on service worker
# {{bug|1179064}} - Ensure that service worker code for signed packages is contained within the package

== Ethan Tseng ==

== Henry Chang ==

== Jonathan Hao ==

== Tim Huang ==
* {{Bug|1180257}} - mozAlarm fires alarms not at the expected time after a timezone change
** Marked as the duplicate of {{Bug|1181489}}

* {{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Studying WiFi Direct
*** Understood the service discovery request/response.
*** Studying the bonjour over service discovery.

== Thomas Nguyen ==
*{{Bug|1166210}} - Remove ServicesSetting changes listener in NfcContentHelper
**r+, Waiting try
*{{Bug|1201427}} - [Aries] NFC Tap-to-Pay dose not work
**Duplicated
*{{Bug|1136512}} - Sony Z3C - nfcd should build with Z3 compatiable libnfc-nci library
**Under review
*{{Bug|976457}} - B2G NFC: API for supporting NFC_A tags
**Working

== Winnie Sun ==

== Yoshi Huang ==

TPE CONNECTIVITY GROUP/2015-10-13

2015-10-14T02:12:24Z

Dimi: /* Thomas Nguyen */

= Meeting Info =
* Time: 2015/10/14 (Wed), 11AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Tim, Thomas, Winnie, Yoshi

= Agenda =
# Weekly status update
# Skip level meeting (10/27)
# 2015 Q4 goal setting
# 2.5 blockers and root cause analysis
# Meeting time

= Weekly Status Update =
== Dimi Lee ==
* ''' Done & Working in Progress '''
# {{bug|1207727}} - Rework updating service workers according to the latest spec. '''f+'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181390}} - fire install and activate events on service worker
# {{bug|1179064}} - Ensure that service worker code for signed packages is contained within the package

== Ethan Tseng ==
* New Security Model
*# Bug 1165267 - Use OriginAttributes for nsCookieService (landed last week)
*# Follow-up bug: Bug 1214071 - Add APIs get/removeCookiesForOriginAttributes() in nsICookieManager2.idl
*#* Request feedback on IDL change (Bobby Holley).
*# Bug 1179060 - Apply a default CSP for signed packaged content (feedback+ from Christoph)
*#* Christoph suggests to remove "unsafe-inline" from default policy for signed packages. (Paul: We cannot do this.)
*#* Require DOM peer as the reviewer (changes in nsDocument).
*#* Dig into deep logic of nsCSPContext and nsCSPParser for implementation plan.
* Review patch: Bug 1204846 - Amount of mobile data consumed regresses
* Management
*# Complete 2015 Q4 goal settings

== Henry Chang ==

== Jonathan Hao ==

== Tim Huang ==
*{{Bug|1204846}} - Amount of mobile data consumed regresses
** The patch has submitted.
*{{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Studying the Wifi Direct.
*{{Bug|1207066}} - [NetworkManager] implement nsINetworkInterface.activate()/deactivate() in wifi network interface
** Planning how to implement this feature.

== Thomas Nguyen ==
*{{Bug|1168704}} - rename setFocusApp in nsINfcContentHelper
**r+, Waiting try
*{{Bug|1166210}} - Remove ServicesSetting changes listener in NfcContentHelper
**Clarified and provided solution
*{{Bug|1201427}} - [Aries] NFC Tap-to-Pay dose not work
**Working

== Winnie Sun ==

== Yoshi Huang ==

= 2015 Q4 Goal Setting =
Also recorded in https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2015-Q4
== New Security Model ==
# '''Deliver a usable first prototype''' (Henry, Jonathan)
# '''Complete all features of NSec'''
#* Signing (Jonathan)
#* Verifying signatures (Henry, Jonathan)
#* CSP (Ethan)
#* Process isolation (Henry)
#* Installing and updating (Henry)
#* Service Workers (Dimi)
#* Origin and cookies jars (Yoshi, Ethan, ...)
# '''Enhancement of NSec'''
#* Add test cases (Henry, ...)
#* Add debugging tools (Henry, ...)
# '''Demonstrate NSec in Orlando work week'''

== Maintenance of Owned Modules ==
# '''Fix 2.5 blockers'''
#* Wi-Fi (Henry, Tim)
#* Alarm and system message (Henry, Tim)
#* NetworkStats (Ethan, Tim)
#* NFC (Dimi, Thomas)
#* RTSP (Jonathan)
# '''New features'''
#* Wi-Fi change to support NetworkManager enhancement (Tim)
#* Service Discovery of Wi-Fi Direct (Tim)
#* Polish NFC on features, emulator and test cases (Thomas)

== Long Term Plan ==
# Integrate New Security Model with Gaia (NGA?)
# TBD

TPE CONNECTIVITY GROUP/2015-10-13

2015-10-14T02:11:57Z

Dimi: /* Thomas Nguyen */

= Meeting Info =
* Time: 2015/10/14 (Wed), 11AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Tim, Thomas, Winnie, Yoshi

= Agenda =
# Weekly status update
# Skip level meeting (10/27)
# 2015 Q4 goal setting
# 2.5 blockers and root cause analysis
# Meeting time

= Weekly Status Update =
== Dimi Lee ==
* ''' Done & Working in Progress '''
# {{bug|1207727}} - Rework updating service workers according to the latest spec. '''f+'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181390}} - fire install and activate events on service worker
# {{bug|1179064}} - Ensure that service worker code for signed packages is contained within the package

== Ethan Tseng ==
* New Security Model
*# Bug 1165267 - Use OriginAttributes for nsCookieService (landed last week)
*# Follow-up bug: Bug 1214071 - Add APIs get/removeCookiesForOriginAttributes() in nsICookieManager2.idl
*#* Request feedback on IDL change (Bobby Holley).
*# Bug 1179060 - Apply a default CSP for signed packaged content (feedback+ from Christoph)
*#* Christoph suggests to remove "unsafe-inline" from default policy for signed packages. (Paul: We cannot do this.)
*#* Require DOM peer as the reviewer (changes in nsDocument).
*#* Dig into deep logic of nsCSPContext and nsCSPParser for implementation plan.
* Review patch: Bug 1204846 - Amount of mobile data consumed regresses
* Management
*# Complete 2015 Q4 goal settings

== Henry Chang ==

== Jonathan Hao ==

== Tim Huang ==
*{{Bug|1204846}} - Amount of mobile data consumed regresses
** The patch has submitted.
*{{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Studying the Wifi Direct.
*{{Bug|1207066}} - [NetworkManager] implement nsINetworkInterface.activate()/deactivate() in wifi network interface
** Planning how to implement this feature.

== Thomas Nguyen ==
*{{Bug|1168704}} - rename setFocusApp in nsINfcContentHelper
**waiting try
*{{Bug|1166210}} - Remove ServicesSetting changes listener in NfcContentHelper
**Clarified and provided solution
*{{Bug|1201427}} - [Aries] NFC Tap-to-Pay dose not work
**Working

== Winnie Sun ==

== Yoshi Huang ==

= 2015 Q4 Goal Setting =
Also recorded in https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2015-Q4
== New Security Model ==
# '''Deliver a usable first prototype''' (Henry, Jonathan)
# '''Complete all features of NSec'''
#* Signing (Jonathan)
#* Verifying signatures (Henry, Jonathan)
#* CSP (Ethan)
#* Process isolation (Henry)
#* Installing and updating (Henry)
#* Service Workers (Dimi)
#* Origin and cookies jars (Yoshi, Ethan, ...)
# '''Enhancement of NSec'''
#* Add test cases (Henry, ...)
#* Add debugging tools (Henry, ...)
# '''Demonstrate NSec in Orlando work week'''

== Maintenance of Owned Modules ==
# '''Fix 2.5 blockers'''
#* Wi-Fi (Henry, Tim)
#* Alarm and system message (Henry, Tim)
#* NetworkStats (Ethan, Tim)
#* NFC (Dimi, Thomas)
#* RTSP (Jonathan)
# '''New features'''
#* Wi-Fi change to support NetworkManager enhancement (Tim)
#* Service Discovery of Wi-Fi Direct (Tim)
#* Polish NFC on features, emulator and test cases (Thomas)

== Long Term Plan ==
# Integrate New Security Model with Gaia (NGA?)
# TBD

TPE CONNECTIVITY GROUP/2015-10-13

2015-10-14T02:09:06Z

Dimi: /* Dimi Lee */

= Meeting Info =
* Time: 2015/10/14 (Wed), 11AM
* Room: 5F, Santos
* Host: Ethan
* Attendees: Dimi, Henry, Jonathan, Tim, Thomas, Winnie, Yoshi

= Agenda =
# Weekly status update
# Skip level meeting (10/27)
# 2015 Q4 goal setting
# 2.5 blockers and root cause analysis
# Meeting time

= Weekly Status Update =
== Dimi Lee ==
* ''' Done & Working in Progress '''
# {{bug|1207727}} - Rework updating service workers according to the latest spec. '''f+'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181390}} - fire install and activate events on service worker
# {{bug|1179064}} - Ensure that service worker code for signed packages is contained within the package

== Ethan Tseng ==
* New Security Model
*# Bug 1165267 - Use OriginAttributes for nsCookieService (landed last week)
*# Follow-up bug: Bug 1214071 - Add APIs get/removeCookiesForOriginAttributes() in nsICookieManager2.idl
*#* Request feedback on IDL change (Bobby Holley).
*# Bug 1179060 - Apply a default CSP for signed packaged content (feedback+ from Christoph)
*#* Christoph suggests to remove "unsafe-inline" from default policy for signed packages. (Paul: We cannot do this.)
*#* Require DOM peer as the reviewer (changes in nsDocument).
*#* Dig into deep logic of nsCSPContext and nsCSPParser for implementation plan.
* Review patch: Bug 1204846 - Amount of mobile data consumed regresses
* Management
*# Complete 2015 Q4 goal settings

== Henry Chang ==

== Jonathan Hao ==

== Tim Huang ==
*{{Bug|1204846}} - Amount of mobile data consumed regresses
** The patch has submitted.
*{{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Studying the Wifi Direct.
*{{Bug|1207066}} - [NetworkManager] implement nsINetworkInterface.activate()/deactivate() in wifi network interface
** Planning how to implement this feature.

== Thomas Nguyen ==

== Winnie Sun ==

== Yoshi Huang ==

= 2015 Q4 Goal Setting =
Also recorded in https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2015-Q4
== New Security Model ==
# '''Deliver a usable first prototype''' (Henry, Jonathan)
# '''Complete all features of NSec'''
#* Signing (Jonathan)
#* Verifying signatures (Henry, Jonathan)
#* CSP (Ethan)
#* Process isolation (Henry)
#* Installing and updating (Henry)
#* Service Workers (Dimi)
#* Origin and cookies jars (Yoshi, Ethan, ...)
# '''Enhancement of NSec'''
#* Add test cases (Henry, ...)
#* Add debugging tools (Henry, ...)
# '''Demonstrate NSec in Orlando work week'''

== Maintenance of Owned Modules ==
# '''Fix 2.5 blockers'''
#* Wi-Fi (Henry, Tim)
#* Alarm and system message (Henry, Tim)
#* NetworkStats (Ethan, Tim)
#* NFC (Dimi, Thomas)
#* RTSP (Jonathan)
# '''New features'''
#* Wi-Fi change to support NetworkManager enhancement (Tim)
#* Service Discovery of Wi-Fi Direct (Tim)
#* Polish NFC on features, emulator and test cases (Thomas)

== Long Term Plan ==
# Integrate New Security Model with Gaia (NGA?)
# TBD

TPE CONNECTIVITY GROUP/2015-09-08

2015-09-08T02:57:41Z

Dimi: /* Dimi */

= 2.5 Blockers =
* Dashboard: http://charts.mozilla.org/fxos/blockers.html#project=1.4,2.0,2.1,2.2,2.5
* Wi-Fi blockers: https://goo.gl/hQugJj
* NFC blocker: https://goo.gl/xFY5bc

= Weekly Status Update =
== Dimi ==
* ''' Service Worker '''
# {{bug|1143717}} - Implement the ServiceWorkerMessageEvent interface . '''r+'''
# {{bug|1188822}} - Make service-workers/service-worker/fetch-request-resources.https.html pass. '''f?'''

* ''' New Security Model '''
# {{bug|1178526}} - Set appropriate origin attributes for signed packages. '''henry is testing it'''

* ''' NFC '''
# {{bug|1201427}} - [Aries] NFC Tap-to-Pay dose not work. '''working'''

== Ethan Tseng ==
* Bug 1165267 - Use OriginAttributes for nsCookieService

== Henry Chang ==

== Jonathan Hao ==

== Tim Huang ==

== Winnie Sun ==

== Yoshi Huang ==

== Aaron Wu (EPM) ==

TPE CONNECTIVITY GROUP/2015-09-08

2015-09-08T02:54:04Z

Dimi: /* Dimi Lee */

= 2.5 Blockers =
* Dashboard: http://charts.mozilla.org/fxos/blockers.html#project=1.4,2.0,2.1,2.2,2.5
* Wi-Fi blockers: https://goo.gl/hQugJj
* NFC blocker: https://goo.gl/xFY5bc

= Weekly Status Update =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1143717}} - Implement the ServiceWorkerMessageEvent interface . '''r+'''
# {{bug|1188822}} - Make service-workers/service-worker/fetch-request-resources.https.html pass. '''f?'''
# {{bug|1178526}} - Set appropriate origin attributes for signed packages. '''henry is testing it'''

== Ethan Tseng ==
* Bug 1165267 - Use OriginAttributes for nsCookieService

== Henry Chang ==

== Jonathan Hao ==

== Tim Huang ==

== Winnie Sun ==

== Yoshi Huang ==

== Aaron Wu (EPM) ==

TPE CONNECTIVITY GROUP/2015-07-14

2015-07-14T06:38:08Z

Dimi: /* Dimi */

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document. '''r?'''
# {{bug|1143717}} - Update MessageEvent.source to be compliant with the spec. '''working'''
# {{bug|1179191}} - When updating a sw via about:sw in b2g the parent process kills the settings app. '''working'''

# {{bug|1172823}} - [FLAME-L] NFC handover passive receive file fail. '''bt issue'''
# {{bug|1182154}} - [Aries-L][NFC] Transfer is not initiated for any file types. '''working'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1181389}} - check for full package update when doing service worker update
# {{bug|1181391}} - Preserve previous package until activate event
# {{bug|1181390}} - fire install and activate events on service worker
# ServiceWorker testcases.

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
** Performance Task Force
*** {{Bug|1159639}} - Implement API to add performance marker
**** Waiting for baku's feedback
*** {{Bug|1174640}} - [Notification] Improve usability/performance of Wifi icon
**** Discussed with Bobby, Alphan, aknow several times, and came up with a proposal.
** New Security Model
*** Studying
*** {{Bug|1178518}} - Support for verifying signed packages
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Winnie ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** {{Bug|1165214}} - DOMStorageManager should use cookieJar for ScopeKey and QuotaKey
** {{Bug|1165466}} - Fix up docshell and loadcontext inheriting code in nsIScriptSecurityManager to use originAttributes rather than explicitly querying appid/browser
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==

* 2.5 status and plan
** Wiki: https://wiki.mozilla.org/Firefox_OS/Releases/2.5
** Nomination :https://charts.paas.allizom.org/fxos/nominations.html#project=1.4,2.0,2.1,2.2,2.5
** Blockers:https://charts.paas.allizom.org/fxos/blockers.html#project=1.4,2.0,2.1,2.2,2.5
** No FL/FLR, please careful about feature quality. FC = Nov 2nd.

TPE CONNECTIVITY GROUP/2015-07-14

2015-07-14T06:32:51Z

Dimi: Created page with "= Discussion Topics = == Dimi == * ''' Done & Working in Progress ''' # {{bug|1170053}} - [Aries] Not able to share a picture using NFC. '''land''' # {{bug|1165774}} - [Flame..."

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1170053}} - [Aries] Not able to share a picture using NFC. '''land'''
# {{bug|1165774}} - [Flame L] NFC not working. '''land'''

# {{bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document. '''r?'''
# {{bug|1143717}} - Update MessageEvent.source to be compliant with the spec. '''f?'''

# {{bug|1168938}} - Memory safety bug in NetworkUtils::postTetherInterfaceList. '''r+'''
# {{bug|1168959}} - Memory-safety bugs in NetworkUtils.cpp generally. '''land'''

* ''' Review & Feedbacks '''

* ''' Pending '''

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
** Performance Task Force
*** {{Bug|1159639}} - Implement API to add performance marker
**** Waiting for baku's feedback
*** {{Bug|1174640}} - [Notification] Improve usability/performance of Wifi icon
**** Discussed with Bobby, Alphan, aknow several times, and came up with a proposal.
** New Security Model
*** Studying
*** {{Bug|1178518}} - Support for verifying signed packages
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Winnie ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** {{Bug|1165214}} - DOMStorageManager should use cookieJar for ScopeKey and QuotaKey
** {{Bug|1165466}} - Fix up docshell and loadcontext inheriting code in nsIScriptSecurityManager to use originAttributes rather than explicitly querying appid/browser
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==

* 2.5 status and plan
** Wiki: https://wiki.mozilla.org/Firefox_OS/Releases/2.5
** Nomination :https://charts.paas.allizom.org/fxos/nominations.html#project=1.4,2.0,2.1,2.2,2.5
** Blockers:https://charts.paas.allizom.org/fxos/blockers.html#project=1.4,2.0,2.1,2.2,2.5
** No FL/FLR, please careful about feature quality. FC = Nov 2nd.

TPE CONNECTIVITY GROUP/2015-07-07

2015-07-07T03:48:57Z

Dimi: /* Dimi */

TPE CONNECTIVITY GROUP/2015-07-07

2015-07-07T03:48:04Z

Dimi: Created page with "= Discussion Topics = == Dimi == * ''' Done & Working in Progress ''' * ''' Review & Feedbacks ''' * ''' Pending ''' * ''' Others ''' == Ethan == * ''' Done & Working in Pro..."

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Winnie ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Howie/Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP

2015-07-07T03:45:38Z

Dimi: /* Weekly Meeting */

= Team members =
* Engineering Manager: Vincent Chang (vchang)
* Yoshi Huang (allstarschh)
* Dimi Lee (dlee)
* Ethan Tseng (ettseng)
* Henry Chang (hchang)
* Jonathan Hao (jhao)

= Owned Modules =
* Wifi and Wifi Direct(chulee, hchang, vchang)
** https://wiki.mozilla.org/WIFI
* NFC (allstarschh)
** https://wiki.mozilla.org/Modules/All#Near_Field_Communication
* NFCD (dlee)
** https://github.com/mozilla-b2g/platform_system_nfcd
* RTSP (ethan, bechen, vchang)

= Feature List =
== Backlog for feature plans ==
* https://connectivity.etherpad.mozilla.org/2

== RTSP ==
* Owner: Ethan, Vincent
* {{bug|957937}}
* Wiki: https://wiki.mozilla.org/Networking/RTSP

== NFC ==
* Owner: Yoshi, Dimi
* {{bug|860906}}
* Wiki: https://wiki.mozilla.org/WebAPI/WebNFC
* Weekly meeting: MoPad https://taiwan.etherpad.mozilla.org/NFC-weekly
* Demo Video
** Contact sharing over NFC: https://www.youtube.com/watch?v=ymTotkFELkE
** NFC tag reading to URL; URL p2p sharing thru NFC: https://www.youtube.com/watch?v=Bcvm5KtRJFw
** First NFC contactless payment with Firefox OS Flame device: http://youtu.be/jzUs4KKx-KI
** NFC MIFARE Classic access control use case with Firefox OS Flame device: http://youtu.be/7ESLCjNSqN4

== WiFi EAP ==
* Owner: Chuck

== WISPr ==
* Owner: Henry, Chuck

== Wifi Direct ==
* Owner: Henry, Chuck
* {{bug|811635}}
* Wiki page: https://wiki.mozilla.org/B2G/Wifi_Direct

== Wifi Display ==
* Owner: Henry, Ethan, Vincent
* {{bug|925615}}
* Wiki page: https://wiki.mozilla.org/B2G/Wifi_Display

== Improvements ==

=== Per-APP Network Metering ===
* Owner: John

=== Per-APP Power Metering ===
* Owner: Borting, Vincent
* {{bug|854200}}

=== Resource Statistics API ===
* Owner: Borting, Vincent
* Objective:
** Provide resource statistics for Firefox OS devices
*** Network usage
*** Power consumption
** Provide resource control
** Integrate existing NetworkStats API and PowerStats API
* wiki: https://wiki.mozilla.org/WebAPI/ResourceStats
* Bugs:
** {{bug|951976}}

= Scrum =
* Sprint backlog per group
** Connectivity: https://wiki.mozilla.org/index.php?title=FirefoxOS/RIL_connectivity
** NFC: https://wiki.mozilla.org/index.php?title=FirefoxOS/NFC
= Feature b2g =
= Release Blockers =
== Based on Assignee ==
<bugzilla>
{
"cf_blocking_b2g":"+",
"cf_blocking_b2g_type":"contains",
"status":["UNCONFIRMED","NEW","ASSIGNED","REOPENED"],
"assigned_to":["vchang@mozilla.com","hchang@mozilla.com","allstars.chh@mozilla.com",
"dlee@mozilla.com","chulee@mozilla.com","ettseng@mozilla.com",
"jhao@mozilla.com"],
"include_fields": "id, assigned_to, summary, whiteboard, status, cf_blocking_b2g"
}
</bugzilla>

== Based on Components ==
<bugzilla>
{
"component":["WIFI", "NFC", "RTSP"],
"cf_blocking_b2g_type":"contains",
"cf_blocking_b2g": "+",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, assigned_to, summary, whiteboard, status, cf_blocking_b2g"
}
</bugzilla>

== Tracking Tools ==
* FFOS Dashboard: http://charts.mozilla.org/ffos/
* Branch/Landing information: https://wiki.mozilla.org/Release_Management/B2G_Landing
* Triage times and queries: https://wiki.mozilla.org/B2G/Triage
* Device Dashboard: http://joshwalker1026.github.io/charts/devices/dashboard.html#

= Waiting for triage ?=
== Based on Assignee ==
<bugzilla>
{
"cf_blocking_b2g":"?",
"cf_blocking_b2g_type":"contains",
"status":["UNCONFIRMED","NEW","ASSIGNED","REOPENED"],
"assigned_to":["vchang@mozilla.com","hchang@mozilla.com","allstars.chh@mozilla.com",
"dlee@mozilla.com","chulee@mozilla.com","ettseng@mozilla.com",
"jhao@mozilla.com"],
"include_fields": "id, assigned_to, summary, whiteboard, status, cf_blocking_b2g"
}
</bugzilla>

== Based on Components ==
<bugzilla>
{
"component":["WIFI", "NFC", "RTSP"],
"cf_blocking_b2g_type":"contains",
"cf_blocking_b2g": "?",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, assigned_to, summary, whiteboard, status, cf_blocking_b2g"
}
</bugzilla>

= Current Bugs =
== Yoshi ==
<bugzilla>
{
"assigned_to": "allstars.chh@mozilla.com",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, summary, depends_on, cf_blocking_b2g, cf_feature_b2g",
"changed_after": "30d",
"changed_before": "Now"
}
</bugzilla>

== Dimi Lee ==
<bugzilla>
{
"assigned_to": "dlee@mozilla.com",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, summary, depends_on, cf_blocking_b2g, cf_feature_b2g",
"changed_after": "30d",
"changed_before": "Now"
}
</bugzilla>

== Ethan Tseng ==
<bugzilla>
{
"assigned_to": "ettseng@mozilla.com ",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, summary, depends_on, cf_blocking_b2g, cf_feature_b2g",
"changed_after": "30d",
"changed_before": "Now"
}
</bugzilla>

== Henry Chang ==
<bugzilla>
{
"assigned_to": "hchang@mozilla.com ",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, summary, depends_on, cf_blocking_b2g, cf_feature_b2g",
"changed_after": "30d",
"changed_before": "Now"
}
</bugzilla>

== Joanthan Hao ==
<bugzilla>
{
"assigned_to": "jhao@mozilla.com",
"status" : ["NEW", "UNCONFIRMED", "ASSIGNED", "REOPENED"],
"include_fields": "id, summary, depends_on, cf_blocking_b2g, cf_feature_b2g",
"changed_after": "30d",
"changed_before": "Now"
}
</bugzilla>

= Team Goals =
{| class="fullwidth-table"
|-
! align="center" style="width: 25%;" | 2015
! align="center" style="width: 25%;" | 2016
|-
|
* [[TPE_CONNECTIVITY_GROUP/2015-Q2 | 2015-Q2]]
* [[TPE_CONNECTIVITY_GROUP/2015-Q3 | 2015-Q3]]
* [[TPE_CONNECTIVITY_GROUP/2015-Q4 | 2015-Q4]]
|
* [[TPE_CONNECTIVITY_GROUP/2016-Q1 | 2016-Q1]]
* [[TPE_CONNECTIVITY_GROUP/2016-Q2 | 2016-Q2]]
* [[TPE_CONNECTIVITY_GROUP/2016-Q3 | 2016-Q3]]
* [[TPE_CONNECTIVITY_GROUP/2016-Q4 | 2016-Q4]]
|}

= Weekly Meeting =
All team members: 15:00 p.m. every Tue.

{| class="fullwidth-table"
|-
! align="center" style="width: 20%;" | 2014 Q3
! align="center" style="width: 20%;" | 2014 Q4
! align="center" style="width: 20%;" | 2015 Q1
! align="center" style="width: 20%;" | 2015 Q2
! align="center" style="width: 20%;" | 2015 Q3
|-
|
* [[TPE_CONNECTIVITY_GROUP/2014-07-22 | 2014-07-22]]
* [[TPE_CONNECTIVITY_GROUP/2014-07-29 | 2014-07-29]]
* [[TPE_CONNECTIVITY_GROUP/2014-08-05 | 2014-08-05]]
* [[TPE_CONNECTIVITY_GROUP/2014-08-12 | 2014-08-12]]
* [[TPE_CONNECTIVITY_GROUP/2014-08-19 | 2014-08-19]]
* [[TPE_CONNECTIVITY_GROUP/2014-08-26 | 2014-08-26]]
* [[TPE_CONNECTIVITY_GROUP/2014-09-02 | 2014-09-02]]
* [[TPE_CONNECTIVITY_GROUP/2014-09-09 | 2014-09-09]]
* [[TPE_CONNECTIVITY_GROUP/2014-09-16 | 2014-09-16]]
* [[TPE_CONNECTIVITY_GROUP/2014-09-23 | 2014-09-23]]
* [[TPE_CONNECTIVITY_GROUP/2014-09-30 | 2014-09-30]]
|
* [[TPE_CONNECTIVITY_GROUP/2014-10-07 | 2014-10-07]]
* [[TPE_CONNECTIVITY_GROUP/2014-10-14 | 2014-10-14]]
* [[TPE_CONNECTIVITY_GROUP/2014-10-21 | 2014-10-21]]
* [[TPE_CONNECTIVITY_GROUP/2014-10-28 | 2014-10-28]]
* [[TPE_CONNECTIVITY_GROUP/2014-11-04 | 2014-11-04]]
* [[TPE_CONNECTIVITY_GROUP/2014-11-11 | 2014-11-11]]
* [[TPE_CONNECTIVITY_GROUP/2014-11-18 | 2014-11-18]]
* [[TPE_CONNECTIVITY_GROUP/2014-12-02 | 2014-12-02]]
* [[TPE_CONNECTIVITY_GROUP/2014-12-09 | 2014-12-09]]
* [[TPE_CONNECTIVITY_GROUP/2014-12-16 | 2014-12-16]]
* [[TPE_CONNECTIVITY_GROUP/2014-12-23 | 2014-12-23]]
* [[TPE_CONNECTIVITY_GROUP/2014-12-30 | 2014-12-30]]
|
* [[TPE_CONNECTIVITY_GROUP/2015-01-06 | 2015-01-06]]
* [[TPE_CONNECTIVITY_GROUP/2015-01-13 | 2015-01-13]]
* [[TPE_CONNECTIVITY_GROUP/2015-01-20 | 2015-01-20]]
* [[TPE_CONNECTIVITY_GROUP/2015-01-27 | 2015-01-27]]
* [[TPE_CONNECTIVITY_GROUP/2015-02-03 | 2015-02-03]]
* [[TPE_CONNECTIVITY_GROUP/2015-02-10 | 2015-02-10]]
* [[TPE_CONNECTIVITY_GROUP/2015-02-17 | 2015-02-17]]
* [[TPE_CONNECTIVITY_GROUP/2015-02-24 | 2015-02-24]]
* [[TPE_CONNECTIVITY_GROUP/2015-03-03 | 2015-03-03]]
* [[TPE_CONNECTIVITY_GROUP/2015-03-10 | 2015-03-10]]
* [[TPE_CONNECTIVITY_GROUP/2015-03-17 | 2015-03-17]]
* [[TPE_CONNECTIVITY_GROUP/2015-03-24 | 2015-03-24]]
* [[TPE_CONNECTIVITY_GROUP/2015-03-31 | 2015-03-31]]
|
* [[TPE_CONNECTIVITY_GROUP/2015-04-07 | 2015-04-07]]
* [[TPE_CONNECTIVITY_GROUP/2015-04-14 | 2015-04-14]]
* [[TPE_CONNECTIVITY_GROUP/2015-04-21 | 2015-04-21]]
* [[TPE_CONNECTIVITY_GROUP/2015-04-28 | 2015-04-28]]
* [[TPE_CONNECTIVITY_GROUP/2015-05-05 | 2015-05-05]]
* [[TPE_CONNECTIVITY_GROUP/2015-05-12 | 2015-05-12]]
* [[TPE_CONNECTIVITY_GROUP/2015-05-19 | 2015-05-19]]
* [[TPE_CONNECTIVITY_GROUP/2015-05-26 | 2015-05-26]]
* [[TPE_CONNECTIVITY_GROUP/2015-06-02 | 2015-06-02]]
* [[TPE_CONNECTIVITY_GROUP/2015-06-09 | 2015-06-09]]
* [[TPE_CONNECTIVITY_GROUP/2015-06-16 | 2015-06-16]]
* [[TPE_CONNECTIVITY_GROUP/2015-06-23 | 2015-06-23]]
* [[TPE_CONNECTIVITY_GROUP/2015-06-30 | 2015-06-30]]
|
* [[TPE_CONNECTIVITY_GROUP/2015-07-07 | 2015-07-07]]
* [[TPE_CONNECTIVITY_GROUP/2015-07-14 | 2015-07-14]]
* [[TPE_CONNECTIVITY_GROUP/2015-07-21 | 2015-07-21]]
* [[TPE_CONNECTIVITY_GROUP/2015-07-28 | 2015-07-28]]
* [[TPE_CONNECTIVITY_GROUP/2015-08-04 | 2015-08-04]]
* [[TPE_CONNECTIVITY_GROUP/2015-08-11 | 2015-08-11]]
* [[TPE_CONNECTIVITY_GROUP/2015-08-18 | 2015-08-18]]
* [[TPE_CONNECTIVITY_GROUP/2015-08-25 | 2015-08-25]]
* [[TPE_CONNECTIVITY_GROUP/2015-09-01 | 2015-09-01]]
* [[TPE_CONNECTIVITY_GROUP/2015-09-08 | 2015-09-08]]
* [[TPE_CONNECTIVITY_GROUP/2015-09-15 | 2015-09-15]]
* [[TPE_CONNECTIVITY_GROUP/2015-09-22 | 2015-09-22]]
* [[TPE_CONNECTIVITY_GROUP/2015-09-29 | 2015-09-29]]
|

TPE CONNECTIVITY GROUP/2015-06-30

2015-07-02T06:19:18Z

Dimi: /* Dimi */

TPE CONNECTIVITY GROUP/2015-Q2

2015-06-09T10:42:42Z

Dimi: /* Dimi */

= High level Goals for the team =
== Fix 2.2 blockers ==
* priority: p1
* https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2.2%2B

== Have the performance improvement plan and finish one performance improvement ==
* priority: p1
* Performance bugs - https://etherpad.mozilla.org/B2GPerfItems
* Performance task force
*# {{Bug|1159639}} - Implement API to add performance marker
* Performance plan
*# WiFi ?
*# RTSP ?
*# NFC ?

== Engage with new security model ==
* priority: p1
* Fix service worker bugs
*# {{Bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document
* Fix CSP bugs
*# {{Bug|959388}} - CSP 1.1: Workers have their own CSP policies, should not inherit from parent document ('''in progress''')
*# {{Bug|881509}} - Content Security Policy ShouldLoad and ShouldProcess do not use request principal (blocks 959388)
*# {{Bug|908933}} - CSP does not block cross-domain applets with object-src 'self
*# {{Bug|1030936}} - [CSP] remove fast-path for certified apps once the C++ backend is activated
*# Introduction to SOP, XSS and CSP - https://goo.gl/HFUysT

* Fix same origin and cookie jars bugs
*# https://github.com/allstarschh/b2gSecurity/blob/master/origin.md
*# Intro for the origin in new security model - http://bit.ly/1AbTqvQ
*# See depending bug {{Bug|1163254}}

== Emulator porting ==
* priority: p1
* Support marionette test for WiFi in emulator-kk
*# {{Bug|1001261}} - (emulator_wifi) B2G WiFi emulation on emulator-kk
* Support marionette test for NFC in emulator-kk
*# {{Bug|1030628}} - (b2g-nfc-emulator) [Meta] NFC emulator improvements
* Support automatically test for RTSP
*# {{Bug|998899}} - [META][RTSP] Build automated tests for RTSP feature

== Multiscreen ==
* priority: p2
* {{Bug|1116089}} - [Meta] Support "1 UA multi-screen" on FxOS

== NFC/WIFI/RTSP test case ==
* priority: p2

== A talk for tw all ==
* End of Stage 1 presentation for Necko study group

== RTSP client refactor ==
* priority: p2
* {{Bug|1138262}} - [META][RTSP] Refactor RTSP component

== WIFI related bugs ==
* Support EAP TLS
*#{{Bug|1151726}} - [Wifi] TEST-UNEXPECTED-ERROR|test_wifi_associate_WPA_EAP_TTLS.js
*# {{Bug|1163089}} - [Wifi] Marionette tests for Wifi WPA-EAP associate start to fail
*# {{Bug|1156204}} - [Settings] Add support for PKCS#12 files
*# {{Bug|998226}} - [wifi][Gaia] To support EAP-TLS and manage user certificate in WLAN setting
*# {{Bug|1163031}} - [Wifi] Provide more detail when certificate management API error

== Have a new HAL for emulator/New Gonk layer ==
* priority: p2
* meeting minutes - https://taiwan.etherpad.mozilla.org/1253
* New HAL interface task force

= Individual Goals and high level schedule =
== Yoshi ==
# Fix same origin and cookie jars bugs
# NFC

== Henry ==
# Landed gecko patches for Multi-Windows
#* Screen manager redesign for multiple display purpose.
#* Co-work with Shelly to land the primary gecko Bug 1138287.
#* Co-work with Luke to land gaia patches.
# Fixed WiFi bugs
#* Help investigate Z3C wifi issues.
# Review slides: https://docs.google.com/presentation/d/1kqP2iD2wyDrQO09vmRTaLduJCJPnp3U15odcmi33X4s/edit#slide=id.p

== Dimi ==
# https://docs.google.com/presentation/d/1Vuo1CQBNgmd21nFvLkj06vuuWR_9LLKqUK0BmcAEwH4/edit?usp=sharing

# Fix some service worker bugs
# Participate new security model architecture design discussion on server worker
# Fix NFC bugs

== Ethan ==
# Fix same origin and cookie jars bugs
# Fix CSP bugs
# RTSP

== Jonathan ==
* https://docs.google.com/a/mozilla.com/presentation/d/1tdhu753HBLDHfB9vgQvjT9sC3pF0CgTSgdt5mqN-Pkw/edit?usp=sharing
# RTSP
# Performance improvement

TPE CONNECTIVITY GROUP/2015-06-02

2015-06-02T02:17:22Z

Dimi: /* Dimi */

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1163556}} - [aries-l] NFC does not work in aries-l. '''working'''
# {{bug|1170053}} - [Aries] Not able to share a picture using NFC. '''working'''
# {{bug|1165774}} - [Flame L] NFC not working. '''working'''
# {{bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document. '''working on mochitest'''
# Prepare service worker slide

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1136512}} - Sony Z3C - nfcd should build with Z3 compatiable libnfc-nci library
# {{bug|1055959}} - [NFC] testNfcBadSessionIdError testcase fail. '''working'''

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** {{Bug|1168292}} - [NFC] System app unable to re-dispatch NFC event. '''v2.2+, landed on master'''
** {{Bug|1168300}} - Add cookieJar attribute and notify webapps-clear-cookiejar-data. '''r?'''
** {{Bug|1170097}} - Add originAttributesToCookieJar to ChromeUtils.jsm. '''r?'''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Howie/Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-05-26

2015-05-26T04:03:38Z

Dimi: /* Dimi */

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1163556}} - [aries-l] NFC does not work in aries-l. '''working'''
# {{bug|1165774}} - [Flame L] NFC not working. '''mozilla side is ok'''
# {{bug|1162836}} - Fix NFC marionette testcase fail. '''land'''
# {{bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document. '''report investigating result'''
# Prepare service worker slide

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1136512}} - Sony Z3C - nfcd should build with Z3 compatiable libnfc-nci library
# {{bug|1055959}} - [NFC] testNfcBadSessionIdError testcase fail. '''working'''

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Howie/Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-05-19

2015-05-19T02:55:47Z

Dimi: /* Dimi */

= Discussion Topics =
* 6/12 電影+老乾杯+三重 e7 club - http://www.e7club.com.tw/
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1163556}} - [aries-l] NFC does not work in aries-l. '''co-work with selin'''
# {{bug|1165774}} - [Flame L] NFC not working. '''co-work with viral'''
# {{bug|1162836}} - Fix NFC marionette testcase fail. '''working'''
# {{bug|1163952}} - nfcd should notify techlost if there is a tag or p2p connection and then nfc is turned off. '''won't fix'''
# {{bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document. '''working'''

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1136512}} - Sony Z3C - nfcd should build with Z3 compatiable libnfc-nci library
# {{bug|1055959}} - [NFC] testNfcBadSessionIdError testcase fail. '''working'''

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** Filed bugs depending on {{bug|1163254}}
** {{Bug|1165841}} - [NFC] Unable to share image from gallery, if this image was once previewed through notification. '''2.2+, ongoing'''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Howie/Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-05-12

2015-05-12T06:20:35Z

Dimi: /* Dimi */

= Discussion Topics =
* Q2 Team building - https://connectivity.etherpad.mozilla.org/15
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''land'''
# {{bug|1055959}} - [NFC] testNfcBadSessionIdError testcase fail. '''working'''
# {{bug|1162836}} - Fix NFC marionette testcase fail. '''working'''
# Help viral check flame-l NFC porting

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1158735}} - FetchEvent.client asserting in onFetch when there's no document
# {{bug|1136512}} - Sony Z3C - nfcd should build with Z3 compatiable libnfc-nci library
# {{bug|1163556}} - [aries-l] NFC does not work in aries-l

== Ethan ==
* ''' Done & Working in Progress '''
*# Contact with security team
*#* Christoph Kerschbaumer will be my mentor in CSP
*#* CSP bug triage @ Fri May 15, 2015 1:45am – 3:15am (CST)
*# {{Bug|959388}} - CSP 1.1: Workers may have their own CSP policies
*#* Depends on {{Bug|881509}} - Content Security Policy ShouldLoad and ShouldProcess do not use request principal
*#* Study Web Worker: a means for web content to run scripts in background threads
*# Trace CSP code: nsDocument::InitCSP()
*# Attend DOM study group: Focus management
*#* nsFocusManager is in charge of window and content focus management
*#* '''Cross-window shifting''' applies same-origin policy
* ''' Review & Feedbacks '''
* ''' Pending '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** List the changes needed in https://github.com/allstarschh/b2gSecurity/blob/master/origin.md
* ''' Review & Feedbacks '''
** {{Bug|1119152}} - [SecureElement] Implement SEReader.isSEPresent
** {{Bug|884594}} - Support NFC Access Control for Secure Element Access
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Howie/Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-05-05

2015-05-05T10:17:47Z

Dimi: /* Dimi */

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1160671}} - [Flame] Unable to turn on NFC. '''root cause found'''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''working'''
# Study service worker
* Trace ServiceWorkerManager.cpp, ServiceWorkerContainer.cpp, ServiceWorkerScriptCache.cpp
* Test service worker with host app, found following issues
*# Cannot launch hosted app with https
*# {{bug|1125961}}
*# 'SerializedLoadContext from child is null', fail in NeckoParent::GetValidatedAppInfo
*# Issue when run hosted app second time
*# crash when link to another html page

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1136512}} - [Lightsaber] Support NFC . '''checking if sony can support libnfc-nci github'''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''on-going'''

== Ethan ==
* ''' Done & Working in Progress '''
*# Study JavaScript security
*#* Review '''Same-Origin Policy (SOP)''' to clarify how SOP uses '''origin'''
*#* Relaxing SOP
*#*# Document.domain
*#*# Cross-Origin Resource Sharing (CORS)
*#*# Cross-document messaging: postMessage API
*# Study '''Cross-Site Scripting (XSS)''' attack
*#* Reflected XSS
*#* Persistent (Stored) XSS
*# Study '''Content Security Policy (CSP)'''
*#* CSP directive
*#** Script execution: script-src
*#** Plug-in content: object-src
*#** Stylesheets and fonts: style-src and font-src
*#** Passive multimedia: img-src and media-src
*#** Subframes: frame-src
*#** Default policy: default-src
*#* CSP key words
*#** none
*#** self
*#** data:
*#** unsafe-inline
*#** unsafe-eval
*# Start to trace CSP implementation in Firefox
*#* nsDocument::initCSP()
*#* nsCSPParser - which separates the CSP header into tokens and parses the CSP
*#* nsCSPUtils which holds the internal representation of the CSP
*#* nsCSPContext which is the interface through which CSP gets called
*# Start to play with CSP mochitest in Gecko
*#* dom/base/test/csp/test_csp_path_matching.html
*# Attend meeting on 5/5: New security model update hosted by Jean Gong
*# Coordinate Necko study group sessions

* ''' Review & Feedbacks '''
*# Help Jonathan on {{Bug|1158661}} - [FFOS2.0][Woodduck][HOMO]RSTP video in 720 H-264 Plays abnormal which can hear the audio only without the video shows

* ''' Pending '''

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|1154690}} - [Shinano][Aries] Sometimes it's hard to connect to some WiFi network
# {{Bug|1157657}} - [Wifi Direct] Periodically do p2p scan if in inactive state
# {{Bug|1160913}} - [Emulator][Wifi] Unable to connect to secure Wifi AP on emulator

# Multi-window
# {{Bug|1116089}} - [Meta] Support "1 UA multi-screen" on FxOS
#* https://wiki.mozilla.org/Firefox_OS/1UA_Multi-Screen

# {{Bug|1138287}} - Refactor GonkDisplay/nsWindow/hwc to support multiple displays
# {{Bug|1138288}} - Extend nsScreenManagerGonk to support multiple screens
#* Dedicated to redesign of nsScreenGonk/nsScreenManagerGonk/nsWindow

* ''' Pending '''
# {{Bug|1131632}} - [Wifi Direct][meta] Wifi Direct V3 refinement
# {{Bug|1141391}} - [Wifi Direct] Create Wifi Direct testing app

* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
** {{Bug|1158661}} - [FFOS2.0][Woodduck][HOMO]RSTP video in 720 H-264 Plays abnormal which can hear the audio only without the video shows.
*** It can play well on my flame, but CN's QA still has problems. I made a few patches, and finally we convinced our partner that the server is malfunctioning.
** Studying and planning about gecko performance marker interface.
*** I thought we could reuse the C++ implementation of WebIDL performance.mark(), but it seems that we don't necessarily have the window object. I will try to get the precise time from some API, and generate output of similar format so that Raptor can parse them.
** Studying DocShell
* ''' Review & Feedbacks '''
* ''' Pending '''
** {{Bug|1142383}} - [RTSP] More RTSP testcases ('''emulator black screen, try to use emulator-kk or x86 now''')
** Refactor planning
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** Discussed with Jonas with his cookie proposal, still need to confirm with him. http://bit.ly/1zf8VlV
* ''' Review & Feedbacks '''
** {{Bug|1119152}} - [SecureElement] Implement SEReader.isSEPresent
** {{Bug|884594}} - Support NFC Access Control for Secure Element Access
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==
* red-tai needs you
** https://mana.mozilla.org/wiki/display/PM/FxOS+-+Red-Tai+Project
** see overview of mozilla efforts.

* L porting status
** Flame
** z3c

== Aaron (EPM for Networking) ==
* 2.2 Status Update
** Code Complete (CC) - June 8th
** CC criteria: http://mzl.la/1J7RrYS
*** NEXUS-5-L 5.1 PVT build MTBF 13.77 hrs https://bugzil.la/1155490
*** FLAME-KK 4.4 PVT build MTBF 34.42 hrs.
** CSRR - May 8th
*** CAF-v2.2-metabug http://mzl.la/1ELeOXg

TPE CONNECTIVITY GROUP/2015-05-05

2015-05-05T10:12:00Z

Dimi: /* Dimi */

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1160671}} - [Flame] Unable to turn on NFC. '''root cause found'''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''working'''
# Study service worker
- Trace ServiceWorkerManager.cpp, ServiceWorkerContainer.cpp, ServiceWorkerScriptCache.cpp
- Test service worker with host app, found following issues
1. Cannot launch hosted app with https
2. bug 1125961
3. 'SerializedLoadContext from child is null', fail in NeckoParent::GetValidatedAppInfo
4. Issue when run hosted app second time
5. crash when link to another html page

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1136512}} - [Lightsaber] Support NFC . '''checking if sony can support libnfc-nci github'''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''on-going'''

== Ethan ==
* ''' Done & Working in Progress '''
*# Study JavaScript security
*#* Review '''Same-Origin Policy (SOP)''' to clarify how SOP uses '''origin'''
*#* Relaxing SOP
*#*# Document.domain
*#*# Cross-Origin Resource Sharing (CORS)
*#*# Cross-document messaging: postMessage API
*# Study '''Cross-Site Scripting (XSS)''' attack
*#* Reflected XSS
*#* Persistent (Stored) XSS
*# Study '''Content Security Policy (CSP)'''
*#* CSP directive
*#** Script execution: script-src
*#** Plug-in content: object-src
*#** Stylesheets and fonts: style-src and font-src
*#** Passive multimedia: img-src and media-src
*#** Subframes: frame-src
*#** Default policy: default-src
*#* CSP key words
*#** none
*#** self
*#** data:
*#** unsafe-inline
*#** unsafe-eval
*# Start to trace CSP implementation in Firefox
*#* nsDocument::initCSP()
*#* nsCSPParser - which separates the CSP header into tokens and parses the CSP
*#* nsCSPUtils which holds the internal representation of the CSP
*#* nsCSPContext which is the interface through which CSP gets called
*# Start to play with CSP mochitest in Gecko
*#* dom/base/test/csp/test_csp_path_matching.html
*# Attend meeting on 5/5: New security model update hosted by Jean Gong
*# Coordinate Necko study group sessions

* ''' Review & Feedbacks '''
*# Help Jonathan on {{Bug|1158661}} - [FFOS2.0][Woodduck][HOMO]RSTP video in 720 H-264 Plays abnormal which can hear the audio only without the video shows

* ''' Pending '''

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|1154690}} - [Shinano][Aries] Sometimes it's hard to connect to some WiFi network
# {{Bug|1157657}} - [Wifi Direct] Periodically do p2p scan if in inactive state
# {{Bug|1160913}} - [Emulator][Wifi] Unable to connect to secure Wifi AP on emulator

# Multi-window
# {{Bug|1116089}} - [Meta] Support "1 UA multi-screen" on FxOS
#* https://wiki.mozilla.org/Firefox_OS/1UA_Multi-Screen

# {{Bug|1138287}} - Refactor GonkDisplay/nsWindow/hwc to support multiple displays
# {{Bug|1138288}} - Extend nsScreenManagerGonk to support multiple screens
#* Dedicated to redesign of nsScreenGonk/nsScreenManagerGonk/nsWindow

* ''' Pending '''
# {{Bug|1131632}} - [Wifi Direct][meta] Wifi Direct V3 refinement
# {{Bug|1141391}} - [Wifi Direct] Create Wifi Direct testing app

* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
** {{Bug|1158661}} - [FFOS2.0][Woodduck][HOMO]RSTP video in 720 H-264 Plays abnormal which can hear the audio only without the video shows.
*** It can play well on my flame, but CN's QA still has problems. I made a few patches, and finally we convinced our partner that the server is malfunctioning.
** Studying and planning about gecko performance marker interface.
*** I thought we could reuse the C++ implementation of WebIDL performance.mark(), but it seems that we don't necessarily have the window object. I will try to get the precise time from some API, and generate output of similar format so that Raptor can parse them.
** Studying DocShell
* ''' Review & Feedbacks '''
* ''' Pending '''
** {{Bug|1142383}} - [RTSP] More RTSP testcases ('''emulator black screen, try to use emulator-kk or x86 now''')
** Refactor planning
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** Discussed with Jonas with his cookie proposal, still need to confirm with him. http://bit.ly/1zf8VlV
* ''' Review & Feedbacks '''
** {{Bug|1119152}} - [SecureElement] Implement SEReader.isSEPresent
** {{Bug|884594}} - Support NFC Access Control for Secure Element Access
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==
* red-tai needs you
** https://mana.mozilla.org/wiki/display/PM/FxOS+-+Red-Tai+Project
** see overview of mozilla efforts.

* L porting status
** Flame
** z3c

== Aaron (EPM for Networking) ==
* 2.2 Status Update
** Code Complete (CC) - June 8th
** CC criteria: http://mzl.la/1J7RrYS
*** NEXUS-5-L 5.1 PVT build MTBF 13.77 hrs https://bugzil.la/1155490
*** FLAME-KK 4.4 PVT build MTBF 34.42 hrs.
** CSRR - May 8th
*** CAF-v2.2-metabug http://mzl.la/1ELeOXg

TPE CONNECTIVITY GROUP/2015-05-05

2015-05-05T06:08:34Z

Dimi: /* Dimi */

= Discussion Topics =
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1160671}} - [Flame] Unable to turn on NFC. '''root cause found'''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''working'''
# Study service worker

* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1136512}} - [Lightsaber] Support NFC . '''checking if sony can support libnfc-nci github'''
# {{bug|964697}} - (emulator-NFC) B2G Emulator: NFC support in KK. '''on-going'''

== Ethan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Henry ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==