Skip to content
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

Trust Model - Do not allow a service provider to provide text to a user #110

Open
pawel-kow opened this issue Jan 24, 2025 · 0 comments
Open
Assignees
Labels
IETF Issues reported from IETF process

Comments

@pawel-kow
Copy link
Member

pawel-kow commented Jan 24, 2025

Fri, 03 Jan 2025 09:32:42 -0800
Paul Hoffman

  • Explain the trust models. How does the DNS provider trust a service
    provider? How does the user know that the message asking them to change
    their DNS is actually from the service provider they interacted with
    earlier? How does the DNS provider know what RRsets and subdomains under
    a FQDN that the service provider can modify?
  • Do not allow a service provider to provide text to a user; this is a giant security hole because the service provider can give misleading text

[PK] This is well covered I think. Service provider can define its name and the name of its service which is a part of a template. This will be then secured by the DNS provider when onboarding the template. This will be described in the trust model section.

OK, I'll look to see how that gets improved. I am concerned if the service provide can say it's name is "Microsoft Inc." even when it clearly is not, or if a random service provider can name its service "General security update".

@pawel-kow pawel-kow added the IETF Issues reported from IETF process label Jan 24, 2025
@pawel-kow pawel-kow self-assigned this Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
IETF Issues reported from IETF process
Projects
None yet
Development

No branches or pull requests

1 participant