Bitmessage/PyBitmessage-2025-03-01
Archived
2
0
Fork 0
Code Issues 167 Pull Requests 56 Actions Packages Projects Releases 5 Wiki Activity

Connection to local namecoind at startup #1146

New Issue
Closed
opened 2018-03-06 11:41:39 +01:00 by PeterSurda · 1 comment
PeterSurda commented 2018-03-06 11:41:39 +01:00 (Migrated from github.com)
Copy Link

When you launch PyBitmessage first time,
it says 'Bitmessage won't connect to anyone until you let it.'
But it seems that it has already attempted to connect local namecoind.

This is inspected by using torsocks:
torsocks $HOME/PyBitmessage/src/bitmessagemain.py

with keys.dat: namecoinrpchost = localhost

WARNING torsocks[9]: [connect] Connection to a local address are denied since it might be a TCP DNS query to a local DNS server. Rejecting it for safety reasons. (in tsocks_connect() at connect.c:192)

with keys.dat: namecoinrpchost =

ERROR torsocks[97]: Unable to resolve. Status reply: 1 (in socks5_recv_resolve_reply() at socks5.c:683)

It seems that namecoind support should be totally disabled by default
and activated later manually.

Tested on 0.6.3.2.

=-=-=-=-=-=-=
By the way, it failed to run PyBitmessage over torsocks.
It could not connect to anywhere.

ERROR torsocks[9]: Connection refused to Tor SOCKS (in socks5_recv_connect_reply() at socks5.c:549)
ERROR torsocks[9]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:533)

Of course, I usually use PyBitmessage through SOCKS5 to enable Tor.

When you launch PyBitmessage first time, it says 'Bitmessage won't connect to anyone until you let it.' But it seems that it has already attempted to connect local namecoind. This is inspected by using torsocks: torsocks $HOME/PyBitmessage/src/bitmessagemain.py # with keys.dat: namecoinrpchost = localhost WARNING torsocks[9]: [connect] Connection to a local address are denied since it might be a TCP DNS query to a local DNS server. Rejecting it for safety reasons. (in tsocks_connect() at connect.c:192) # with keys.dat: namecoinrpchost = ERROR torsocks[97]: Unable to resolve. Status reply: 1 (in socks5_recv_resolve_reply() at socks5.c:683) It seems that namecoind support should be totally disabled by default and activated later manually. Tested on 0.6.3.2. =-=-=-=-=-=-= By the way, it failed to run PyBitmessage over torsocks. It could not connect to anywhere. ERROR torsocks[9]: Connection refused to Tor SOCKS (in socks5_recv_connect_reply() at socks5.c:549) ERROR torsocks[9]: General SOCKS server failure (in socks5_recv_connect_reply() at socks5.c:533) Of course, I usually use PyBitmessage through SOCKS5 to enable Tor.
g1itch commented 2019-07-22 13:35:23 +02:00 (Migrated from github.com)
Copy Link

I assume it's fixed in #1146

I assume it's fixed in #1146
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Something isn't working as it's supposed to
build
Related to building or build system
dependencies
Pull requests that update a dependency file
developers
The issue is relevant mainly for developers rather than users
documentation
duplicate
enhancement
New feature
formatting
Code or UI text formatting
invalid
legal
mobile
Frontend for mobile devices (kivy)
obsolete
packaging
performance
protocol
Protocol change
question
refactoring
regression
Some issue, fixed in the past, appears again
security
test
translation
usability
wontfix
No Label
bug
Milestone
No items
No Milestone v0.6.4
Projects
Clear projects
No project
Assignees
Clear assignees
PeterSurda
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Bitmessage/PyBitmessage-2025-03-01#1146
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?