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

[wip] Add "How to Create DNS Stamps" guide #262

Closed
wants to merge 3 commits into from

Conversation

grumaxxx
Copy link
Contributor

@grumaxxx grumaxxx commented Aug 4, 2023

Since AdguardTeam/DnsLibs supports checking the certificate hash from a DNS stamp, it is necessary to add instructions on how to create such stamps

@grumaxxx
Copy link
Contributor Author

grumaxxx commented Aug 4, 2023

Do I need to add screenshots from the DNS Stamp calculator?

@grumaxxx grumaxxx changed the title Add "How to Create DNS Stamps" guide [wip] Add "How to Create DNS Stamps" guide Aug 4, 2023
Copy link
Member

@ameshkov ameshkov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add this article to the DNS knowledge base:
https://github.com/AdguardTeam/KnowledgeBaseDNS

Add it to the Miscellaneous section.


This guide will help you learn how to create your own DNS stamp for Secure DNS. Secure DNS is a service that enhances your internet security and privacy by encrypting your DNS queries. This prevents the possibility of your queries being intercepted or manipulated by malicious actors.

By creating and using your own DNS stamp, you're taking an important step towards a more secure and private internet experience. This guide should equip you with the knowledge you need to generate your own DNS stamp confidently, whether for use in AdGuard, AdGuard VPN, or any other application that supports DNS stamps.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Слишком ChatGPT'шно, имхо :) Это совсем не important step, а опции для параноиков, если они хотят дополнительные меры безопасности :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For Secure DNS, tls://, https:// or quic:// URLs are normally used and it is enough for most users, and is recommended way.

However, if you need additional security, like pre-resolved server IPs and certificate pinning by hash, you may generate your own DNS stamp. This guide tells you how to do it.

2. Depending on the chosen protocol, select the corresponding protocol from the dropdown menu (DoH, DoT, or DoQ).

3. Fill in the necessary fields:
- **IP address**: Enter the DNS server's IP address. If you are using the DoT or DoQ protocol, ensure you have also specified the corresponding port.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Нужно отметить, что данное поле необязательно, и нужно использовать с осторожностью: использование данной опции может сломать интернет в IPv6-only сетях.


3. Fill in the necessary fields:
- **IP address**: Enter the DNS server's IP address. If you are using the DoT or DoQ protocol, ensure you have also specified the corresponding port.
- **Hashes**: Insert the SHA256 hash of the server's certificate. If the DNS server you are using provides a ready-made Ed25519 public key, find and copy it. Otherwise, you can obtain it by following the instructions in the ["Obtaining the Certificate Hash"](###obtaining-the-certificate-hash) section.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

А причём тут Ed25519? У TLS-сертов тип публичного ключа - ECDSA или RSA

Плюс нужно отметить, что данное поле необязательно.

@grumaxxx grumaxxx closed this Aug 4, 2023
@ameshkov ameshkov deleted the how_to_create_dns_stamps branch September 19, 2024 21:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants