![]() The 4 pinned servers have nothing to do with toxdns1, it's not possible to use toxdns1 anymore. It doesn't mean that only those 4 servers work, you can use any toxdns3 server with qTox, but we know the keys to these 4 ones and so we can pin them. The 4 pinned servers are toxdns3 servers, they are pinned so if somebody tries to compromise them and change the key, qTox will refuse to use them because it knows the real key. Why there is 4 servers hardcoded and why we can't use "tox1" dns requests. Yes, i see, they have 4 pinned servers ( ) ![]() You should use toxdns3 instead, and soon the better HTTPS version. It used to be possible, but toxdns1 has been removed because it's not secure for our users. So, in such case there is no way to force qTox check directly TXT records on my domain directly as "tox1"? Toxdns1 has already been removed, and the replacement for toxdns3 is almost ready. What we're going to do is deprecated (remove) toxdns1 and toxdns3, and replace them with a HTTPS version that always works, even through proxies. So qTox asks if you want to do the request anyways, but it can only do it outside the proxy. So if you have a proxy, you CAN NOT use toxdns1 or toxdns3 with it, because they need TXT records. It's not possible, it can't be made to work. It's impossible to request DNS TXT records through a proxy. So why qtox forcing me to disable proxy, send direct request to toxdns service which i do not run and don't want to install instead of simple request to server like toxv1? No more tox1 fallback - it's exactly what microsoft does with their skype, same style with "use it as is or go I was away this week, so let me answer your questions now. So i'm here in this issue, trying to understand "wtf is going on" with qTox. Everyone tells me that if i don't like something, i can rewrite it, but it's not a solution and 14 years ago last time when i've coded something on C, so. I feel myself like i've got pair of nice opensource shoes and now i see, that this shoes use only special cream from four another shops. But hard-coded servers - thats the 2nd bullshit (1st was no fallback on tox1 anymore, no more choice old users) about what i've spoken before. If they wanna keep tox as "all encrypted" system, lets do it. When tor1/tor2 it's a weak point of Tox - i'm agree. Hard-coding a small number of "known-good" ToxDNS servers just tries to mitigate the intrinsic problem, I suppose. Some of them (yes, except TXT in current tor realisation) can by-pass Tor. On a side note, could you please try to keep things a bit more polite? I understand that you feel very emotional about this - I really can relate to that ), but.ĭNS requests simply wouldn't be routed through proxy, thus they're disabled when qTox uses proxy. If you want to help with the situation, could you please create a distributed/decentralized, well-working way of finding/discovering ToxID by searching for "usernames" (or something) that would be implemented in toxcore, so that qTox, like other clients, could ~easily use it? So, hope, will explain for us kindly "what the fuck is going on?" with qtox.Ĭan't say anything in name, but the way I see things… What has changed, is correct way of handling DNS requests (so that they won't be sent outside of proxy and instead are disabled if proxy is in use) and removal of totally insecure and deprecated ~upstream toxdns1 and toxdns2. Note though that using ToxDNS at all is constituted by no apparent way of doing it well via distributed/decentralized means.Īlso, as always, PRs with additional servers were and will be accepted. When it comes to ToxDNS, you always had to run your own service or use someone's else. QTox doesn't force you or anyone to use them - you can always use Tox IDs. I see that qtox force people to use toxdns services on another websites or run yourself. DNS requests simply wouldn't be routed through proxy, thus they're disabled when qTox uses proxy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |