-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dbsc(e) #67
Dbsc(e) #67
Conversation
DBSCE/KeyGeneration.md
Outdated
@@ -0,0 +1,91 @@ | |||
### Local key helper on Windows | |||
|
|||
On Windows, a Local key helper is a COM class. A COM interface that the local key helper implements is TBD (working name for this document is ILocalKeyHelper) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is a COM class per domain? Or the same class registered for multiple domains? Could I use *.contoso.com in the example below on line 33?
DBSCE/KeyGeneration.md
Outdated
|
||
 | ||
|
||
When the browser needs to communicate with a local key helper. It uses its ID to locate the registry key, then reads the default value of this registry key and activates the object by the activation scheme (CLSID or ProgId according to the document). After activation it queries ILocalKeyHelper interface and invokes corresponding methods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"It uses it's ID" Is this a new sentence or should this be a continuation of the one before. We have a few IDs in the doc. CLSID, ProgId, LocalKeyHelperId, API Activation ID. I'm assuming here it's a match on the LocalKeyHelperId. We can also answer the matching question here. Could we register *.login.com and have it match www.login.com, foo.login.com, or just login.com?
- Steps 1-16 specify the key generation process for a public local key helper. The binding statement is expected to be short lived as elaborated in the [high level design](#high-level-design). | ||
- Steps 17-29 are [DBSC](https://github.com/wicg/dbsc) with additional parameters introduced with DBSC(E). | ||
|
||
 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe after conference, but I like coloring you've used in High Level design part, blue and black. IMHO, it was more readable.
SHA: ede2488 Reason: push, by sameerag Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: ede2488 Reason: push, by halflumi Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This PR adds to the existing DBSC proposal to address enterprise cookie binding.