tor socks access issues continue (0.6dEV pYbm code @ 20170706)

[chan] bitmessage
Jul 8 14:21

Original Subject :: Peer "Ratings" Looks great, and now well on the way to having features to observe peer networking performance and connections like the most mature of torrent applications. Tempted once again to deploy a number of the new 0.6 (Dev track) github codebases using this. Just to see it in operation. But I rarely use direct clearnet conventional DNS access platforms to make connections that are obviously related to privacy ( and presumed piracy file sharing peer encrypted networks ) That interesting looking new status screen remains forever blank :-( Links to screenshots and newbie handholding setup suggestions to operate with (tor) socks please. I need references from known good not too hostile networks. From a Nation in the free world that doesnt use deceptive technical practices to limit access to the internet because it cannot publish laws openly to do so. And targets those law-abiding citizens technically capable of contributing without warrant for "special treatment" and observation. I am having terrible difficulties getting this to even connect behind any stock VM implementations using tor ( such as Whonix ). It just stubbornly refuses to startup within a sensible, safe timeframe : ( less than 20 - odd minutes ). My "best of breed" non asyncore earlier versions work just fine. On Public "Well managed" WiFi here, overt tor entries are rapidly funnelled down to one or two entry points that have been carefully selected. Depending on the traffic put through it at startup, to a small extent. The fantastic improvements in the older networking code around 3-4 months ago means that tor connection is usually achieved within 5mins of startup. Especially if other conventional - harder to deny - http traffic is running in parallel over the same tor connection. Thus a full many days absence sync of a BM client can come in well under the radar of a NOC that regards all encrypted peer connections as either undesirable - or to be network teleported to agencies equipped to defeat anonymity of those using them. Yes, I am aware that such behaviour may be seen as "leeching" and not contributing to the community benefit. But it is a legitimate need for a minority of well-intentioned lawful users asserting their human rights. Comments Please People. Honest operational data for comparison. Some recent commits to the asyncore default 0.6 codebases were supposed to bring limited socks capability. But I have no idea how to implement workarounds for issues as I have no clue about the low level operational coding tricks that have been employed. Case examples, and tutorials, would be extremely useful in gaining a wider tester base using PyBitmessage over tor networks. I run many variations of recent tordev codebases in addition to stable releases, examining network behavioural differences carefully. I raise the movie quote of a hard-pressed Brand New Technology Starship engaged in early battle before commissioning. From the Admiral present on the Bridge, used to the older, "just works" integration in combat situations... I'm sure that you know it. Trying to stay focussed on the core broader mission of network profiling; I cannot afford too many diversions into low level network programming detail in unfamiliar languages. Earlier scenarios suggest that it is always the pioneers that retire early: staggering out of the woods with arrows in their back. I have that feeling at a third attempt at using asyncore on anything other than clearnet. github 0.6 codebase as at end 20170706 It is unreasonable to tie down fast paced development with anal rules to document thoroughly every last reason for a commit. But maybe the coredevs need to find a documention guru former codedev happy to take on that role. Right now I'm SOL on figuring out why five attempts have all failed. Even tried a (recent) torsocks run in quiet desperation. After nearly every socks4a and socks5 configuration failed. Debug logs from PyBM and other logging is not helping much. Please save me from pcap dissection analysis. i just dont have the time for that. [ Snippage - removed link ]

BM-2cX62WCeFcUwzXWqxTBfaAzNy4j1y8yZVm
Jul 8 14:24

The development code is still being worked on and may not work for you at this moment. Have a nice day, Peter Surda Bitmessage core developer

[chan] bitmessage
Jul 8 23:10

Aye. Just discovered that applying previous advice to force non-asyncore network operation is equally futile. Pretty funky Critical errors. Sets, and pcaps for 20min sessions both socks5 (functions fine w/snapshot 20170325) - or socks4a. Standard Whonix workstation setting. Three different gateways used with different tordev and one stable 0.3.0.9-1 stable tried. Forgetting to revert the knownnodes.dat file going back will, of course fail the original pre asyncore codebase also ( any chance of sanity checks to fail gracefully? ) An entry for the snapshot date / last git commit etc migh be useful in event of mixing up the data files accidentally..

[chan] bitmessage
BM-2cWy7cvHoq3f1rYMerRJp8PT653jjSuEdY

Subject Last Count
peers Jul 26 11:36 4
© 2013-2016 The Bitmessage Developers Jul 26 07:12 6
0.6.3 Jul 24 20:52 3
Bug with chan creation Jul 24 10:15 12
Brute forcing BM addr's Jul 23 04:22 26
Network Size Jul 22 14:47 10
memory leak? Jul 21 06:19 3
BM bot sourcecode sample Jul 20 15:56 7
RE: BM bot sourcecode sample Jul 20 04:01 1
BitMessage need new improvements Jul 19 23:35 3
2 bugs while quitting Jul 19 19:03 1
[Feature Request/Question] Blacklist counters Jul 19 12:01 1
raspberry pi Jul 18 17:13 3
Feature request (2) Jul 17 00:44 13
Bug report (UI shows deleted messages) Jul 17 00:20 3
ECC Curves: secp256k1 versus secp521r1 -> BitMessage Secure Station Jul 16 22:18 1
PyBitmessage message save folder Jul 16 21:00 5
HELP(!) - Impossible PoW recipient address msg Jul 16 20:53 6
ECC Curves: secp256k1 versus secp521r1 Jul 16 20:44 28
Precedence of work / Priority of work Jul 16 20:43 5
I need help Jul 16 16:42 1
Pre-commitment and "open source canary" Jul 16 16:41 2
Killing impossible PoW sent items (daemon) Jul 16 16:40 1
Feature request (1) Jul 13 13:45 6
Bitmessage statistics Jul 13 09:42 13
addr command problems and plans Jul 13 06:19 7
BM client 0.6.2 (OS X) does not show images Jul 12 04:16 24
bug in latest commits Jul 11 08:46 11
Bitmessage bug in latest v0.6 branch Jul 11 06:09 1
bmwrapper broadcasts Jul 10 14:27 5
Beamstat chanlist bug? Jul 10 06:10 3
FPGA Hardware backdoors risk and counter-measures, regarding « TOR/VPN fingerprinting family anonymity breach fix » with a custom FPGA based « Single Socket » Ethernet Controller. Jul 9 11:36 1
tor socks access issues continue (0.6dEV pYbm code @ 20170706) Jul 8 23:10 3
FPGA Hardware backdoors, regarding « TOR/VPN fingerprinting family anonymity breach fix » with a custom FPGA based « Single Socket » Ethernet Controller. Jul 8 14:10 3
BM-2NB prefix ? Jul 8 13:30 3
Jabit and Abit update Jul 8 07:45 1
Peer "Ratings" Jul 7 12:54 9
How to.. Jul 6 18:01 42
Is there a quick way to export a thread, or all threads of a chan in a readable manner. Jul 6 04:00 6
Dev-talk PML status / instructions pls Jul 5 21:04 5
BM db blob questions Jul 5 07:40 11
How to connect to more nodes Jul 5 07:34 4
P.P.S. Re: BM db blob questions Jul 5 03:21 2
bitmessage API TTL Jul 5 01:08 2
Re: Re: Re: Re: Religious garbage at this point Jul 4 22:28 7
Yes it's obvious my BM private keys have been stolen.... Jul 4 22:20 22
MiNode I2P support testing Jul 2 07:04 25
To the person running /wire:0.1.0/bmd:0.0.1/ on 158.69.119.35:8444 Jul 1 12:55 9
So you think God is a myth ... Jul 1 12:14 1
How to.. (Node Conns Encrypted) Jul 1 10:17 1
Any predictions? Jun 30 12:24 2
Hello ! Jun 30 10:03 3
If I had cash Jun 30 09:56 3
"addr" commands Jun 29 22:14 2
How to.. (DNS issues and asyncore/conventional Network Access behaviour) Jun 29 13:03 3