Expertiza_Wiki - User contributions [en]

User:Rjain9

2016-11-15T03:30:28Z

Rmuddur:

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 
=='''Introduction'''==
=== Servo ===
[https://servo.org/ Servo] is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== HTTP Cookie ===
An [https://en.wikipedia.org/wiki/HTTP_cookie HTTP Cookie] is a small part of data which is sent by the website to the user's computer and is stored by the user's web browser while the user is browsing. A cookie is mainly used for recording a user's browsing activity or to remember stateful information for the websites.

=== Rust ===
[https://doc.rust-lang.org/book/ Rust] is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.

=='''Project Description'''==
The goal of this project is to implement newer, more secure standards, and complete missing pieces of existing ones, in order to increase the security available to users of the Servo browser. The project entails adding improved network security features for Servo engine by implementing a maximum number of cookies per host, and restricting insecure cookies from overwriting secure ones. The initial steps for this project have been completed as part of the OSS Project.

=='''Tasks'''==

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Redesign CookieStorage to store cookies in a HashMap where the key is the base domain of the cookie's source (ie. "www.google.co.uk" becomes "google.co.uk")

3) Store a max_per_host limit in CookieStorage that is checked when adding new cookies; evict the oldest cookie if the limit is reached (add tests to tests/unit/net/cookie.rs)

4) Implement the [https://datatracker.ietf.org/doc/draft-ietf-httpbis-cookie-alone/?include_text=1 Leave Secure Cookies Alone] specification - ensure that newly created insecure cookies cannot override existing secure cookies (add tests to tests/unit/net/cookie.rs)

The current implementation of CookieStorage utilizes vector of Cookies. No restrictions are placed on the number of cookies that can be added per host.The proposed change will refactor CookieStorage to use HashMap with Base host as key. There would a limit on the maximum number of cookies per host. Changes will also include, implementation of '''Deprecate modification of 'secure' cookies from non-secure origins''' which update RFC6265 by removing the ability for a non-secure origin to set cookies with a 'secure' flag, and to overwrite cookies whose 'secure' flag is set.

Since this contains refactoring, all existing unit testcases need to pass. Additionally, new unit test cases will be written for validating implementation of aforementioned specification.

=='''Approach'''==
First step would be to update the vector to HasMap by maintaining the wrapper functions used on the CookieStporage class. Upon completion of the task, all the unit test cases should pass. This would provide an additional checkpoint to verify the integrity of the new CookieStorage class's behavior.

Subsequent steps would include refactoring of the code so that the existing functionality is retained with added feature and advantages provided by HashMaps like faster search.

RFC implementation would be possible after the code refactor of CookieStorage class. Most of the RFC related changes are related to maintaining the content of the map. So this step would be penultimate step of the project.

Team would follow Test Driven Development, so unit tests would be written first wherever required and production code would be written to make the testcases pass.

We would follow Pair Programming to minimize errors and maximize the productivity. We are going to adhere to industry set standards which provide better QoS and stable product.

=='''Continuous Integration'''==
Continuous Integration, being a key element in Test Driven Development. Our team will setup our own Travis server to ensure code sanity.
==Test Plan==
There is no manual testing in this project. Existing unit tests will ensure that refactoring has not broken any functionality. New unit test cases would be written for validating "Leave Secure Cookies Alone" specification.

1) Unit test for checking "secure-only-flag" is set.
2) Unit test for "domain" domain-matches the "domain" of the newly created cookie, or vice-versa.
3) Unit test to validate The "path" of the newly created cookie path-matches the "path" of the existing cookie.

Please note that since lot of unit tests are already in place. We are not required to write many new test cases. After refactoring, if CI passes without any dip in code coverage then we can say refactoring is successful.
=='''Files to be modified'''==
* /servo/components/cookie_storage.rs
* /servo/components/net/cookie.rs
* /servo/test/unit/cookie.rs
* /servo/components/servo/cargo.toml
* /servo/components/servo/cargo.lock

=='''Key People'''==
=== Developers ===
* Guru Darshan
* Raghavendra Nayak
* Rishi Jain
* Tsung-Ying Chuang
=== Mentor ===
* Ed Gehringer

User:Rjain9

2016-11-15T03:26:33Z

