Wirtschaftsuniversität Wien Magisterarbeit - SemanticLab

More documents

Recommendations

Info

Figure 6.4.: The privacy policy of yahoo.com does not match the users’ preferences Of course, users can also read the human-readable P3P policy of the website as shown in Figure 6.5 by clicking on the status icon. Webprivacy’s toolbar also offers a menu which is accessible by right-clicking on the status icon. There, Webprivacy’s preferences can be quickly accessed: Webprivacy can be disabled or enabled and Webprivacy’s cache can be cleared. Although it is not strictly P3P compliant, Webprivacy caches the results of each check for each domain during a browser session. This was implemented for providing a better user experience: because the P3P policy of a website does not have to be checked more than once per session, the results are available immediately. 64
Figure 6.5.: The privacy policy of p3ptools.org does match the users’ preferences 6.3.3. Issues Beside a good user-experience, P3P clients need to be as reliable as possible. However, the P3P standard also has to consider that other organizations or companies have different or more detailed requirements when it comes to expressing their privacy policies. That is why the extension mechanism was introduced to extend the P3P Base Data Schema as already discussed in Chapter 3. However, this raises the question how P3P clients such as Webprivacy should react to data-elements which are not in the Base Data Schema. IBM for example defines its own data schema for data it collects on its website such as the computers’ serial number when using the online services for IBM/Lenovo computers. Another issue was partly addressed in the previous section but should be dealt with in more detail. The problems of not well-formed policies or reference files which link to a non-existing P3P policy should be highlighted on the basis of two examples: • IBM.com: IBM has a P3P reference file in place at the well-known location, that is “www.ibm.com/w3c/p3p.xml”. Besides the issue that this policy reference file 65
Page 1:
Wirtschaftsuniversität Wien Magist
Page 4 and 5:
Contents Abbreviations vii Listings
Page 6 and 7:
II. Applied part 53 6. Development
Page 8 and 9:
Listings viii 3.1. HTTP response he
Page 10 and 11:
List of Tables x 3.1. PURPOSE sub-e
Page 12 and 13:
1. Introduction This thesis address
Page 14 and 15:
In addition, the applied part of th
Page 16 and 17:
2. Privacy Threats Privacy is the
Page 18 and 19:
term friendly fraud relates to legi
Page 20 and 21:
over iGoogle, search Wikipedia via
Page 22 and 23:
collect a lot of personal data abou
Page 24 and 25: 2.4. Privacy sensitive technologies
Page 26 and 27: • Data necessary to identify the
Page 28 and 29: 3. Privacy Standards The following
Page 30 and 31: The well-known location method (whi
Page 32 and 33: • User Preferences: User-agents m
Page 34 and 35: Another important issue for policy
Page 36 and 37: 1 M i c r o s o f t Way< /DATA> Red
Page 38 and 39: 28 PURPOSE Plain Language Translati
Page 40 and 41: Finally, an example should be provi
Page 42 and 43: • There is a commercial P3P polic
Page 44 and 45: Element Value ruling allow user cat
Page 46 and 47: 3.3.1. XACML - an introduction Simi
Page 48 and 49: 3.3.3. Summary The introduced priva
Page 50 and 51: specified conditions” [ISO01a]. T
Page 52 and 53: applied to this characteristic too,
Page 54 and 55: Figure 5.1.: Microsoft Internet Exp
Page 56 and 57: 5.1.2. Firefox The Mozilla Foundati
Page 58 and 59: shortcuts and context-menu, users s
Page 60 and 61: 5.3. Proxies In this section, proxi
Page 62 and 63: 52 Figure 5.10.: The settings dialo
Page 64 and 65: 6. Development of a Privacy Plug-In
Page 66 and 67: • components directory: this dire
Page 68 and 69: Speaking of information it has to b
Page 70 and 71: Figure 6.2.: Displaying the P3P pol
Page 72 and 73: matches the users preferences befor
Page 76 and 77: is different from the one available
Page 78 and 79: access elements in a policy which i
Page 80 and 81: implementation available although t
Page 82 and 83: [Dro06] Dennis Drotar, Rachel Green
Page 84 and 85: [Kob07] Alfred Kobsa. Privacy-enhan
Page 86 and 87: [Oli04] Nadia Olivero and Peter Lun
Page 88 and 89: [Woo06] Jisuk Woo. The right not to
Page 90 and 91: M i c r o s o f t i s a premier spo
Page 92 and 93: 82
Page 94 and 95: B. E-Mail correspondence Subject :
Page 96: the Thank you , Renukesh M i c r o
show all

Wirtschaftsuniversität Wien Magisterarbeit - SemanticLab

Create successful ePaper yourself

Delete template?

Save as template?