Onion-specific proxy not working #1465

New Issue

2019-05-28T16:47:02+02:00

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 ):

👍 1

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.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-02-20#1465