Rmuddur:

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 
=='''Introduction'''==
=== Servo ===
[https://servo.org/ Servo] is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== HTTP Cookie ===
An [https://en.wikipedia.org/wiki/HTTP_cookie HTTP Cookie] is a small part of data which is sent by the website to the user's computer and is stored by the user's web browser while the user is browsing. A cookie is mainly used for recording a user's browsing activity or to remember stateful information for the websites.

=== Rust ===
[https://doc.rust-lang.org/book/ Rust] is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.

=='''Project Description'''==
The goal of this project is to implement newer, more secure standards, and complete missing pieces of existing ones, in order to increase the security available to users of the Servo browser. The project entails adding improved network security features for Servo engine by implementing a maximum number of cookies per host, and restricting insecure cookies from overwriting secure ones. The initial steps for this project have been completed as part of the OSS Project.

=='''Tasks'''==

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Redesign CookieStorage to store cookies in a HashMap where the key is the base domain of the cookie's source (ie. "www.google.co.uk" becomes "google.co.uk")

3) Store a max_per_host limit in CookieStorage that is checked when adding new cookies; evict the oldest cookie if the limit is reached (add tests to tests/unit/net/cookie.rs)

4) Implement the [https://datatracker.ietf.org/doc/draft-ietf-httpbis-cookie-alone/?include_text=1 Leave Secure Cookies Alone] specification - ensure that newly created insecure cookies cannot override existing secure cookies (add tests to tests/unit/net/cookie.rs)

The current implementation of CookieStorage utilizes vector of Cookies. No restrictions are placed on the number of cookies that can be added per host.The proposed change will refactor CookieStorage to use HashMap with Base host as key. There would a limit on the maximum number of cookies per host. Changes will also include, implementation of '''Deprecate modification of 'secure' cookies from non-secure origins''' which update RFC6265 by removing the ability for a non-secure origin to set cookies with a 'secure' flag, and to overwrite cookies whose 'secure' flag is set.

Since this contains refactoring, all existing unit testcases need to pass. Additionally, new unit test cases will be written for validating implementation of aforementioned specification.

=='''Approach'''==
First step would be to update the vector to HasMap by maintaining the wrapper functions used on the CookieStporage class. Upon completion of the task, all the unit test cases should pass. This would provide an additional checkpoint to verify the integrity of the new CookieStorage class's behavior.

Subsequent steps would include refactoring of the code so that the existing functionality is retained with added feature and advantages provided by HashMaps like faster search.

RFC implementation would be possible after the code refactor of CookieStorage class. Most of the RFC related changes are related to maintaining the content of the map. So this step would be penultimate step of the project.

Team would follow Test Driven Development, so unit tests would be written first wherever required and production code would be written to make the testcases pass.

We would follow Pair Programming to minimize errors and maximize the productivity. We are going to adhere to industry set standards which provide better QoS and stable product.

=='''Continuous Integration'''==
Continuous Integration, being a key element in Test Driven Development. Our team will setup our own Travis server to ensure code sanity.
==Test Plan==
There is no manual testing in this project. Existing unit tests will ensure that refactoring has not broken any functionality. New unit test cases would be written for validating "Leave Secure Cookies Alone" specification.

1) Unit test for checking "secure-only-flag" is set.
2) Unit test for "domain" domain-matches the "domain" of the newly created cookie, or vice-versa.
3) Unit test to validate The "path" of the newly created cookie path-matches the "path" of the existing cookie.

=='''Files to be modified'''==
* /servo/components/cookie_storage.rs
* /servo/components/net/cookie.rs
* /servo/test/unit/cookie.rs
* /servo/components/servo/cargo.toml
* /servo/components/servo/cargo.lock

=='''Key People'''==
=== Developers ===
* Guru Darshan
* Raghavendra Nayak
* Rishi Jain
* Tsung-Ying Chuang
=== Mentor ===
* Ed Gehringer

User:Rjain9

2016-11-15T03:25:13Z

