Difference between revisions of "Trust Service"
From MgmtWiki
(→Reference) |
(→Problem) |
||
| Line 5: | Line 5: | ||
*Any [[Web Site]] that wishes to acquire [[User Information]] should first present [[Assurance]] as to their trustworthiness to the [[User]]. | *Any [[Web Site]] that wishes to acquire [[User Information]] should first present [[Assurance]] as to their trustworthiness to the [[User]]. | ||
==Problem== | ==Problem== | ||
| − | + | *There are few functional trust services today, for example: | |
| − | + | #DOI | |
| + | #DNSSEC | ||
==Solution== | ==Solution== | ||
Revision as of 10:48, 15 November 2018
Full Title or Meme
Any Web Site that reports on the depth of support that other sites or documents have for the principles of the Framework Profiles that they claim to support.
Context
- Any Web Site that wishes to acquire User Information should first present Assurance as to their trustworthiness to the User.
Problem
- There are few functional trust services today, for example:
- DOI
- DNSSEC
Solution
Compare with other solutions like:
- Attempts to make a trusted connection from a user to Web Site have included EV Certs and other attempt to over come the failings inherent in trusting any connection based on the URL have all failed. See the page Bearer Tokens Considered Harmful for details.
- Create a Trusted Identifier as a URN for web sites and then bind the token to that URN.
