privacyguides/i18n
1
0
Fork 0
mirror of https://github.com/privacyguides/i18n.git synced 2025-06-24 03:34:20 +00:00
Code Activity

New Crowdin translations by GitHub Action

Browse Source
This commit is contained in:
Crowdin Bot
2024-10-28 20:34:06 +00:00
parent 00dc94abd0
commit e4483be36c
58 changed files with 873 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

30
i18n/cs/about/jobs.md
View File

@ -9,4 +9,32 @@ We are occasionally looking for strong journalistic writers, product reviewers,
---
_We do not have any job openings at the moment._
## Open Positions
<div class="grid cards" markdown>
- :material-video-box:{ .lg .middle } **Content Creator**
---
Full-Time | Remote | \$20-$25/hour
[View posting :material-arrow-right-drop-circle:](jobs/content-creator.md)
- :material-file-document-edit:{ .lg .middle } **Journalist**
---
Full-Time | Remote | \$20-$25/hour
[View posting :material-arrow-right-drop-circle:](jobs/journalist.md)
- :material-comment-account-outline:{ .lg .middle } **Intern - Community/News**
---
Internship | Remote | \$15/hour
[View posting :material-arrow-right-drop-circle:](jobs/intern-news.md)
</div>

2
i18n/cs/advanced/dns-overview.md
View File

@ -12,7 +12,7 @@ When you visit a website, a numerical address is returned. For example, when you
DNS has existed since the [early days](https://en.wikipedia.org/wiki/Domain_Name_System#History) of the Internet. DNS requests made to and from DNS servers are **not** generally encrypted. In a residential setting, a customer is given servers by the ISP via [DHCP](https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol).
Unencrypted DNS requests are able to be easily **surveilled** and **modified** in transit. In some parts of the world, ISPs are ordered to do primitive [DNS filtering](https://en.wikipedia.org/wiki/DNS_blocking). When you request the IP address of a domain that is blocked, the server may not respond or may respond with a different IP address. As the DNS protocol is not encrypted, the ISP (or any network operator) can use [DPI](https://en.wikipedia.org/wiki/Deep_packet_inspection) to monitor requests. ISPs can also block requests based on common characteristics, regardless of which DNS server is used. Unencrypted DNS always uses [port](https://en.wikipedia.org/wiki/Port_(computer_networking)) 53 and always uses UDP.
Unencrypted DNS requests are able to be easily **surveilled** and **modified** in transit. In some parts of the world, ISPs are ordered to do primitive [DNS filtering](https://en.wikipedia.org/wiki/DNS_blocking). When you request the IP address of a domain that is blocked, the server may not respond or may respond with a different IP address. As the DNS protocol is not encrypted, the ISP (or any network operator) can use [DPI](https://en.wikipedia.org/wiki/Deep_packet_inspection) to monitor requests. ISPs can also block requests based on common characteristics, regardless of which DNS server is used.
Below, we discuss and provide a tutorial to prove what an outside observer may see using regular unencrypted DNS and [encrypted DNS](#what-is-encrypted-dns).