Rmuddur:

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 
=='''Introduction'''==
=== Servo ===
[https://servo.org/ Servo] is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== HTTP Cookie ===
An [https://en.wikipedia.org/wiki/HTTP_cookie HTTP Cookie] is a small part of data which is sent by the website to the user's computer and is stored by the user's web browser while the user is browsing. A cookie is mainly used for recording a user's browsing activity or to remember stateful information for the websites.

=== Rust ===
[https://doc.rust-lang.org/book/ Rust] is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.

=='''Project Description'''==
The goal of this project is to implement newer, more secure standards, and complete missing pieces of existing ones, in order to increase the security available to users of the Servo browser. The project entails adding improved network security features for Servo engine by implementing a maximum number of cookies per host, and restricting insecure cookies from overwriting secure ones. The initial steps for this project have been completed as part of the OSS Project.

=='''Tasks'''==

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Redesign CookieStorage to store cookies in a HashMap where the key is the base domain of the cookie's source (ie. "www.google.co.uk" becomes "google.co.uk")

3) Store a max_per_host limit in CookieStorage that is checked when adding new cookies; evict the oldest cookie if the limit is reached (add tests to tests/unit/net/cookie.rs)

4) Implement the [https://datatracker.ietf.org/doc/draft-ietf-httpbis-cookie-alone/?include_text=1 Leave Secure Cookies Alone] specification - ensure that newly created insecure cookies cannot override existing secure cookies (add tests to tests/unit/net/cookie.rs)

The current implementation of CookieStorage utilizes vector of Cookies. No restrictions are placed on the number of cookies that can be added per host.The proposed change will refactor CookieStorage to use HashMap with Base host as key. There would a limit on the maximum number of cookies per host. Changes will also include, implementation of '''Deprecate modification of 'secure' cookies from non-secure origins''' which update RFC6265 by removing the ability for a non-secure origin to set cookies with a 'secure' flag, and to overwrite cookies whose 'secure' flag is set.

Since this contains refactoring, all existing unit testcases need to pass. Additionally, new unit test cases will be written for validating implementation of aforementioned specification.

=='''Approach'''==
First step would be to update the vector to HasMap by maintaining the wrapper functions used on the CookieStporage class. Upon completion of the task, all the unit test cases should pass. This would provide an additional checkpoint to verify the integrity of the new CookieStorage class's behavior.

Subsequent steps would include refactoring of the code so that the existing functionality is retained with added feature and advantages provided by HashMaps like faster search.

RFC implementation would be possible after the code refactor of CookieStorage class. Most of the RFC related changes are related to maintaining the content of the map. So this step would be penultimate step of the project.

Team would follow Test Driven Development, so unit tests would be written first wherever required and production code would be written to make the testcases pass.

We would follow Pair Programming to minimize errors and maximize the productivity. We are going to adhere to industry set standards which provide better QoS and stable product.

=='''Continuous Integration'''==
Continuous Integration, being a key element in Test Driven Development. Our team will setup our own Travis server to ensure code sanity.
==Test Plan==
There is no manual testing in this project. Existing unit tests will ensure that refactoring has not broken any functionality. New unit test cases would be written for validating "Leave Secure Cookies Alone" specification.

1) Unit test for checking "secure-only-flag" is set.
2) Unit test for "domain" domain-matches the "domain" of the newly created cookie, or vice-versa.
3) Unit test to validate The "path" of the newly created cookie path-matches the "path" of the existing cookie.

=='''Files to be modified'''==
* /servo/components/cookie_storage.rs
* /servo/components/net/cookie.rs
* /servo/test/unit/cookie.rs
* /servo/components/servo/cargo.toml
* /servo/components/servo/cargo.lock

=='''Key People'''==
=== Developers ===
* Guru Darshan
* Raghavendra Nayak
* Rishi Jain
* Tsung-Ying Chuang
=== Mentor ===
* Ed Gehringer

User:Rjain9

2016-11-15T03:20:35Z

