You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tricky, because who should resolve the DNS for covert? If it's the client, then we need to warn people that we're going to resolve DNS locally of the provided covert (censors could detect this). If it's the station, then people can issue DNS queries from our station...? Seems bad.
We generally provide IPs for covert addresses normally, but it would be nice to let the cli resolve for development purposes (perhaps with an appropriate warning)
The text was updated successfully, but these errors were encountered:
Providing a domain name causes some problems.
Tricky, because who should resolve the DNS for covert? If it's the client, then we need to warn people that we're going to resolve DNS locally of the provided covert (censors could detect this). If it's the station, then people can issue DNS queries from our station...? Seems bad.
We generally provide IPs for covert addresses normally, but it would be nice to let the cli resolve for development purposes (perhaps with an appropriate warning)
The text was updated successfully, but these errors were encountered: