Trusted Browser - Revision history

Tom: /* Problems */

2023-11-06T18:50:44Z

‎Problems

2023-11-06T18:49:54Z

‎Problems

2023-11-06T18:49:01Z

‎Problems

2023-11-06T18:47:25Z

‎Solutions

2022-05-27T00:03:34Z

‎References

2022-05-01T18:40:56Z

‎References

2021-02-10T17:24:06Z

‎References

2021-02-10T17:23:01Z

‎References

2021-02-10T17:15:00Z

‎Solutions

2021-02-10T17:13:46Z

‎Context

@@ Line 7: / Line 7: @@
 ==Problems==
 * The [[User Agent]] string provided by the browser in the HTTP header is used now simply to give the web server information on what sort of HTML it can process. It is routinely spoofed and has no security capability what-so-ever.
-* The makers of [[Smart Phone]] browsers are working to improve the security of the browser experience, details are shown in the following section. * Any user agents come with the ability to add extensions, which can [https://news.wisc.edu/from-to-ezacces-your-browser-extension-could-grab-your-password-and-sensitive-info/ compromise any security guarantee] provided by the developers.
+* Any user agents come with the ability to add extensions, which can [https://news.wisc.edu/from-to-ezacces-your-browser-extension-could-grab-your-password-and-sensitive-info/ compromise any security guarantee] provided by the developers.
 ==Solutions==

@@ Line 7: / Line 7: @@
 ==Problems==
 * The [[User Agent]] string provided by the browser in the HTTP header is used now simply to give the web server information on what sort of HTML it can process. It is routinely spoofed and has no security capability what-so-ever.
-* The makers of [[Smart Phone]] browsers are working to improve the security of the browser experience, details are shown in the following section. * Nay user agents come with the ability to add extensions, which can [https://news.wisc.edu/from-to-ezacces-your-browser-extension-could-grab-your-password-and-sensitive-info/ compromise any security guarantee] provided by the developers.
+* The makers of [[Smart Phone]] browsers are working to improve the security of the browser experience, details are shown in the following section. * Any user agents come with the ability to add extensions, which can [https://news.wisc.edu/from-to-ezacces-your-browser-extension-could-grab-your-password-and-sensitive-info/ compromise any security guarantee] provided by the developers.
 ==Solutions==

@@ Line 7: / Line 7: @@
 ==Problems==
 * The [[User Agent]] string provided by the browser in the HTTP header is used now simply to give the web server information on what sort of HTML it can process. It is routinely spoofed and has no security capability what-so-ever.
-* The makers of [[Smart Phone]] browsers are working to improve the security of the browser experience, details are shown in the following section.
+* The makers of [[Smart Phone]] browsers are working to improve the security of the browser experience, details are shown in the following section. * Nay user agents come with the ability to add extensions, which can [https://news.wisc.edu/from-to-ezacces-your-browser-extension-could-grab-your-password-and-sensitive-info/ compromise any security guarantee] provided by the developers.
 ==Solutions==

@@ Line 15: / Line 15: @@
 *New browser based on Blink
 *Align with some existing browser that want to be considered the best
-*Browser extension
+*Browser extensions can add features, but then are within the trust boundary. Then they are [https://news.wisc.edu/from-to-ezacces-your-browser-extension-could-grab-your-password-and-sensitive-info/ part of the problem.]
-*Read every image on the page to see if it should be considered a trustmark
+*Read every image on the page to see if it should be considered a trust-mark
 *New element, tag on img (attribute or method)

@@ Line 28: / Line 28: @@
 ==References==
-[[Category:Glossary]]
+[[Category: Glossary]]
-[[Category:Trust]]
+[[Category: Trust]]
 [[Category: User Agent]]

@@ Line 20: / Line 20: @@
 ==References==
-* See the wiki pages [[User Agent]] and [[Identifier use in Browsers]].
+* See the wiki pages for: [[Browser]], [[User Agent]] and [[Identifier use in Browsers]].
 *OWASP
 *[https://safebrowsing.google.com/ Safe Browsing (Google)]

@@ Line 3: / Line 3: @@
 ==Context==
-Currently nearly all HTTP traffic is initialized by 4 browsers, all of which are tracked within the
+Currently nearly all HTTP traffic is initialized by 4 browsers, all of which are tracked within the [blink-dev@chromium.org blink dev community]. The primary source code repos are chromium (Google) and web-kit (Apple).
 ==Problems==