Rmuddur:

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 
=='''Introduction'''==
=== Servo ===
[https://servo.org/ Servo] is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== HTTP Cookie ===
An [https://en.wikipedia.org/wiki/HTTP_cookie HTTP Cookie] is a small part of data which is sent by the website to the user's computer and is stored by the user's web browser while the user is browsing. A cookie is mainly used for recording a user's browsing activity or to remember stateful information for the websites.

=== Rust ===
[https://doc.rust-lang.org/book/ Rust] is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.

=='''Project Description'''==
The goal of this project is to implement newer, more secure standards, and complete missing pieces of existing ones, in order to increase the security available to users of the Servo browser. The project entails adding improved network security features for Servo engine by implementing a maximum number of cookies per host, and restricting insecure cookies from overwriting secure ones. The initial steps for this project have been completed as part of the OSS Project.

=='''Tasks'''==

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Redesign CookieStorage to store cookies in a HashMap where the key is the base domain of the cookie's source (ie. "www.google.co.uk" becomes "google.co.uk")

3) Store a max_per_host limit in CookieStorage that is checked when adding new cookies; evict the oldest cookie if the limit is reached (add tests to tests/unit/net/cookie.rs)

4) Implement the [https://datatracker.ietf.org/doc/draft-ietf-httpbis-cookie-alone/?include_text=1 Leave Secure Cookies Alone] specification - ensure that newly created insecure cookies cannot override existing secure cookies (add tests to tests/unit/net/cookie.rs)

The current implementation of CookieStorage utilizes vector of Cookies. No restrictions are placed on the number of cookies that can be added per host.The proposed change will refactor CookieStorage to use HashMap with Base host as key. There would a limit on the maximum number of cookies per host. Changes will also include, implementation of '''Deprecate modification of 'secure' cookies from non-secure origins''' which update RFC6265 by removing the ability for a non-secure origin to set cookies with a 'secure' flag, and to overwrite cookies whose 'secure' flag is set.

Since this contains refactoring, all existing unit testcases need to pass. Additionally, new unit test cases will be written for validating implementation of aforementioned specification.

=='''Approach'''==
First step would be to update the vector to HasMap by maintaining the wrapper functions used on the CookieStporage class. Upon completion of the task, all the unit test cases should pass. This would provide an additional checkpoint to verify the integrity of the new CookieStorage class's behavior.

Subsequent steps would include refactoring of the code so that the existing functionality is retained with added feature and advantages provided by HashMaps like faster search.

RFC implementation would be possible after the code refactor of CookieStorage class. Most of the RFC related changes are related to maintaining the content of the map. So this step would be penultimate step of the project.

Team would follow Test Driven Development, so unit tests would be written first wherever required and production code would be written to make the testcases pass.

We would follow Pair Programming to minimize errors and maximize the productivity. We are going to adhere to industry set standards which provide better QoS and stable product.

=='''Continuous Integration'''==
Continuous Integration, being a key element in Test Driven Development. Our team will setup our own Travis server to ensure code sanity.
==Test Plan==
There is no manual testing in this project. Existing unit tests will ensure that refactoring has not broken any functionality. New unit test cases would be written for validating "Leave Secure Cookies Alone" specification.

=='''Files to be modified'''==
* /servo/components/cookie_storage.rs
* /servo/components/net/cookie.rs
* /servo/test/unit/cookie.rs
* /servo/components/servo/cargo.toml
* /servo/components/servo/cargo.lock

=='''Key People'''==
=== Developers ===
* Guru Darshan
* Raghavendra Nayak
* Rishi Jain
* Tsung-Ying Chuang
=== Mentor ===
* Ed Gehringer

CSC/ECE 517 Fall 2016

2016-10-29T00:02:19Z

Rmuddur: /* Writing Assignments 2 */

[http://www.example.com link title]==Calibration Assignment Submissions==
*[[Calibration Assignment Submission (Firebrick JS)]]
*[[Calibration Assignment Submission (Active Job)]]
==Writing Assignments 2==
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE 517 Fall 2016/E1643. Refactor Suggestion controller]]
*[[CSC/ECE 517 Fall 2016/E1631. Refactoring Bidding Interface]]
*[[CSC/ECE 517 Fall 2016/E1674.Refactor leaderboard.rb and write unit tests]]
*[[CSC/ECE 517 Fall 2016/E1671. Unit Tests for participants.rb Hierarchy]]
*[[CSC/ECE 517 Fall 2016/E1668.Test e-mailing functionality]]
*[[CSC/ECE 517 Fall 2016/E1658. Refractor lottery_controller.rb and write integration tests]]
*[[CSC/ECE 517 Fall 2016/E1660. Review requirements and thresholds]]
*[[CSC/ECE 517 Fall 2016/E1650. Sort instructor views alphabetically by default]]
*[[CSC/ECE 517 Fall 2016/E1644. Refactor and test Teams Controller]]
*[[CSC/ECE 517 Fall 2016/E1659. Refactor on_the_fly_calc.rb]]
*[[CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors]]
*[[CSC/ECE 517 Fall 2016/E1653. Fix and improve rubric criteria]]
*[[CSC/ECE 517 Fall 2016/E1642. Refactor review_response_map.rb]]
*[[CSC/ECE_517_Fall_2016/E1664:_Feature_Test_Assignment_Creation]]
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE_517_Fall_2016/E1654. Improve_date-picker_and_deadlines]]
*[[CSC/ECE_517_Fall_2016/E1652 Fix teammate advertisements and requests to join a team ]]
*[[CSC/ECE_517_Fall_2016/E1662. UI issues/fixes]]
*[[CSC/ECE_517_Fall_2016/E1673. Refactor question_type.rb]]
*[[CSC/ECE_517_Fall_2016/E1675. Timestamp for student file & hyperlink submissions]]
*[[CSC/ECE_517_Fall_2016/E1640. Refactor response.rb and response_helper.rb]]
*[[CSC/ECE 517 Fall 2016/E1634. Refactor and write unit test of due_date.rb and deadline_helper.rb]]
*[[CSC/ECE_517_Fall_2016/M1654._Improve_network_security_features]]

CSC/ECE 517 Fall 2016

2016-10-28T23:58:53Z

Rmuddur: /* Writing Assignments 2 */

