Re: [tor-onions] Borg SSH could not resolve hosname

2021-03-01 Thread Tortilla



On Thu, February 18, 2021 9:11 pm, anan wrote:
> John Scott:
>> On Mon, 2021-02-08 at 01:49 +0100, anan wrote:
>>> Could not resolve hostname
>> What's happening is that Borg is trying to resolve the domain name on
>> its own instead of leaving Tor to do the job. This leaves traces for
>> your internet service provider (or whoever else resolves your DNS
>> queries), so if you need to keep the fact that you tried connecting
>> confidential, this should be taken seriously. Otherwise you may wish to
>> ignore it.
>>
>> Does the same message appear when using SSH?
>>
>>
>
> Hey, thanks for the answer!
>
> torsocks ssh works perfectly, I get no error message.
>
> Borg is supposed to use SSH for communication, so I don't understand why
> I get those name resolution errors. Borg does its job, it works ok
> through torsocks, but it shows those name resolution error messages.

In my experience, torsocks stopped being able to completely contain the
apps it wraps some time a number of years ago, but thankfully AORTA does a
better job. I never dove into the code or saw anyone explain why, but you
should try AORTA:

https://hoevenstein.nl/


___
tor-onions mailing list
tor-onions@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions


Re: [tor-onions] Borg SSH could not resolve hosname

2021-02-22 Thread anan
John Scott:
> On Mon, 2021-02-08 at 01:49 +0100, anan wrote:
>> Could not resolve hostname
> What's happening is that Borg is trying to resolve the domain name on
> its own instead of leaving Tor to do the job. This leaves traces for
> your internet service provider (or whoever else resolves your DNS
> queries), so if you need to keep the fact that you tried connecting
> confidential, this should be taken seriously. Otherwise you may wish to
> ignore it.
> 
> Does the same message appear when using SSH?
> 
> 

Hey, thanks for the answer!

torsocks ssh works perfectly, I get no error message.

Borg is supposed to use SSH for communication, so I don't understand why
I get those name resolution errors. Borg does its job, it works ok
through torsocks, but it shows those name resolution error messages.


PS. By the way, I originally sent my question to this list, but it was
never approved by the moderator (or there was another problem I don't
know), so then I sent my message to the tor-talk list and it was finally
approved there. But now I get an answer in this list, where my question
has never been published as far as I know...
I don't understand anything :)
___
tor-onions mailing list
tor-onions@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions


Re: [tor-onions] Borg SSH could not resolve hosname

2021-02-22 Thread dylan
This is an interesting find. Can you workaround this by using torsocks? 

-Original Message-
From: tor-onions  On Behalf Of John 
Scott
Sent: Thursday, February 18, 2021 10:02 AM
To: tor-onions@lists.torproject.org
Subject: Re: [tor-onions] Borg SSH could not resolve hosname

On Mon, 2021-02-08 at 01:49 +0100, anan wrote:
> Could not resolve hostname
What's happening is that Borg is trying to resolve the domain name on its own 
instead of leaving Tor to do the job. This leaves traces for your internet 
service provider (or whoever else resolves your DNS queries), so if you need to 
keep the fact that you tried connecting confidential, this should be taken 
seriously. Otherwise you may wish to ignore it.

Does the same message appear when using SSH?

___
tor-onions mailing list
tor-onions@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions


Re: [tor-onions] Borg SSH could not resolve hosname

2021-02-18 Thread John Scott
On Mon, 2021-02-08 at 01:49 +0100, anan wrote:
> Could not resolve hostname
What's happening is that Borg is trying to resolve the domain name on
its own instead of leaving Tor to do the job. This leaves traces for
your internet service provider (or whoever else resolves your DNS
queries), so if you need to keep the fact that you tried connecting
confidential, this should be taken seriously. Otherwise you may wish to
ignore it.

Does the same message appear when using SSH?


signature.asc
Description: This is a digitally signed message part
___
tor-onions mailing list
tor-onions@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-onions