jedisct1

55 ms·

751.
by jedisct1 7y ago
Unfortunately, Wireguard will not work if you are not on a network where only TCP ports 80 and 443 are open. For these, you can try DSVPN, which is even easier than Wireguard to set up: https://github.com/jedisct1/dsvpn
752.
by jedisct1 7y ago
This.
753.
by jedisct1 7y ago
Indeed, a traditional camera with the post-processing of a smartphone would be incredible. But indeed, camera manufacturers are way way way behind. The best they can do at the moment is find faces on a picture (and still, not that well exce
754.
Go Is the New Ruby(00f.net)
105 points by jedisct1 7y ago|59 comments
755.
by jedisct1 7y ago
Which is good. I don't want a browser to bypass DNS settings to use something else instead. Especially since DNS encryption and anonymization is already done on the router for the whole network.
756.
by jedisct1 7y ago
There are many encrypted DNS servers outside the US: https://dnscrypt.info/map
757.
by jedisct1 7y ago
And at the same time, they deployed a DoH server: https://github.com/DNSCrypt/dnscrypt-resolvers/blob/master/v...
758.
by jedisct1 7y ago
Get a VPS and run your own VPN. It doesn't have to be complicated: https://github.com/jedisct1/dsvpn
759.
by jedisct1 7y ago
Not much any more, with load balancers/geo routing/CDNs generating ephemeral host names, and everybody using very low TTLs.
760.
by jedisct1 7y ago
DNSCrypt uses the standard DNS mechanism, and just encrypts the content beforehand. Quick one-off requests. No handshake cost. It uses UDP, or TCP for large responses, exactly like standard DNS. In fact, it can even share port 53 with stand
761.
by jedisct1 7y ago
A little bit. I run some public DNS servers.
762.
by jedisct1 7y ago
Still here, still what most public secure DNS run, still secure and reliable, still being constantly improved, and new implementations keep being written. https://dnscrypt.info The protocol was recently extended with Anonymized
763.
by jedisct1 7y ago
Which is supposed to be replaced by https://github.com/withoutboats/fehler
764.
by jedisct1 7y ago
The `randombytes_deterministic()` function from libsodium or libhydrogen does exactly what the name suggests.
765.
by jedisct1 7y ago
How multitasking used to work on Atari :) But this requires code pages to be writable. Which, from a security perspective is awful.
766.
by jedisct1 7y ago
Same here. My Canon scanner is not going to work any longer. And Canon is notoriously bad at updating their drivers, so my scanner will now be a brick.
767.
by jedisct1 7y ago
dsvpn https://github.com/jedisct1/dsvpn
768.
by jedisct1 7y ago
I use a bitbar module for this: https://github.com/jedisct1/bitbar-dnscrypt-proxy-switcher/
769.
by jedisct1 7y ago
You can adds DNSCrypt support to pdnsd, simply by installing https://github.com/jedisct1/encrypted-dns-server - In `upstream_addr`, instead of `9.9.9.9:53`, just put the IP and port of your pdnsd server.
770.
by jedisct1 7y ago
Yandex Browser has been supporting encrypted DNS since 2016....
771.
by jedisct1 7y ago
Hi! The GitHub repository for dnscrypt-proxy was simply moved from my personal GitHub account to the DNSCrypt organization. GitHub automatically adds redirections when a project is moved, so this should be transparent. dnscrypt-proxy 2 is a
772.
by jedisct1 7y ago
And to run your own encrypted DNS server: https://github.com/jedisct1/encrypted-dns-server
773.
by jedisct1 7y ago
It doesn't work any more on Raspberry Pi.
774.
by jedisct1 7y ago
To avoid centralization, help deploy more independent resolvers: https://dnscrypt.info/ And for more privacy, we will soon need DNS relays https://github.com/DNSCrypt/dnscrypt-protocol/blob/ma
775.
by jedisct1 7y ago
It's just an ad for Cloudflare.
776.
by jedisct1 7y ago
Indeed, we will need to make a choice between minimizing latency or using a relay. But a lot of people use DNS over Tor already. For people concerned about privacy, a bit of extra latency is totally acceptable. Anonymized DNSCrypt is lighte
777.
by jedisct1 7y ago
The underlying DNSCrypt protocol does the padding already: https://dnscrypt.info/protocol DNS queries and responses are wrapped, they are never modified. EDNS padding is a horrible hack.
778.
by jedisct1 7y ago
At the end, you still need to trust the resolver. There is a proposal to improve this. Resolves won't know client IPs any more: https://github.com/DNSCrypt/dnscrypt-protocol/blob/master/AN... Refere
779.
by jedisct1 7y ago
A really good presentation on the privacy implications of "modern DNS" by PowerDNS https://www.youtube.com/watch?v=V2F92orIEO8
780.
by jedisct1 7y ago
There are many more secure public resolvers than Google and Quad9 : https://dnscrypt.info/public-servers

More ›