[http://www.example.com link title]==Calibration Assignment Submissions==
*[[Calibration Assignment Submission (Firebrick JS)]]
*[[Calibration Assignment Submission (Active Job)]]
==Writing Assignments 2==
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE 517 Fall 2016/E1643. Refactor Suggestion controller]]
*[[CSC/ECE 517 Fall 2016/E1631. Refactoring Bidding Interface]]
*[[CSC/ECE 517 Fall 2016/E1674.Refactor leaderboard.rb and write unit tests]]
*[[CSC/ECE 517 Fall 2016/E1671. Unit Tests for participants.rb Hierarchy]]
*[[CSC/ECE 517 Fall 2016/E1668.Test e-mailing functionality]]
*[[CSC/ECE 517 Fall 2016/E1658. Refractor lottery_controller.rb and write integration tests]]
*[[CSC/ECE 517 Fall 2016/E1660. Review requirements and thresholds]]
*[[CSC/ECE 517 Fall 2016/E1650. Sort instructor views alphabetically by default]]
*[[CSC/ECE 517 Fall 2016/E1644. Refactor and test Teams Controller]]
*[[CSC/ECE 517 Fall 2016/E1659. Refactor on_the_fly_calc.rb]]
*[[CSC/ECE 517 Fall 2016/E1657. Introduce a Student View for instructors]]
*[[CSC/ECE 517 Fall 2016/E1653. Fix and improve rubric criteria]]
*[[CSC/ECE 517 Fall 2016/E1642. Refactor review_response_map.rb]]
*[[CSC/ECE_517_Fall_2016/E1664:_Feature_Test_Assignment_Creation]]
*[[CSC/ECE 517 Fall 2016/E1666. Test team functionality]]
*[[CSC/ECE_517_Fall_2016/E1654. Improve_date-picker_and_deadlines]]
*[[CSC/ECE_517_Fall_2016/E1652 Fix teammate advertisements and requests to join a team ]]
*[[CSC/ECE_517_Fall_2016/E1662. UI issues/fixes]]
*[[CSC/ECE_517_Fall_2016/E1673. Refactor question_type.rb]]
*[[CSC/ECE_517_Fall_2016/E1675. Timestamp for student file & hyperlink submissions]]
*[[CSC/ECE_517_Fall_2016/E1640. Refactor response.rb and response_helper.rb]]
*[[CSC/ECE 517 Fall 2016/E1634. Refactor and write unit test of due_date.rb and deadline_helper.rb]]
*[CSC/ECE 517 Fall 2016/M1654. Improve Network Security Features http://wiki.expertiza.ncsu.edu/index.php/CSC/ECE_517_Fall_2016/M1654._Improve_network_security_features]

CSC/ECE 517 Fall 2016/M1654. Improve network security features

2016-10-28T23:54:13Z

Rmuddur: /* Servo */

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 

Servo supports standard [HTTP cookies] and parts of the Referral-Policy web standard. The project aims at increasing the security available to Servo browser users by implementing secure standards and complete the missing parts of the existing implementations. The project involves adding "strict" version of existing referrer policies.

=='''Introduction'''==

=== Rust ===
[https://doc.rust-lang.org/book/ Rust] is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.

=== Servo ===
[https://servo.org/ Servo] is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== Referrer Policy ===
Referrer is a HTTP header field which contains the source of the URL that requested the web page. Referrer-policy dictates algorithm used to generate Referrer header when a new web page is requested.

=='''Project Description'''==
The project entails adding improved network security features for Servo engine by supplementing the existing Referrer-policies with 'strict origin' and 'strict origin when cross origin' policies.

A brief description of the list of tasks assigned as part of the project is as follows:

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions

3) Implement strict-origin and strict-origin-when-cross-origin referrer policies (see determine_request_referrer and determine_policy_for_token)

4) Add support for the new strict policy values in the Referrer-Policy HTTP header (source)

5) Add tests for the new policy values in tests/unit/net/http_loader.rs (run with ./mach test-unit -p net)

=== Referrer Policies added in this project ===
==== Strict Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin Strict Origin] Referrer Policy dictates that the Referrer in HTTP header is always filled with the stripped URL of the origin and not the complete URL.

