Onion-specific proxy not working #1465

Open
opened 2019-05-28 16:47:02 +02:00 by PeterSurda · 2 comments
PeterSurda commented 2019-05-28 16:47:02 +02:00 (Migrated from github.com)

Typos in the code, some places use onionproxy and others onion_proxy. It never worked.

Typos in the code, some places use `onionproxy` and others `onion_proxy`. It never worked.
g1itch commented 2019-08-01 14:26:40 +02:00 (Migrated from github.com)

I replaced onionproxy in 19ab56a. But I cannot imagine how to test that code ):

I replaced `onionproxy` in 19ab56a. But I cannot imagine how to test that code ):
PeterSurda commented 2019-08-02 21:31:21 +02:00 (Migrated from github.com)

Well, you could point the non-onion proxy to a port where there is no proxy running (or firewall non-tor connections), and set onion proxy to tor. You'll have to observe it manually and perhaps run a tcpdump in a separate terminal, as there is a chance of a false positive when interpreting the results simply from feedback of PyBitmessage, but for the time being that should be good enough.

Well, you could point the non-onion proxy to a port where there is no proxy running (or firewall non-tor connections), and set onion proxy to tor. You'll have to observe it manually and perhaps run a `tcpdump` in a separate terminal, as there is a chance of a false positive when interpreting the results simply from feedback of PyBitmessage, but for the time being that should be good enough.
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2024-12-07#1465
No description provided.