On 7/4/2018 4:05 AM, NIIBE Yutaka wrote:
Werner Koch wrote:
... on Windows. Actually I developed the fallback on Windows becuase
there it is easier to install the Tor browser. Anyway, Gniibe probably
found and fixed the problem in our DNS resolver. I suggest to wait for
the next release - pr
Werner Koch wrote:
> ... on Windows. Actually I developed the fallback on Windows becuase
> there it is easier to install the Tor browser. Anyway, Gniibe probably
> found and fixed the problem in our DNS resolver. I suggest to wait for
> the next release - probably next week.
That's not for Cy
On 06/29/2018 07:45 PM, Jacob Adams wrote:
> On 06/27/2018 04:50 PM, Jacob Adams wrote:
>> I've got another pinentry problem unfortunately.
>> The tty is owned by the correct user this time and $GPG_TTY is set
>> correctly.
>>
>> I have two gpgme contexts, one for openpgp and another for assuan
>>
On Mon, 2 Jul 2018 18:03, tookm...@gmail.com said:
> Should I file a bug against GPGME? GPG? Not really sure where the
> problem is here.
Against gpg. I won't assign it a high priority, though.
Shalom-Salam,
Werner
--
# Please read: Daniel Ellsberg - The Doomsday Machine #
Die Gedank
On Mon, 2 Jul 2018 21:22, dirk.gottschalk1...@googlemail.com said:
> localhost. This is not my intention. I have a running server in my
> network which rund Suid/Provoxy/TOR. Is it possible to connect to this
> tor server on the socks port for doing LDAP, WKD, or DANE Lookups?
No, this is curren
On Mon, 2 Jul 2018 20:46, johndoe65...@mail.com said:
> It looks like the code that is responsible for falling back to port
> 9150 when port 5090 is not available is somehow failing.
... on Windows. Actually I developed the fallback on Windows becuase
there it is easier to install the Tor brows