==== Strict origin When Cross Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin-when-cross-origin Strict Origin When Cross Origin] Referrer Policy dictates that the Referrer in HTTP header is filled with the stripped URL of the origin if the request is sent to a URL different from the origin and the complete URL is sent when making [https://en.wikipedia.org/wiki/Same-origin_policy same origin] requests.

== '''Implementation''' ==
Strict Origin and Strict Origin When Cross origin Referrer policy implementations have been added to the codebase. The pull request for Servo repository is available [https://github.com/rjain9/servo/pull/1 here] and Hyper is available [https://github.com/hyperium/hyper/pull/943 here]

Referrer policy implementation 
[[File:Ubs.jpg]] 
Selected Test case changes 
[[File:Ubs1.jpg]]

For complete changes please refer aforementioned url.

== '''Testing''' ==
Various testcase scenerios involving request from HTTP to HTTPS URLs and vice-versa have been added in [https://github.com/rjain9/servo/pull/1 tests/unit/net/http_loader.rs]. Full functionality coverage has been taken case of by ensuring that all same origin and cross origin test cases have been included.

CSC/ECE 517 Fall 2016/M1654. Improve network security features

2016-10-28T23:52:49Z

Rmuddur: /* Rust */

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 

Servo supports standard [HTTP cookies] and parts of the Referral-Policy web standard. The project aims at increasing the security available to Servo browser users by implementing secure standards and complete the missing parts of the existing implementations. The project involves adding "strict" version of existing referrer policies.

=='''Introduction'''==

=== Rust ===
[https://doc.rust-lang.org/book/ Rust] is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.

=== Servo ===
Servo is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== Referrer Policy ===
Referrer is a HTTP header field which contains the source of the URL that requested the web page. Referrer-policy dictates algorithm used to generate Referrer header when a new web page is requested.

=='''Project Description'''==
The project entails adding improved network security features for Servo engine by supplementing the existing Referrer-policies with 'strict origin' and 'strict origin when cross origin' policies.

A brief description of the list of tasks assigned as part of the project is as follows:

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions

3) Implement strict-origin and strict-origin-when-cross-origin referrer policies (see determine_request_referrer and determine_policy_for_token)

4) Add support for the new strict policy values in the Referrer-Policy HTTP header (source)

5) Add tests for the new policy values in tests/unit/net/http_loader.rs (run with ./mach test-unit -p net)

=== Referrer Policies added in this project ===
==== Strict Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin Strict Origin] Referrer Policy dictates that the Referrer in HTTP header is always filled with the stripped URL of the origin and not the complete URL.

==== Strict origin When Cross Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin-when-cross-origin Strict Origin When Cross Origin] Referrer Policy dictates that the Referrer in HTTP header is filled with the stripped URL of the origin if the request is sent to a URL different from the origin and the complete URL is sent when making [https://en.wikipedia.org/wiki/Same-origin_policy same origin] requests.

== '''Implementation''' ==
Strict Origin and Strict Origin When Cross origin Referrer policy implementations have been added to the codebase. The pull request for Servo repository is available [https://github.com/rjain9/servo/pull/1 here] and Hyper is available [https://github.com/hyperium/hyper/pull/943 here]

Referrer policy implementation 
[[File:Ubs.jpg]] 
Selected Test case changes 
[[File:Ubs1.jpg]]

For complete changes please refer aforementioned url.

== '''Testing''' ==
Various testcase scenerios involving request from HTTP to HTTPS URLs and vice-versa have been added in [https://github.com/rjain9/servo/pull/1 tests/unit/net/http_loader.rs]. Full functionality coverage has been taken case of by ensuring that all same origin and cross origin test cases have been included.

CSC/ECE 517 Fall 2016/M1654. Improve network security features

2016-10-28T23:52:06Z

Rmuddur: /* Implementation */

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 

Servo supports standard [HTTP cookies] and parts of the Referral-Policy web standard. The project aims at increasing the security available to Servo browser users by implementing secure standards and complete the missing parts of the existing implementations. The project involves adding "strict" version of existing referrer policies.

=='''Introduction'''==

=== Rust ===
Rust is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.[https://doc.rust-lang.org/book/ title]

=== Servo ===
Servo is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== Referrer Policy ===
Referrer is a HTTP header field which contains the source of the URL that requested the web page. Referrer-policy dictates algorithm used to generate Referrer header when a new web page is requested.

=='''Project Description'''==
The project entails adding improved network security features for Servo engine by supplementing the existing Referrer-policies with 'strict origin' and 'strict origin when cross origin' policies.

A brief description of the list of tasks assigned as part of the project is as follows:

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions

3) Implement strict-origin and strict-origin-when-cross-origin referrer policies (see determine_request_referrer and determine_policy_for_token)

4) Add support for the new strict policy values in the Referrer-Policy HTTP header (source)

5) Add tests for the new policy values in tests/unit/net/http_loader.rs (run with ./mach test-unit -p net)

=== Referrer Policies added in this project ===
==== Strict Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin Strict Origin] Referrer Policy dictates that the Referrer in HTTP header is always filled with the stripped URL of the origin and not the complete URL.

