Jul 28 08:41
Up until recently I have been using MiNode_I2P as a bridge to connect via I2P, but about a week ago there was a major update in the BM source code, and now my BM will no longer connect to the MiNode_I2P software. Granny Smith could do with a bit of help to get it working again.
Jul 28 09:13
BM doesn't concern itself with being compatible with past versions of itself let alone other implementations. Just go back to what you were using before.
Jul 28 09:58
Have you tried changing what port PyBitmessage is listening on so it's different from the MiNode's?
Jul 28 11:41
I changed the port number in the settings, and now MiNode/I2P is working again. Is there an easy way to enable or disable all connections to clearnet?
Jul 28 11:52
>Is there an easy way to enable or disable all connections to clearnet? Forget I asked that. I can see now that my BM is only connected to my MiNode node at 127.0.0.1:8444, and to the I2P network. There doesn't appear to be any connection to clearnet. I have Tor installed on my computer, with SOCKS port 9050 and ControlPort 9051 enabled, but I have never been able to get my BM to connect to it. I have no idea if using I2P is any more secure than using To would be.
Jul 28 12:01
Bitmessage in trustedpeer mode will not connect to any other nodes, so this is safe. Minode hovewer will connect to clearnet nodes by default settings. Start minode with these keys if you wish to disable clearnet connections: start.sh --i2p --no-ip
Jul 28 12:04
> I have no idea if using I2P is any more secure than using To would be. In my opinion both are good enough as long as you are not specifically targeted by some government. BTW, accoding to this: https://geti2p.net/pl/comparison/tor I2P is more "Peer-to-peer friendly"
Jul 28 12:52
The command I was using to start MiNode was: sh i2p_bridge.sh --debug --i2p-tunnel-length 1 and I have changed it to: sh start.sh --i2p --no-ip I don't know if there enough I2P nodes to allow BM to work properly, otherwise I'll have to re-enable MiNode connections to clearnet.
Jul 28 14:24
Granny isn't very sure about this stuff, so here goes. Am I right in thinking that my MiNode is now relying on other MiNode nodes that are still connected to the clearnet to relay BM traffic back to my node, and into my BM client? I wonder, from the point of a nosy intruder, how visible and identifiable my BM traffic is now, and whether it can be traced to my real IP address. I assume that the NSA and GCHQ still know what colour pants I am wearing!
Jul 28 22:39
> Am I right in thinking that my MiNode is now relying on other MiNode nodes that are still connected to the clearnet to relay BM traffic back to my node, and into my BM client? Yes, some other minodes are connected both to i2p and clearnet. If they will shut down, you will stop to get messages sent from clearnet. > I wonder, from the point of a nosy intruder, how visible and identifiable my BM traffic is now, and whether it can be traced to my real IP address. I2P is anonymous, your traffic is encrypted and all BM traffic signatures should be lost. However some posts here in chans state that all modern PCs have hardware backdoors, and NSA can connect to your PC and read all memory and files.
|All green peers 127.0.0.1?||Aug 19 09:07||5|
|Chips without backdoors||Aug 18 19:10||4|
|New warnings in log||Aug 17 21:00||20|
|Yellow peers and green peers||Aug 16 20:59||4|
|cannot import name bmpow||Aug 15 12:36||2|
|Brute forcing BM addr's||Aug 15 07:58||4|
|Bitmessage crashes when posting||Aug 14 05:51||10|
|plz assist. are you a netcat or SSH tunnel guru?||Aug 14 05:01||4|
|shorter bitmessage addresses||Aug 14 04:56||14|
|Why Python?||Aug 13 10:45||16|
|Nerd Bully||Aug 13 05:17||1|
|Bitmessage not connecting||Aug 12 04:16||64|
|Feature idea||Aug 10 03:30||10|
|Local nodes won't connect properly||Aug 9 15:51||28|
|I do any thing in iran for BTC||Aug 7 15:36||3|
|Bitmessage feature request||Aug 7 12:50||4|
|query about short addresses||Aug 7 06:54||4|
|Curious||Aug 5 22:39||8|
|Full time nodes||Aug 5 13:50||9|
|changes to the dodobit server||Aug 5 11:05||2|
|Received Date||Aug 5 06:04||13|
|apinotifypath||Aug 4 06:04||9|
|BM <-> TOR||Aug 3 13:19||12|
|BM Bandwidth||Aug 2 14:11||11|
|When I try to register BM, collided with your key||Aug 2 13:51||12|
|Received Date||Aug 1 21:34||4|
|Bitmessage reminds me of ...||Aug 1 14:36||3|
|I need help||Aug 1 13:08||3|
|Response from Bitmessage Dodo Server||Aug 1 02:25||1|
|Streams and bloom filter||Jul 31 21:25||3|
|Questions about bitmessage streams||Jul 31 21:25||1|
|TTL question||Jul 31 08:03||3|
|API JSON index error||Jul 31 07:22||3|
|API question||Jul 30 11:22||7|
|MiNode||Jul 30 07:19||3|
|Yes it's obvious my BM private keys have been stolen....||Jul 29 19:50||2|
|Keys.dat options||Jul 29 04:56||3|
|Bitmessage and I2P no longer working||Jul 28 22:39||10|
|Connect Bitmessage only to .onion nodes||Jul 27 13:22||3|
|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|
|Network Size||Jul 22 14:47||5|