MozillaWiki - User contributions [en]

Security/Safe Browsing/V4 Implementation

2016-12-23T09:58:15Z

Hchang:

= 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 (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-10-05T06:17:54Z

Hchang: /* Use custom API key */

= 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#M2 Dashboard for M2 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]

Security/Safe Browsing/V4 Implementation

2016-10-05T06:17:29Z

Hchang:

= 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.)

= Use 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#M2 Dashboard for M2 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]

Security/Safe Browsing/V4 Implementation

2016-10-03T07:24:32Z

Hchang: /* M1.5 (TBC, maybe 10/15) */

= 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.)

= Use 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

== M1.5 (TBC, maybe 10/15) ==
The intention of M1.5 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. (landing)
# {{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. (landing)
# {{Bug|1305484}} to store v4 list states to disk rather than preference. (TBD)

As for the last one ({{Bug|1305484}}), the down side of NOT fixing it before enabling list update on nightly is that all the nightly user would have a full list update once we've changed to storing list states in disk (if we didn't deal with the annoying migration things).

== M2 (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#M2 Dashboard for M2 bugs]

== M3 (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]

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

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

== M5 (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-03T07:06:08Z

Hchang:

= 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.)

= Use 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

== M1.5 (TBC, maybe 10/15) ==
The intention of M1.5 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.
# {{Bug|1305581}} to examine checksum against the updated lists.
# {{Bug|1285848}} to support compressed list update.
# {{Bug|1305801}} to store list update to disk.

== M2 (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#M2 Dashboard for M2 bugs]

== M3 (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]

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

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

== M5 (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-03T07:02:11Z

Hchang:

= 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.)

= Use 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

== M1.5 == (TBC, maybe 10/15)
The intention of M1.5 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.
# Bug 1305581 to examine checksum against the updated lists.
# Bug 1285848 to support compressed list update.
# Bug 1305801 to store list update to disk.

== M2 (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#M2 Dashboard for M2 bugs]

== M3 (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]

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

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

== M5 (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-03T01:57:27Z

Hchang: /* Use custom API key */

= 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.)

= Use 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 (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#M2 Dashboard for M2 bugs]

== M3 (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]

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

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

== M5 (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-03T01:56:39Z

Hchang:

= 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.)

= Use 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 prepared 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 (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#M2 Dashboard for M2 bugs]

== M3 (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]

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

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

== M5 (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-03T01:30:02Z

Hchang: /* M1 (2016/9/30) */

Security/Safe Browsing/V4 Implementation

2016-09-22T22:40:26Z

Hchang: /* M1 (2016/9/30) */

Security/Safe Browsing/V4 Implementation

2016-07-18T10:04:10Z

Hchang: /* Design and Implementation */

= 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.)

= 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 ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

== M3 (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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

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

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

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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T09:59:26Z

Hchang: /* Design and Implementation */

= 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.)

= 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 ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

== M3 (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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

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

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

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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T09:09:02Z

Hchang:

= 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 =

= 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 ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

== M3 (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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

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

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

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

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

Security/Safe Browsing

2016-07-18T08:46:55Z

Hchang: /* History */ Added v4 history

Note: The Safe Browsing feature in Firefox has been renamed to Phishing Protection, but it's still known as Safe Browsing internally.

[[Security/Application Reputation|Download Protection]] and [[Security/Tracking protection|Tracking protection]] have their own separate pages.

= History =

[http://www.google.com/tools/firefox/safebrowsing/ Google Safe Browsing] was an anti-phishing extension released by Google on [http://labs.google.com/ labs.google.com] in December 2005. Google has released this extension to the Mozilla Foundation under MPL 1.1/GPL 2.0/LGPL 2.1 in order that it might be used as part of Firefox if desired. We've landed this change on the trunk as a global extension as of 7 March 2006. You can read the discussion that lead up to to its integration in https://bugzilla.mozilla.org/show_bug.cgi?id=329292

Google is migrating Safe Browsing to v4 protocol since 2015 and we are now working on integrating to our code base with a incremental approach. That is, we will be landing v4 patches progressively and leave v2 up and running until v4 is extensively tested. In other words, v2 and v4 will co-exist for a while to make sure Safe Browsing feature not broken. See https://wiki.mozilla.org/Security/Safe_Browsing/V4_Implementation to know the plans and milestones for v4 implementation.

= Prefs =

* <tt>browser.safebrowsing.blockedURIs.enabled</tt>: enable the plugin stability blocking (no override or UI)
* <tt>browser.safebrowsing.debug</tt>: show debugging info from the JavaScript list update code on the command line
* <tt>browser.safebrowsing.id</tt>: what SAFEBROWSING_ID in <tt>gethashURL</tt> and <tt>updateURL</tt> maps to
* <tt>browser.safebrowsing.malware.enabled</tt>: enable '''malware''' protection (includes '''unwanted''' as well)
* <tt>browser.safebrowsing.provider.google.gethashURL</tt>: server endpoint for completions of malware and phishing lists
* <tt>browser.safebrowsing.provider.google.lists</tt>: list of tables coming from the Google Safe Browsing service
* <tt>browser.safebrowsing.provider.google.reportURL</tt>: probably unused
* <tt>browser.safebrowsing.provider.google.updateURL</tt>: server endpoint for malware and phishing list updates
* <tt>browser.safebrowsing.provider.google.lastupdatetime</tt>: timestamp (in ms) of when the last list update happened.
* <tt>browser.safebrowsing.provider.google.nextupdatetime</tt>: timestamp (in ms) of when the list should next be downloaded.
* <tt>browser.safebrowsing.reportMalwareMistakeURL</tt>: destination for the "This isn't an attack site" button (after ignoring the interstitial warning)
* <tt>browser.safebrowsing.reportPhishMistakeURL</tt>: destination for the "This isn't a web forgery" button (after ignoring the interstitial warning)
* <tt>browser.safebrowsing.reportPhishURL</tt>: destination for the "Help | Report Web Forgery" menu item
* <tt>urlclassifier.blockedTable</tt>: list of tables to use for the plugin stability blocking
* <tt>urlclassifier.disallow_completions</tt>: list of tables for which we never call <tt>gethash</tt>
* <tt>urlclassifier.gethashnoise</tt>: the number of fake entries to add to any <tt>gethash</tt> calls
* <tt>urlclassifier.gethash.timeout_ms</tt>: the timeout after which gethash requests should be aborted
* <tt>urlclassifier.malwareTable</tt>: list of tables to use when looking for malware (they need to be named <tt>*-malware-*</tt> or <tt>*-unwanted-*</tt>)
* <tt>urlclassifier.max-complete-age</tt>
* <tt>urlclassifier.phishTable</tt>: list of tables to use when looking for phishing (they need to be named <tt>*-phish-*</tt>)

Firefox 49 and earlier:

* <tt>browser.safebrowsing.enabled</tt>: enable '''phishing''' protection

Firefox 50 and later:

* <tt>browser.safebrowsing.phishing.enabled</tt>: enable '''phishing''' protection

= Documentation =
* Safe Browsing Protocol [https://web.archive.org/web/20160422212049/https://developers.google.com/safe-browsing/developers_guide_v2 v2.2] and [https://developers.google.com/safe-browsing/v4/ v4]
* [[Phishing Protection: Design Documentation|Design Documentation]]
* [[Phishing Protection: Server Spec|Server Spec]]
* [[Phishing Protection: Client Spec|Client Spec]]
* [https://support.mozilla.org/en-US/kb/how-does-phishing-and-malware-protection-work SUMO]
* [https://feeding.cloud.geek.nz/posts/how-safe-browsing-works-in-firefox/ Overview of how Safe Browsing works in Firefox]

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

* [https://bugzilla.mozilla.org/show_bug.cgi?id=1149867 Tracking bug]
* The Firefox implementation is split into a few parts:
** <tt>browser/components/safebrowsing/</tt> (front-end tests)
** <tt>netwerk/base/nsChannelClassifier</tt>
** <tt>toolkit/components/url-classifier/</tt> (includes the list manager)
* Local store is in:
** <tt>~/.cache/mozilla/firefox/XXXX/safebrowsing/</tt> on Linux
** <tt>~/Library/Caches/Firefox/Profiles/XXXX/safebrowsing/</tt> on Mac
** <tt>C:\Users\XXXX\AppData\Local\mozilla\firefox\profiles\XXXX\safebrowsing\</tt> on Windows
* [https://github.com/mozilla/itisatrap itisatrap.org] test pages
* [https://people.mozilla.org/~fmarier/safebrowsing-dashboard/ Telemetry dashboard]

== Code walkthrough ==

Both [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/netwerk/base/nsBaseChannel.cpp#611 nsBaseChannel::Open()] and [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/netwerk/base/nsBaseChannel.cpp#672 nsBaseChannel::AsyncOpen()] ask for the channel to be [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/netwerk/base/nsBaseChannel.cpp#306 "classified"] by
[https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/netwerk/base/nsChannelClassifier.cpp#354 nsChannelClassifier]. There is also a [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/netwerk/protocol/http/nsHttpChannel.cpp#5185 local-only classification] that is requested by [[Security/Tracking protection|tracking protection]].

The classifier [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/toolkit/components/url-classifier/nsUrlClassifierDBService.cpp#173 determines the type of URL that it is] and then [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/toolkit/components/url-classifier/nsUrlClassifierDBService.cpp#988 returns the appropriate NS_ERROR code]. That causes the channel to be [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/netwerk/base/nsChannelClassifier.cpp?offset=200#646 cancelled with that error code].

When the [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/docshell/base/nsDocShell.cpp#7613 classification state of the page changes], the appropriate UI [https://dxr.mozilla.org/mozilla-central/rev/f8086bd3c84fc1a42c3625cf3cc2253f0a5e8cfd/docshell/base/nsDocShell.cpp#4854 is shown].

= QA =

* Test pages
** [http://itisatrap.org/firefox/its-an-attack.html Malware], [http://itisatrap.org/firefox/its-a-trap.html phishing], [http://itisatrap.org/firefox/unwanted.html unwanted software] and [http://itisatrap.org/firefox/forbidden.html forbidden] hard-coded test URLs
** [http://phishtank.com/ Phishtank] (real phishing sites)
** [http://testsafebrowsing.appspot.com Google test pages] (we don't implement: Clank Warnings, Client-side phishing detection, Bad IP Warnings)
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1250329 Meta QA bug]
* [https://www.google.com/transparencyreport/safebrowsing/diagnostic/index.html Info on why certain URLs are blocked]
* [https://github.com/fmarier/sbdbdump/blob/master/dump.py Script to dump the contents of the local store]
* [https://dxr.mozilla.org/mozilla-central/source/testing/firefox-ui/tests/functional/security UI tests (Marionette)]
* [https://hg.mozilla.org/qa/mozmill-tests/file/default/firefox/tests/remote/restartTests/testSafeBrowsing_initialDownload/test2.js Mozmill test for initial list download] (needs to be [https://bugzilla.mozilla.org/show_bug.cgi?id=1237396 ported to Marionette])

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

MOZ_LOG="UrlClassifierDbService:5,nsChannelClassifier:5,UrlClassifierProtocolParser:5,UrlClassifierStreamUpdater:5,UrlClassifierPrefixSet:5"

and also see the <tt>browser.safebrowsing.debug</tt> pref to see debugging output from the JS pieces of Safe Browsing.

= Telemetry =

* Performance
** [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=URLCLASSIFIER_CL_CHECK_TIME&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_CL_CHECK_TIME]: how long a Safe Browsing lookup took
** [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=URLCLASSIFIER_CL_UPDATE_TIME&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_CL_UPDATE_TIME]: how long table updates takes
** [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=URLCLASSIFIER_LOOKUP_TIME&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_LOOKUP_TIME]: time spent in the dbservice while doing a 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=URLCLASSIFIER_PS_CONSTRUCT_TIME&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_PS_CONSTRUCT_TIME]: time spent constructing a PrefixSet
** [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=URLCLASSIFIER_PS_FALLOCATE_TIME&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_PS_FALLOCATE_TIME]: time spent allocating a PrefixSet
** [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=URLCLASSIFIER_PS_FILELOAD_TIME&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_PS_FILELOAD_TIME]: time spent loading PrefixSet from disk
* Server-related
** [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=URLCLASSIFIER_COMPLETE_TIMEOUT&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_COMPLETE_TIMEOUT]: whether or not a client timed out while contacting the gethash 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=URLCLASSIFIER_COMPLETE_REMOTE_STATUS&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_COMPLETE_REMOTE_STATUS]: HTTP status code returned by the gethash 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=URLCLASSIFIER_UPDATE_REMOTE_STATUS&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_UPDATE_REMOTE_STATUS]: HTTP status code returned by the update server
* Database size
** [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=URLCLASSIFIER_LC_COMPLETIONS&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_LC_COMPLETIONS]: number of entries in the completion cache
** [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=URLCLASSIFIER_LC_PREFIXES&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-04-25&table=1&trim=1&use_submission_date=0 URLCLASSIFIER_LC_PREFIXES]: number of entries in the prefix cache

= Links =

* Google reporting forms:
** [https://www.google.com/safebrowsing/report_badware/ Malware]
** [https://www.google.com/safebrowsing/report_phish/ Phishing] -- [https://www.google.com/safebrowsing/report_phish/?tpl=mozilla Firefox-specific]
** [https://www.google.com/safebrowsing/report_error/ Phishing error] (false positive) -- [https://www.google.com/safebrowsing/report_error/?tpl=mozilla Firefox-specific]

Security/Safe Browsing/V4 Implementation

2016-07-18T08:27:02Z

Hchang: /* M0 (2016/7/31) */

= 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 ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

== M3 (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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

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

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

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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T07:52:33Z

Hchang:

= 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

=== Bugs ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

== M3 (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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m3",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

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

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

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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T07:46:28Z

Hchang: /* Bugs */

= 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

=== Bugs ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T07:42:41Z

Hchang: /* Bugs */

= 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

=== Bugs ===

<bugzilla>
{
"whiteboard": "#sbv4-m0",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id",
"resolution": ["FIXED", "WONTFIX", "DUPLICATE", "WORKSFORME", "INCOMPLETE"],
}
</bugzilla>

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T07:41:05Z

Hchang: /* Bugs */

= 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

=== Bugs ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

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

Security/Safe Browsing/V4 Implementation

2016-07-18T07:40:16Z

Hchang: /* Bugs */

= 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

=== Bugs ===

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

== 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 ===
<bugzilla>
{
"whiteboard": "#sbv4-m1",
"include_fields": "id, summary, status, assigned_to,resolution,",
"order": "bug_id"
}
</bugzilla>

== M2 (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

=== Bugs ===

Security/Safe Browsing/V4 Implementation

2016-07-18T07:39:20Z

Hchang: /* Bugs */

= 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

=== Bugs ===

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

== 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 ===

== M2 (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

=== Bugs ===

Security/Safe Browsing/V4 Implementation

2016-07-18T07:30:32Z

Hchang: Created page with "= 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 #..."

= 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

=== 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 ===

== M2 (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

=== Bugs ===

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-17T08:58:32Z

Hchang: /* Configure your device */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add additional required attributes to the manifest file
* Use the developer signing tool to create and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

The configuring steps will be covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest even though system message and web activity is still not supported at the moment.

=== 2. Add Additional Required Attributes to the Manifest File ===
Beside the well-known attributes in the gaia manifest, there are two additional attributes required by signed package and you have to manually add to the manifest:
# '''package-identifer''': A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# '''moz-package-origin''': The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add additional attributes to the manifest like "moz-resources".

For example, your manifest file may look like the following:

<pre>
{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org"
}
</pre>

After packaging and signing, it becomes:

<pre>
{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org",
//
// Auto-generated part.
"moz-resources": [...],
}
</pre>

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Now you can use [URL-of-the-package]!//[resource-path-relative-to-the-package] to access the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: '''network.http.enable-packaged-apps''' = true
** Enables Signed Package support: '''network.http.signed-packages.enabled''' = true
** Create a '''network.http.signed-packages.developer-root''' preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-17T03:59:02Z

Hchang: /* 2. Add Additional Required Attributes to the Manifest File */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add additional required attributes to the manifest file
* Use the developer signing tool to create and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

The configuring steps will be covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest even though system message and web activity is still not supported at the moment.

=== 2. Add Additional Required Attributes to the Manifest File ===
Beside the well-known attributes in the gaia manifest, there are two additional attributes required by signed package and you have to manually add to the manifest:
# '''package-identifer''': A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# '''moz-package-origin''': The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add additional attributes to the manifest like "moz-resources".

For example, your manifest file may look like the following:

<pre>
{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org"
}
</pre>

After packaging and signing, it becomes:

<pre>
{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org",
//
// Auto-generated part.
"moz-resources": [...],
}
</pre>

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Now you can use [URL-of-the-package]!//[resource-path-relative-to-the-package] to access the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: network.http.enable-packaged-apps = true
** Enables Signed Package support: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-17T03:29:30Z

Hchang: /* 2. Add Additional Required Attributes to the Manifest File */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add additional required attributes to the manifest file
* Use the developer signing tool to create and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

The configuring steps will be covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest even though system message and web activity is still not supported at the moment.

=== 2. Add Additional Required Attributes to the Manifest File ===
Beside the well-known attributes in the gaia manifest, there are two additional attributes required by signed package and you have to manually add to the manifest:
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add additional attributes to the manifest like "moz-resources".

For example, your manifest file may look like the following:

{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org"
}

After packaging and signing, it becomes:

{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org",
//
// Auto-generated part.
"moz-resources": [...],
}

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Now you can use [URL-of-the-package]!//[resource-path-relative-to-the-package] to access the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: network.http.enable-packaged-apps = true
** Enables Signed Package support: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-17T03:25:45Z

Hchang: /* Creating/Modifying a Signed Package */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add additional required attributes to the manifest file
* Use the developer signing tool to create and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

The configuring steps will be covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest even though system message and web activity is still not supported at the moment.

=== 2. Add Additional Required Attributes to the Manifest File ===
Beside the well-known attributes in the gaia manifest, there are two additional attributes required by signed package and you have to manually add to the manifest:
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add additional attributes to the manifest like "moz-resources".

For example, your manifest file may look like the following:

{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org"
}

After packaging and signing, it would become:

{
// Regular manifest attributes.
...,
...,
...,

// New attributes introduced by NSec.
"package-identifier": "3bd9a32f-8fd6-404f-bfbe-b883d2e93646",
"moz-package-origin": "http://people.mozilla.org",

// Auto-generated part.
"moz-resources": [...],
}
=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Now you can use [URL-of-the-package]!//[resource-path-relative-to-the-package] to access the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: network.http.enable-packaged-apps = true
** Enables Signed Package support: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T09:34:56Z

Hchang: /* Creating/Modifying a Signed Package */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add additional required attributes to the manifest file
* Use the developer signing tool to create and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

The configuring steps will be covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest even though system message and web activity is still not supported at the moment.

=== 2. Add Additional Required Fields to the Manifest File ===
Beside the well-known fields in the gaia manifest, there are two additional fields that you have to add to the manifest:
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest like "moz-resources".

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Now you can use [URL-of-the-package]!//[resource-path-relative-to-the-package] to access the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: network.http.enable-packaged-apps = true
** Enables Signed Package support: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T09:31:05Z

Hchang: /* Getting Started with Signed Packages */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add additional required attributes to the manifest file
* Use the developer signing tool to create and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

The configuring steps will be covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest. Note that system message and web activity is still not supported at the moment.

=== 2. Add Required Fields to the Manifest File ===
Beside the well-known fields in the gaia manifest, there are two additional fields that you have to add to the manifest:
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest like "moz-resources".

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Then you can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: network.http.enable-packaged-apps = true
** Enables Signed Package support: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T09:28:58Z

Hchang: /* Configuring your device */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add required fields to the manifest file
* Use the developer signing tool to make and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

These steps are covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest. Note that system message and web activity is still not supported at the moment.

=== 2. Add Required Fields to the Manifest File ===
Beside the well-known fields in the gaia manifest, there are two additional fields that you have to add to the manifest:
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest like "moz-resources".

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Then you can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configure your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages support: network.http.enable-packaged-apps = true
** Enables Signed Package support: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g or restart the device.

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T09:26:18Z

Hchang: /* Creating/Modifying a Signed Package */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add required fields to the manifest file
* Use the developer signing tool to make and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

These steps are covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file. However, you don't need to create the package on your own. What you need to do is:
 

=== 1. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app. Claim the permissions/system message/web activity as usual in the manifest. Note that system message and web activity is still not supported at the moment.

=== 2. Add Required Fields to the Manifest File ===
Beside the well-known fields in the gaia manifest, there are two additional fields that you have to add to the manifest:
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest like "moz-resources".

=== 3. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 4. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

Then you can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via browser. For example, if you host your package in http://foo.com/app.pak, the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configuring your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages network: http.enable-packaged-apps = true
** Enables Signed Packages: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g (ie either):
restart your device
“adb shell stop b2g” then “adb shell start b2g”

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T09:18:34Z

Hchang: /* 1. Add Additional Fields to the Manifest File */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add required fields to the manifest file
* Use the developer signing tool to make and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

These steps are covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file.
 

=== 0. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app.

=== 1. Add Additional Required Fields to the Manifest File ===
# package-identifer: A UUID string to uniquely identify this package. The identifier will be considered as a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest file like "moz-resources" during packaging.

=== 2. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 3. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

You can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via your browser. For example, if you host your package in http://foo.com/app.pak, then the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configuring your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages network: http.enable-packaged-apps = true
** Enables Signed Packages: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g (ie either):
restart your device
“adb shell stop b2g” then “adb shell start b2g”

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T09:04:38Z

Hchang: /* Getting Started with Signed Packages */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a regular gaia app
* Add required fields to the manifest file
* Use the developer signing tool to make and sign your package
* Host the package in where you specify in the manifest file

Since the signed package support (i.e. new security model) is pref'ed out at the moment, you have to
* Configure a number of developer preferences
* Upload your signing certificate to your test device
before testing this feature.

These steps are covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file.
 

=== 0. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app.

=== 1. Add Additional Fields to the Manifest File ===
# package-identifer: A UUID to uniquely identify this package. The identifier will be treated a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest file like "moz-resources".

=== 2. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 3. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

You can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via your browser. For example, if you host your package in http://foo.com/app.pak, then the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configuring your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages network: http.enable-packaged-apps = true
** Enables Signed Packages: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g (ie either):
restart your device
“adb shell stop b2g” then “adb shell start b2g”

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

FirefoxOS/New security model/Getting Started with Signed Packages

2015-11-16T08:58:22Z

Hchang: /* Creating/Modifying a Signed Package */

== Getting Started with Signed Packages ==
Signed Packages are web packages that been signed with a signing key. In production, these are signed by MarketPlace, but for testing purposes, developers can configure their device to accept a test signing key, so they can sign their own packages for one specific device.
 

The steps in the process are:
* Create a manifest for your Signed Package
* Use the developer signing tool to sign your package
* Upload the modified package to a server

Before you test for the first time, you must also do the following steps (only the first time):
* Configure a number of developer preferences
* Upload your signing certificate to your test device

These steps are covered in detail below.
 

== Creating/Modifying a Signed Package ==
Signed Packages are similar to existing web apps packaged apps - i.e. they consist of HTML, JavaScript, CSS files and other resources, and are packed into a package with a manifest.webapp file.
 

=== 0. Write a Regular Gaia App ===
The first step to create and host your signed package is to create a normal gaia app.

=== 1. Add Additional Fields to the Manifest File ===
# package-identifer: A UUID to uniquely identify this package. The identifier will be treated a part of the origin. So please be careful to change this value across versions.
# moz-package-origin: The origin where the package is going to be hosted. This prevents the package from being downloaded and hosted by other people.

Note that the packaging/signing tool would automatically add other fields to the manifest file like "moz-resources".

=== 2. Create and Sign Your Package ===
* Install a [https://github.com/johnathan79717/fxos-package-signing-tool signing tool]
* Follow the tool instructions to sign the package

=== 3. Host Your Package ===
* Signed Packages are hosted as a file on a web server. The only requirements are:
** The package is served with the MIME type of “application/package”
** The package is served from the location specified in the manifest (moz-package-origin)

You can now use [URL-of-the-package]!//[relative-path-to-resource] to navigate the packaged web content via your browser. For example, if you host your package in http://foo.com/app.pak, then the path to "index.html" inside the package would be http://foo.com/app.pak!//index.html.

 

== Preparing a Device to Load Signed Packages ==
In order to test Signed Packages on a device, you must upload your developer certificate to the device, and configure a number of preferences to both enable Signed Packages, and also to switch to trusting the developer certificate.
 

=== Configuring your device ===
If you have not already done so, you will need to enable remote debugging via DevTools, and grant additional access. (Enable remote debugging in the developer menu of the device. Use WebIDE to request higher privileges, and then access the preferences section. For information on how to do this, see here.)

* Upload the develop certificate created during signing to an accessible location:
adb push developercert.der /data/local/developercert.der
* Configure a number of preferences as follows:
** Enables web packages network: http.enable-packaged-apps = true
** Enables Signed Packages: network.http.signed-packages.enabled = true
** Create a signed-packages.developer-root preference using the path you created in the previous step: network.http.signed-packages.developer-root = /data/local/developercert.der
* Restart b2g (ie either):
restart your device
“adb shell stop b2g” then “adb shell start b2g”

=== Limitations ===
System Messages is not supported yet. Any function related to System Message cannot be used for now.

TPE CONNECTIVITY GROUP/2015-10-21

2015-10-21T03:10:49Z

Hchang: /* Henry Chang */

= 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 ==
* Collaborated with the team to create feature sets of NSec for 2.5.
** https://wiki.mozilla.org/FirefoxOS/New_security_model/2.5_Status
* Bug 1179060 - Apply a default CSP for signed packaged content (work in progress)
* Bug 1214071 - Add APIs get/removeCookiesForOriginAttributes() in nsICookieManager2.idl (work in progress)
* Bug 1213827 - CSP frame-ancestors breaks firefox os apps (2.5+)
** This is critical :)

== Henry Chang ==
# Bug 1178526 - Set appropriate origin attributes for signed packages.
## Move patch part 2 to Bug 1216062 (landed in mozilla-inbound).
## Discussing the approach in patch part 3 with Honza.
# Bug 1180088 - Fix security checks so that they work without appid by tagging a child process with a package identifier.
## r+'d by Kanru.
## Figuring out if we can have a test case on B2G emulator (impossible on browser since parent prcoess permission assertion is for B2G only)
# Bug 1216443 - Navigating from "about:blank" to signed packaged web content doesn't trigger process switch.
## The followup bug of Bug 1190088.
# Bug 1214572 - Should use a new process to load content when loading from a signed packaged web app.
## Need he20:10, 20 October 2015 (PDT)20:10, 20 October 2015 (PDT)~~lp

== Jonathan Hao ==
{{Bug|1178448}} - Tool for creating new signed packages
* Rebasing the r+ package, will land that patch first, and file another bug to address the pref renaming and bypassing trust origin.
{{Bug|1216469}} - Bypass verification for signed packages from trust origins.
* Ongoing

== 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 ==
* {{Bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
** Studying how the command send to the wpa_supplicant

== Yoshi Huang ==
* {{Bug|1196665}} - Add originAttributes into SpecialPowers
** addressing bholley's comment
* {{Bug|1196652}} - OriginSuffix is shown in about:serviceworker on b2g
** ongoing, add {wrapReflector: true} in Cu.cloneInto, but still cannot work on b2g.

TPE CONNECTIVITY GROUP/2015-10-13

2015-10-14T03:06:01Z

Hchang: /* Henry Chang */

= 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
#* https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2015-10-13#2015_Q4_Goal_Setting
# 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
# Meeting time
# Initiative of Orlando WW
# Progress of NSec this week: What can we deliver? What blocks us?

= 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)
*# {{Bug|1214071}} - Add APIs get/removeCookiesForOriginAttributes() in nsICookieManager2.idl ('''ongoing''')
*# {{Bug|1179060}} - Apply a default CSP for signed packaged content ('''feedback+''' from Christoph)
* Review patch: Bug 1204846 - Amount of mobile data consumed regresses
* Management
*# Complete 2015 Q4 goal settings

== Henry Chang ==
# Bug 1210573 - Add packageIdentifier attribute to nsIPackagedAppUtils
## To parse the 'package-identifier' from the manifest file.
## Landed.
## A prerequisite of Bug 1178526
# Bug 1212223 - nsMultiMixedConv might call |SendData| with incorrect buffer length
## Landed
## Fixed corrupt manifest file issue.
# Bug 1210235 - Pref off any signed web packaged app things
## r+'d by Valentin.
## Requires pref "network.http.packaged-signed-apps-enabled" to enable "signed package verification"
## Also, this patch would bypass the verification process if a package has no signautre (performance issue.)
#Bug 1214079 - Doom all the cache of the signed packaged web app if it's not verified.
## I was hoping to solve Bug 1190757 ([PackagedAppService] Delete all cached files if a package downloading in interrupted.) but Honza has some concerns so I just focus the special case: "verification failure" first.
# Bug 1178526 - Set appropriate origin attributes for signed packages
## Only last one patch waiting for Honza's review.
## was suppose to review on Monday Oct 12
# Bug 1180088 - Fix security checks so that they work without appid by tagging a child process with a package identifier.

== Jonathan Hao ==
* {{Bug|1178448}} - Let developer add their own trusted CA
** r-. I shouldn't do file I/O on main thread.
* {{Bug|1205209}} - [RTSP]When user connects a special RTSP link, the crash will happen.
** Landed.
* {{Bug|1207964}} - Remove workaround from bug 1080461
** To remove a workaround blocking RTSP live streams.
** Need to find RTSP live stream links to test.

== 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 ==
* {{bug|1187262}} - A device cannot connect B device through wifi
** Finally r+ !!!!!!!!!!!!!!!!!!!!
* Find out the flow chart to make service discovery of wifi direct
** Thanks to Henry!!!!
* Study on the current code, and think about how to make out the flow.
** How to send command to wpa_supplicant -> WifiCommand.jsm
** How to new a new event of p2p -> WifiWorker.js
** How to get "p2p_peers" 's result - > Add a listener of "scanresult"
** How to get the response? -> Add an event "P2P-SERV-DISC-RESP" in WifiP2pManager.jsm

== 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-15

2015-09-15T03:22:21Z

Hchang: /* Henry Chang */

= 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 ==

== Ethan Tseng ==

== Henry Chang ==

# Bug 1186290 - Notify TabParent to switch process when a signed packaged is loading from different origin.
## Add nsIPackagedAppChannelListener.onStartSignedPackageRequest
## Decide whether to call nsFrameLoader::SwitchProcessAndLoadURL in TabParent
## Who is supposed to review this patch? I asked for Jason first cuz he gave me some feedback before.

# Bug 1163254 - Add signedPkg OriginAttribute for new Firefox OS security model
## Actually 'packageId' is added to OriginAttributes rather than 'signedPkg'.
## IPC part is also included in the patch.
## bholley may review this since he's back from PTO (?)

# Bug 1178526 - Set appropriate origin attributes for signed packages
## Depends on Bug 1186290. (we need a path to propagate the packageId from deep internal to nsHttpChannel.)
## Add attribute 'packageId' to nsILoadContext, which is being refacored all around. Don't think we should wait because the refactor is not blocker.
## No idea who could review this. Will ask Honza or bholley first.

# Bug 1178518 - Support for verifying signed packages
## Change PackagedAppVerifier to call back the verification result asynchronously.

# Bug 1178533 - Register permissions, system messages etc on navigation to signed packages
## Help Stephanie solve issues she met.
## Worked around the parent side permission check (AssertAppProcessPermission) like what TCPSocketParent uses. Child side perm## ission check is okay since its alll origin-based. However, parent side would depend on if the tab has own app or a browser element to do the check (TabContext). Even more, mozIAppliction.hasPermission would be used to check permissions, where mozIAppliction is passed around child/parent by appId.
## Have a working fix by hacking TabContext. If we are loading a packaged content, we set the TabContext to AppFrame and owns a hand-made mozIApplication created by origin.

# Followup to Bug 1178533: In the long run we need something like nsIAppService to store proxies of mozIApplication for signed packaged content. For example, CSP module needs the csp defined in the manifest and for now no information in the manifest will be stored at all (except permissions.)

== Jonathan Hao ==

== Tim Huang ==
* {{Bug|1181489}} - mozAlarm mixes up 2 alarms: one for a regular CalDav sync, the other to wake you up
** Successfully reproduce this bug.
** Now, I am trying to confirm the root cause of this bug.
** A work around had been tried and could avoid this problem, however, it may trigger another issue according to the root cause, that I cannot sure yet, of this bug.

== Winnie Sun ==

== Yoshi Huang ==

== Aaron Wu (EPM) ==

TPE CONNECTIVITY GROUP/2015-07-14

2015-07-14T06:57:15Z

Hchang: /* Henry */

= 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 '''
# {{bug|1131493}} - [Wifi Direct] Support bonjour/upnp service advertisement
# {{bug|1178525}} - Ensure the package is verified before content is served
# {{bug|1144623}} - [Shinano][Aries] Inconsistent WiFi state reported: connecting in statusbar, connected in Settings app

* ''' Review & Feedbacks '''

* ''' Study '''
# Every bit about current app/security model on B2G. Will have a presentation.

== Jonathan ==
* ''' Done & Working in Progress '''
** {{Bug|1178518}} - Support for verifying signed packages
*** Studied package formats: http://w3ctag.github.io/packaging-on-the-web/
*** The signature format is still undefined.
*** Trace code in DocShell and Necko
*** Valentin from the Necko team said they've already implemented packaging support in {{Bug|1036275}}.
* ''' Review & Feedbacks '''
* ''' Pending '''
** 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.
* ''' 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-Q2

2015-06-09T09:19:45Z

Hchang: /* Henry */

= 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 ==
# 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-Q2

2015-06-09T02:36:17Z

Hchang: /* Henry */

= 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.

== Dimi ==
# 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 ==
# RTSP
# Performance improvement

TPE CONNECTIVITY GROUP/2015-05-26

2015-05-26T06:56:41Z

Hchang: /* Henry */

= 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 '''
*# Attend meeting @5/21: Origins and cookie jar transition to Yoshi
*#* Also discussed IPC security with Paul Theriault
*# {{Bug|1030936}} - [CSP] remove fast-path for certified apps once the C++ backend is activated ('''in progress''')
*#* Path is ready (simply code deletion) and review+. Need to resolve test failure in Gu test.
*#* Learning Gaia unit test (Gu test).
*# {{Bug|908933}} - CSP does not block cross-domain applets with object-src 'self ('''in progress''')
*# Prepare sharing talk: SOP, XSS and CSP
*# Arrange a brown bag sharing from Necko study group

* ''' Review & Feedbacks '''
*# Review: {{Bug|849642}} - Intermittent test_networkstats_enabled_perm.html | navigator.mozNetworkStats should be a nsIDOMMozNetworkStatsManager object ('''landed''')
*# Review: {{Bug|958689}} - Intermittent test_networkstats_alarms.html | uncaught exception - TypeError: navigator.mozNetworkStats is null | test_networkstats_enabled_no_perm.html | Accessing navigator.mozNetworkStats.getAvailableNetworks should have thrown! | Got an exception ('''landed''')

* ''' Pending '''
*#* {{Bug|959388}} - CSP 1.1: Workers have their own CSP policies, should not inherit from parent document
*#* {{Bug|881509}} - Content Security Policy ShouldLoad and ShouldProcess do not use request principal (blocks 959388)

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|1160913}} - [Emulator][Wifi] Unable to connect to secure Wifi AP on emulator
# {{Bug|1165844}} - Add stopDhcp function to nsINetworkService
#* landed.
# {{Bug|1161874}} - Add an entry point to trigger wifi display on B2G
#* r+'d for AudioManager.cpp part

# Multi-window
# {{Bug|1138287}} - Refactor GonkDisplay/nsWindow/hwc to support multiple displays
#* Merging with mc complete. Testing
#* Dedicated to redesign of nsScreenGonk/nsScreenManagerGonk/nsWindow

# {{Bug|1166658}} - [Emulator][meta] wifi marionette test case fixup
#* {{Bug|1166660}} - [Emulator][KK] test_wifi_auto_connect.js fails on KK emulator
#* {{Bug|1167099}} - [Emulator][KK] Wifi tethering test case failure
#* {{Bug|1168285}} - [Emulator][KK] When re-enable wifi, the remembered network cannot be automatically connected.
#* {{Bug|1160913}} - [Emulator][Wifi] Unable to connect to secure Wifi AP on emulator

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

* ''' Others '''

== Jonathan ==
（Took 3 days off)
* ''' Done & Working in Progress '''
** {{Bug|1159639}} - Implement API to add performance marker (WIP)
*** Have a patch now, can be recognized by Raptor.
*** :baku implemented a PerformanceBase. I should be able to inherit that and reduced duplicated code.
** Preparing for a sharing in DOM study group about 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 '''
** {{Bug|1165841}} - [NFC] Unable to share image from gallery, if this image was once previewed through notification. '''2.2+, landed on master already, waiting for Bug 1166595 landed on v2.2'''
** {{Bug|1165787}} - Use origin in RequestSyncService.jsm. '''ongoing'''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

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

TPE CONNECTIVITY GROUP/2015-05-19

2015-05-19T06:43:59Z

Hchang: /* Henry */

= 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 '''
*# Attend CSP bug triage @ Fri May 15, 2015
*#* CSP (bug 493857) has 50 open bugs (https://bugzilla.mozilla.org/showdependencytree.cgi?id=493857&hide_resolved=1)
*# Take 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
*# Trace CSP implementation
*#* nsDocument::InitCSP()
*#* nsCSPService and its ShoudLoad()
*#* CSPContext and its ShouldLoad()

* ''' Review & Feedbacks '''
*# Review: {{Bug|849642}} - Intermittent test_networkstats_enabled_perm.html | navigator.mozNetworkStats should be a nsIDOMMozNetworkStatsManager object ('''r+''')
*# Review: {{Bug|958689}} - Intermittent test_networkstats_alarms.html | uncaught exception - TypeError: navigator.mozNetworkStats is null | test_networkstats_enabled_no_perm.html | Accessing navigator.mozNetworkStats.getAvailableNetworks should have thrown! | Got an exception ('''r+''')
*# Both bugs have the same root cause and solution: Replace SpecialPowers.addPermission() by pushPermissions().

* ''' Pending '''

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|1160913}} - [Emulator][Wifi] Unable to connect to secure Wifi AP on emulator
# {{Bug|1165776}} - Support "run in new thread" for dhcpRequest in NetworkWorker
#* r+'d and flagged checkin-needed
# {{Bug|1165844}} - Add stopDhcp function to nsINetworkService
#* under review
# {{Bug|1161874}} - Add an entry point to trigger wifi display on B2G
#* r+'d for AudioManager.cpp part

# Multi-window
# {{Bug|1138287}} - Refactor GonkDisplay/nsWindow/hwc to support multiple displays
#* Merging with mc complete. Testing
# {{Bug|1138288}} - Extend nsScreenManagerGonk to support multiple screens
#* landed
#* 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 '''
* ''' 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 '''
** Intro for the origin in new security model. http://bit.ly/1AbTqvQ

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-05-12

2015-05-12T06:59:35Z

Hchang: /* Henry */

= 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 '''
# {{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|1159639}} - Implement API to add performance marker (WIP)
*** Eli replied, we could use absolute timestamp for now.
*** Took some time to get familliar with XPCOM to implement a service from scratch.
** Studying DocShell
*** http://mikeconley.ca/blog/2014/07/07/docshell-in-a-nutshell-part-1-original-intents/
*** http://mikeconley.ca/blog/2014/08/10/docshell-in-a-nutshell-part-2-the-wonder-years-1999-2004/
*** http://mikeconley.ca/blog/2015/01/03/docshell-in-a-nutshell-part-3-maturation-2005-2010/
*** http://www-archive.mozilla.org/projects/embedding/docshell.html
*** https://developer.mozilla.org/en-US/docs/Document_Loading_-_From_Load_Start_to_Finding_a_Handler
* ''' 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 '''
** 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-05T08:21:02Z

Hchang: /* Henry */

= 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 '''
*# 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) ==

== Aaron (EPM for Networking) ==
* 2.2 Status Update
** Code Complete (CC) - June 8th
*** 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-04-28

2015-04-28T06:37:03Z

Hchang: /* Henry */

= Discussion Topics =
* CAF CS code freeze: May 8th
* Bugs priority: 2.2 > spark > anything else

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

== Ethan ==
* ''' 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
*## Follow-up of {{Bug|1155544}} - [FFOS2.0][Woodduck][HOMO] Device reset when user try to see a RTSP video in H-264
*# Study Content Security Policy
*# Interview x 2
* ''' Review & Feedbacks '''
*# Review: {{Bug|1151760}} - [RTSP] Playback jumps to the end-of-stream after playing 34 seconds
* ''' Pending '''

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* checkin-needed
# {{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

# 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
#* Dedicated to redesign of nsScreenGonk/nsScreenManagerGonk/nsWindow

* ''' Review & Feedbacks '''
# {{Bug|1130962}} - Remove http proxy pref from NetworkService

* ''' 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 '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** Study suborigin proposal from Google, and send it to dev-b2g. https://groups.google.com/forum/#!topic/mozilla.dev.b2g/Rm9Yxg4r3W8
** Check the issues from cookie jars from Jonas' proposal.
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==
* 2.2 Status
** QA report: https://wiki.mozilla.org/B2G/QA/2.2/2015-04-27Status
** MTBF
*** NEXUS-5-L 5.1 PVT build MTBF 38.5 hrs & counting.
***FLAME-KK 4.4 PVT build MTBF 34.42 hrs.
** CAF CS code freeze: May 8th (CSRR)
*** Must meet stability numbers MTBF > 200, CPTH < 3
--> CPTH : the number of unique crashes per thousand hours. So less than 3 unique crashes, and each of those crashing less than once per 200 hours.

TPE CONNECTIVITY GROUP/2015-04-28

2015-04-28T06:34:52Z

Hchang: /* Henry */

= Discussion Topics =
* CAF CS code freeze: May 8th
* Bugs priority: 2.2 > spark > anything else

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

== Ethan ==
* ''' 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
*## Follow-up of {{Bug|1155544}} - [FFOS2.0][Woodduck][HOMO] Device reset when user try to see a RTSP video in H-264
*# Study Content Security Policy
*# Interview x 2
* ''' Review & Feedbacks '''
*# Review: {{Bug|1151760}} - [RTSP] Playback jumps to the end-of-stream after playing 34 seconds
* ''' Pending '''

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* checkin-needed

# {{Bug|1154690}} - [Shinano][Aries] Sometimes it's hard to connect to some WiFi network

# 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
#* Dedicated to redesign of nsScreenGonk/nsScreenManagerGonk/nsWindow

* ''' Review & Feedbacks '''
# {{Bug|1130962}} - Remove http proxy pref from NetworkService

* ''' 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 '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** Study suborigin proposal from Google, and send it to dev-b2g. https://groups.google.com/forum/#!topic/mozilla.dev.b2g/Rm9Yxg4r3W8
** Check the issues from cookie jars from Jonas' proposal.
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==
* 2.2 Status
** QA report: https://wiki.mozilla.org/B2G/QA/2.2/2015-04-27Status
** MTBF
*** NEXUS-5-L 5.1 PVT build MTBF 38.5 hrs & counting.
***FLAME-KK 4.4 PVT build MTBF 34.42 hrs.
** CAF CS code freeze: May 8th (CSRR)
*** Must meet stability numbers MTBF > 200, CPTH < 3
--> CPTH : the number of unique crashes per thousand hours. So less than 3 unique crashes, and each of those crashing less than once per 200 hours.

TPE CONNECTIVITY GROUP/2015-04-21

2015-04-21T01:36:09Z

Hchang: /* Henry */

= 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 '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* checkin-needed

# {{Bug|1154690}} - [Shinano][Aries] Sometimes it's hard to connect to some WiFi network

# 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
#* Dedicated to redesign of nsScreenGonk/nsScreenManagerGonk/nsWindow

* ''' Review & Feedbacks '''
# {{Bug|1130962}} - Remove http proxy pref from NetworkService

* ''' 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 '''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

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

== Wesley(EPM) ==

== Aaron (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-04-14

2015-04-14T03:23:03Z

Hchang: /* Henry */

= 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 '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* r+'d
# {{Bug|1053650}} - [B2G][MMS] Host Resolving with specified DNS in XMLHttpRequest
#* r+'d
# {{Bug|1130962}} - Remove http proxy pref from NetworkService
# {{Bug|1131632}} - [Wifi Direct][meta] Wifi Direct V3 refinement
# {{Bug|1118272}} - Alarms API does not fire at the right time with mozPower.cpuSleepAllowed on
#* Landed
# {{Bug|1146248}} - Avoid concurrent dhcp_do_request execution
#* Landed
# {{Bug|1146208}} - "Error: wifiListStart mark not found" while opening settings app
# {{Bug|1141391}} - [Wifi Direct] Create Wifi Direct testing app

# Multi-window

* ''' 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) ==

* New Security Model
** https://wiki.mozilla.org/FirefoxOS/New_security_model

TPE CONNECTIVITY GROUP/2015-04-07

2015-04-07T05:52:49Z

Hchang: /* Henry */

= Discussion Topics =
* Sensitive API - https://wiki.mozilla.org/FirefoxOS/New_security_model
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1144561}} - Create branch for platform_external_libnfc-nci. '''testing'''
# Prepare Necko Study Group TLS presentation slide
# Study New security model
* ''' Review & Feedbacks '''

* ''' Pending '''
# {{bug|1069201}} - [NFC] Support HCE in nfcd. '''on-going'''

== Ethan ==
* ''' Done & Working in Progress '''
# {{Bug|1146251}} - [Midori 2.0][Crash][Video streaming] MS crashed when play RTSP video
#* Uplift to 2.0 to avoid crash: {{bug|1088538}} - [RTSP] System crash in the end of playback due to NULL accessUnit
#* However, the long duration clip cannot be played normally, it would jump to end-of-stream
# Multi-screen project
#* Support the demonstration brown bag
#* Pick up the architecture from Henry
# FxOS new security model
#* Collect and digest information

* ''' Review & Feedbacks '''

* ''' Pending '''
# Documentation: Design draft of Necko idle state (ongoing)

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* r+'d
# {{Bug|1053650}} - [B2G][MMS] Host Resolving with specified DNS in XMLHttpRequest
#* r+'d
# {{Bug|1130962}} - Remove http proxy pref from NetworkService
# {{Bug|1131632}} - [Wifi Direct][meta] Wifi Direct V3 refinement
# {{Bug|1118272}} - Alarms API does not fire at the right time with mozPower.cpuSleepAllowed on
#* Landed
# {{Bug|1146248}} - Avoid concurrent dhcp_do_request execution
#* Landed
# {{Bug|1146208}} - "Error: wifiListStart mark not found" while opening settings app
# {{Bug|1141391}} - [Wifi Direct] Create Wifi Direct testing app

# Multi-window

* ''' Review & Feedbacks '''

* ''' Pending '''

* ''' Others '''

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

== Yoshi ==
* ''' Done & Working in Progress '''
** {{Bug|1149431}} - Add nfc as privileged permission in app-validator. '''landed, expected to work on 4/8 CST'''
** {{Bug|1150372}} - Add nfc feature checkbox in App Minimum Requirements.
** {{Bug|1146270}} - Move HCI Event Origin into NfcOptions.webidl. '''r+'''
** {{Bug|1127735}} - Update TechDiscoveredNotication. '''r+'''
* ''' Review & Feedbacks '''
* ''' Pending '''
* ''' Others '''

== Wesley(EPM) ==

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

TPE CONNECTIVITY GROUP/2015-03-24

2015-03-24T06:28:22Z

Hchang: /* Henry */

= Discussion Topics =
* Q1 performance review presentation
* NFC Tokyo workweek sharing - https://github.com/changyihsin/nfcworkshopkddi/blob/master/note.md
== Dimi ==
* ''' Done & Working in Progress '''
# {{bug|1143528}} - [Flame][NFC] Can't enable/disable NFC in Settings. '''thomas fixed'''
# {{bug|1136515}} - [Flame][NFC] libnfc-pn547.so is not built. '''land'''
# {{bug|1144561}} - Create branch for platform_external_libnfc-nci. '''ni?'''
# {{bug|1069201}} - [NFC] Support HCE in nfcd. '''on-going'''
# Prepare HCE presentation
# Study Cryptography and TLS

nfcd refactor:
# {{bug|1057918}} - [NFC] Support enable/disable debug message at runtime. '''r?'''

* ''' Review & Feedbacks '''
# {{bug|884594}} - Support NFC Access Control for Secure Element Access

* ''' Pending '''

== Ethan (Last 2 Weeks) ==
* ''' Done & Working in Progress '''
# {{Bug|1117486}} - [FFOS2.0][Woodduck] System crash by replaying the same RTSP clip several times ('''resolved fixed''')
#* Uplift to 2.0, 2.1, 2.2, 2.1S and 2.0M
# {{Bug|1059144}} - [MADAI][Multimedia] System crash when RTSP client connects to a non-RTSP-server port
#* Uplift to 2.0
# {{Bug|1133461}} - [RTSP] Remove the extra PLAY request for seek operation ('''resolved fixed''')
#* Follow-up: {{Bug|1141412}} - [RTSP] Tweak EnsureActive to make it more suitable for RTSP streaming
# {{Bug|1139811}} - [Nexus 5][Cost Control]The device can't pop up the warn box when the data usage exceeds limit value
#* Cannot reproduce, extreme corner case
# DOM group: Review all sessions/slides of phase 1 and provide categorization idea
# Necko group
#* Coordinate and work out Part-I session topics (https://taiwan.etherpad.mozilla.org/NeckoStudyGroup)
#* Rehearsal for ''Overview of HTTP'' (Good job, Jonathan! Thanks to Henry and Jessica! \^o^/)

* ''' Review & Feedbacks '''
# Review: {{Bug|1144513}} - [gonk-lmr1] Adapt RTSPSource.cpp
# Provide suggestion: {{Bug|1142383}} - [RTSP] More RTSP testcases
# Feedback to remove blocker flag
#* {{Bug|1122400}} - [Flame][RTSP]RTSP error appears in browser app, and then there is an unwanted alert page if we play video in video app
# Feedback to triage
#* {{Bug|1083680}} - [Usage][Cost Control] (Follow up to fix root cause) Noticeable difference between by application breakdown totals and the total displayed in chart and widget
#* {{Bug|1102812}} - [NetworkStats] Improve the accuracy of network statistics

* ''' Pending '''
# Documentation: Design draft of Necko idle state

== Henry ==
* ''' Done & Working in Progress '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* r+'d
# {{Bug|1053650}} - [B2G][MMS] Host Resolving with specified DNS in XMLHttpRequest
#* r+'d
# {{Bug|1130962}} - Remove http proxy pref from NetworkService
# {{Bug|1131632}} - [Wifi Direct][meta] Wifi Direct V3 refinement
# {{Bug|1118272}} - Alarms API does not fire at the right time with mozPower.cpuSleepAllowed on
#* Found the root cause and attached a patch for review.
# {{Bug|1146248}} - Avoid concurrent dhcp_do_request execution
# {{Bug|1146208}} - "Error: wifiListStart mark not found" while opening settings app
# {{Bug|1141391}} - [Wifi Direct] Create Wifi Direct testing app

# Multi-window

* ''' Review & Feedbacks '''

* ''' Pending '''

* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''

* ''' Review & Feedbacks '''

* ''' Pending '''

* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''
** {{Bug|1146270}} - Move HCI Event Origin into NfcOptions.webidl. '''ongoing'''

* ''' Review & Feedbacks '''
** {{Bug|884594}} - Support NFC Access Control for Secure Element Access

== Wesley(EPM) ==

== Howie (EPM for Networking) ==

TPE CONNECTIVITY GROUP/2015-03-17

2015-03-17T01:38:09Z

Hchang: /* Henry */

= 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 '''
# {{Bug|992772}} - [B2G][RIL][NetworkManager] ResolveHostName with the DNS of the specified NetworkInterface.
#* r+'d
# {{Bug|1053650}} - [B2G][MMS] Host Resolving with specified DNS in XMLHttpRequest
#* Under review
# {{Bug|1130962}} - Remove http proxy pref from NetworkService
# {{Bug|1131632}} - [Wifi Direct][meta] Wifi Direct V3 refinement
# {{Bug|1118272}} - Alarms API does not fire at the right time with mozPower.cpuSleepAllowed on
#* Found the root cause and attached a patch for review.
# Multi-window

* ''' Review & Feedbacks '''
# {{Bug|1140261 }} - gecko/ipc/keystore/KeyStore.cpp:142:27: error: comparison of unsigned expression >= 0 is always true [-Werror=type-limits]

* ''' Pending '''

* ''' Others '''

== Jonathan ==
* ''' Done & Working in Progress '''

* ''' Review & Feedbacks '''

* ''' Pending '''

* ''' Others '''

== Yoshi ==
* ''' Done & Working in Progress '''

* ''' Review & Feedbacks '''

* ''' Pending '''

* ''' Others '''

== Wesley(EPM) ==

== Howie (EPM for Networking) ==