==== Strict origin When Cross Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin-when-cross-origin Strict Origin When Cross Origin] Referrer Policy dictates that the Referrer in HTTP header is filled with the stripped URL of the origin if the request is sent to a URL different from the origin and the complete URL is sent when making [https://en.wikipedia.org/wiki/Same-origin_policy same origin] requests.

== '''Implementation''' ==
Strict Origin and Strict Origin When Cross origin Referrer policy implementations have been added to the codebase. The pull request for Servo repository is available [https://github.com/rjain9/servo/pull/1 here] and Hyper is available [https://github.com/hyperium/hyper/pull/943 here]

Referrer policy implementation 
[[File:Ubs.jpg]] 
Selected Test case changes 
[[File:Ubs1.jpg]]

For complete changes please refer aforementioned url.

== '''Testing''' ==
Various testcase scenerios involving request from HTTP to HTTPS URLs and vice-versa have been added in [https://github.com/rjain9/servo/pull/1 tests/unit/net/http_loader.rs]. Full functionality coverage has been taken case of by ensuring that all same origin and cross origin test cases have been included.

CSC/ECE 517 Fall 2016/M1654. Improve network security features

2016-10-28T23:51:00Z

Rmuddur: /* Implementation */

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 

Servo supports standard [HTTP cookies] and parts of the Referral-Policy web standard. The project aims at increasing the security available to Servo browser users by implementing secure standards and complete the missing parts of the existing implementations. The project involves adding "strict" version of existing referrer policies.

=='''Introduction'''==

=== Rust ===
Rust is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.[https://doc.rust-lang.org/book/ title]

=== Servo ===
Servo is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== Referrer Policy ===
Referrer is a HTTP header field which contains the source of the URL that requested the web page. Referrer-policy dictates algorithm used to generate Referrer header when a new web page is requested.

=='''Project Description'''==
The project entails adding improved network security features for Servo engine by supplementing the existing Referrer-policies with 'strict origin' and 'strict origin when cross origin' policies.

A brief description of the list of tasks assigned as part of the project is as follows:

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions

3) Implement strict-origin and strict-origin-when-cross-origin referrer policies (see determine_request_referrer and determine_policy_for_token)

4) Add support for the new strict policy values in the Referrer-Policy HTTP header (source)

5) Add tests for the new policy values in tests/unit/net/http_loader.rs (run with ./mach test-unit -p net)

=== Referrer Policies added in this project ===
==== Strict Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin Strict Origin] Referrer Policy dictates that the Referrer in HTTP header is always filled with the stripped URL of the origin and not the complete URL.

==== Strict origin When Cross Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin-when-cross-origin Strict Origin When Cross Origin] Referrer Policy dictates that the Referrer in HTTP header is filled with the stripped URL of the origin if the request is sent to a URL different from the origin and the complete URL is sent when making [https://en.wikipedia.org/wiki/Same-origin_policy same origin] requests.

== '''Implementation''' ==
Strict Origin and Strict Origin When Cross origin Referrer policy implementations have been added to the codebase. The pull request for Servo repository is available [https://github.com/rjain9/servo/pull/1 here] and Hyper is available [https://github.com/hyperium/hyper/pull/943 here]

Referrer policy implementation 
[[File:Ubs.jpg]] 
Test case changes 
[[File:Ubs1.jpg]]

== '''Testing''' ==
Various testcase scenerios involving request from HTTP to HTTPS URLs and vice-versa have been added in [https://github.com/rjain9/servo/pull/1 tests/unit/net/http_loader.rs]. Full functionality coverage has been taken case of by ensuring that all same origin and cross origin test cases have been included.

File:Ubs1.jpg

2016-10-28T23:49:35Z

Rmuddur:

CSC/ECE 517 Fall 2016/M1654. Improve network security features

2016-10-28T23:47:03Z

Rmuddur: /* Implementation */

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 

Servo supports standard [HTTP cookies] and parts of the Referral-Policy web standard. The project aims at increasing the security available to Servo browser users by implementing secure standards and complete the missing parts of the existing implementations. The project involves adding "strict" version of existing referrer policies.

=='''Introduction'''==

=== Rust ===
Rust is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.[https://doc.rust-lang.org/book/ title]

=== Servo ===
Servo is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== Referrer Policy ===
Referrer is a HTTP header field which contains the source of the URL that requested the web page. Referrer-policy dictates algorithm used to generate Referrer header when a new web page is requested.

=='''Project Description'''==
The project entails adding improved network security features for Servo engine by supplementing the existing Referrer-policies with 'strict origin' and 'strict origin when cross origin' policies.

A brief description of the list of tasks assigned as part of the project is as follows:

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions

3) Implement strict-origin and strict-origin-when-cross-origin referrer policies (see determine_request_referrer and determine_policy_for_token)

4) Add support for the new strict policy values in the Referrer-Policy HTTP header (source)

5) Add tests for the new policy values in tests/unit/net/http_loader.rs (run with ./mach test-unit -p net)

=== Referrer Policies added in this project ===
==== Strict Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin Strict Origin] Referrer Policy dictates that the Referrer in HTTP header is always filled with the stripped URL of the origin and not the complete URL.

