Describe mitigations for homoglyph/typo-squatting attacks and name duplication #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
scouten-adobe
changed the title
Closed
puhley
reviewed
Jul 8, 2024
docs/modules/ROOT/pages/index.adoc
Outdated
| @@ -904,11 +904,22 @@ Any content including, but not limited to the _<<_named_actor,named actor’s>>_ | |||
|
|
|||
| The effectiveness of such attacks will necessarily be dependent on the language and other related development tooling in use for any given implementation. Beyond reminding implementors that parsing and validation errors are a likely attack surface, it is outside the scope of this specification to provide language-specific guidance. | |||
|
|
|||
| ==== Homoglyph and typo-squatting attacks | |||
| ==== Homoglyph and typo-squatting attacks and name duplication | |||
There was a problem hiding this comment.
"Name collisions"? - Duplication suggests putting it twice?
There was a problem hiding this comment.
Speaking of putting things twice, I just realized we have an existing "Name collisions" section. I've cross-referenced the two sections and removed this part of this header.
scouten-adobe
commented
Jul 9, 2024
| @@ -892,7 +892,7 @@ NOTE: The above questions target name collisions for individuals, but the same q | |||
|
|
|||
| Whether a name collision is intentional or coincidental, careful attention should be paid as to how to gather the appropriate technical details to allow differentiate distinct _<<_named_actor,named actors>>_ and to meaningfully expose that differentiation in user experience. | |||
|
|
|||
| NOTE: TO DO (link:https://github.com/creator-assertions/identity-assertion/issues/115[issue #115]): Think through identity presentation so as to provide meaningful differentiation between similarly-named _<<_actor,actors>>._ | |||
There was a problem hiding this comment.
Removed this TO DO link since we moved #115 to post-1.0 milestone.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #117.