==== Strict origin When Cross Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin-when-cross-origin Strict Origin When Cross Origin] Referrer Policy dictates that the Referrer in HTTP header is filled with the stripped URL of the origin if the request is sent to a URL different from the origin and the complete URL is sent when making [https://en.wikipedia.org/wiki/Same-origin_policy same origin] requests.

== '''Implementation''' ==
Strict Origin and Strict Origin When Cross origin Referrer policy implementations have been added to the codebase. The pull request for Servo repository is available [https://github.com/rjain9/servo/pull/1 here] and Hyper is available [https://github.com/hyperium/hyper/pull/943 here]

Referrer policy implementation 
[[File:Ubs.jpg]]

== '''Testing''' ==
Various testcase scenerios involving request from HTTP to HTTPS URLs and vice-versa have been added in [https://github.com/rjain9/servo/pull/1 tests/unit/net/http_loader.rs]. Full functionality coverage has been taken case of by ensuring that all same origin and cross origin test cases have been included.

CSC/ECE 517 Fall 2016/M1654. Improve network security features

2016-10-28T23:46:49Z

Rmuddur: Added file

M1654: Improve network security features for Servo (cookies and strict referrer policies)
 

Servo supports standard [HTTP cookies] and parts of the Referral-Policy web standard. The project aims at increasing the security available to Servo browser users by implementing secure standards and complete the missing parts of the existing implementations. The project involves adding "strict" version of existing referrer policies.

=='''Introduction'''==

=== Rust ===
Rust is a systems programming language developed and maintained by Mozilla. It is used as a multi-paradigm, compiled programming language for creating highly safe systems. Rust can be used for a variety of jobs including and not restricted to embedding into other languages, creating modular and optimized programs adhering to space-time constraints and can also be used to develop low-level code for writing device drivers.[https://doc.rust-lang.org/book/ title]

=== Servo ===
Servo is a modern high-performance browser engine designed for both application and embedded use which is written in Rust. It is created by Mozilla Research and is being built by a global community of individual contributors and companies such as Mozilla and Samsung.

=== Referrer Policy ===
Referrer is a HTTP header field which contains the source of the URL that requested the web page. Referrer-policy dictates algorithm used to generate Referrer header when a new web page is requested.

=='''Project Description'''==
The project entails adding improved network security features for Servo engine by supplementing the existing Referrer-policies with 'strict origin' and 'strict origin when cross origin' policies.

A brief description of the list of tasks assigned as part of the project is as follows:

1) Compile Servo and ensure that it runs on tests/html/about-mozilla.html

2) Email the mozilla.dev.servo mailing list (be sure to subscribe first!) introducing your group and asking any necessary questions

3) Implement strict-origin and strict-origin-when-cross-origin referrer policies (see determine_request_referrer and determine_policy_for_token)

4) Add support for the new strict policy values in the Referrer-Policy HTTP header (source)

5) Add tests for the new policy values in tests/unit/net/http_loader.rs (run with ./mach test-unit -p net)

=== Referrer Policies added in this project ===
==== Strict Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin Strict Origin] Referrer Policy dictates that the Referrer in HTTP header is always filled with the stripped URL of the origin and not the complete URL.

==== Strict origin When Cross Origin ====
[https://w3c.github.io/webappsec-referrer-policy/#referrer-policy-strict-origin-when-cross-origin Strict Origin When Cross Origin] Referrer Policy dictates that the Referrer in HTTP header is filled with the stripped URL of the origin if the request is sent to a URL different from the origin and the complete URL is sent when making [https://en.wikipedia.org/wiki/Same-origin_policy same origin] requests.

== '''Implementation''' ==
Strict Origin and Strict Origin When Cross origin Referrer policy implementations have been added to the codebase. The pull request for Servo repository is available [https://github.com/rjain9/servo/pull/1 here] and Hyper is available [https://github.com/hyperium/hyper/pull/943 here]

Referrer policy implementation
[[File:Ubs.jpg]]

== '''Testing''' ==
Various testcase scenerios involving request from HTTP to HTTPS URLs and vice-versa have been added in [https://github.com/rjain9/servo/pull/1 tests/unit/net/http_loader.rs]. Full functionality coverage has been taken case of by ensuring that all same origin and cross origin test cases have been included.

File:Ubs.jpg

2016-10-28T23:45:03Z

Rmuddur:

File:Ubs.png

2016-10-28T23:32:55Z

Rmuddur: