Currently peer-to-peer communication occurs over insecure sockets. Wrapping these sockets in SSL is done via ssl.wrap_socket, the resulting object has most of the same methods as a standard socket.

Each peer could generate and self-sign a certificate and be configured to accept any certificate that it is presented. (We don't really care who we're connecting to as long as its over a secure channel, for now)

Bitmassage uses over 1GB memory. It might be caused by a ton of threads for many connections. I suggest using "gevent" to reduce the number. Thank you.

On my Xubuntu 12.10 with xfce-desktop sometimes (not always) pyBitmessage causes a python process that uses 100% of one complete CPU:

#ps aux|grep bitmes

ruben     2703 88.3  1.7 1870944 70304 ?       Sl   20:44  19:14 python bitmessagemain.py

If I close the GUI, that process stays and continues to waste the CPU

only

#kill -kill 2703

stops bitmessage and releases the CPU

setup.py is interactive, so it's broken for any distro that your script doesn't automagically detect. Why does it even attempt to do that? Setuptools and distutils are distro-agnostic.

• setting BITMESSAGE_HOME doesn't always work, so we wrote a function to do this
• logger and BMConfigParser now clear old config when loading new
• add method for flushing log files
• rework logic in test_logger
• detect thread names on UNIX-like OSes
• be more accurate when starting or stopping a process, better waiting mechanisms
• add extra cleanup during TestProcess start

Recent distributions like Debian bullseye don't support QT4 anymore. This pull request provides a flatpak-builder configuration and instructions how to package PyBitmessage as a flatpak application which bundles QT4.

This pull request is also a necessary requirement for https://github.com/Bitmessage/PyBitmessage/issues/1607

Hello!

This is an appeal to contributors: write more pythonic code! Please read PEP8 carefully and don't trust linters bugs.

About 79 characters line length limit, I repeat it here: readability has nothing to do with your screen size.

Not sure is it correct to add symlink into repository. Some setuptools commands wont work without it.

memory overflow at 1.79gigabytes ram consumption on windows 32bit machine running provided latest win32 binary of bitmessage.exe

bitmessage.exe recently crashed during runtime with qt4...dll gui or similar, and now never starts up any more in the end, as it crashes with unknown memory error whenever it is started up now and taskmanager and other process related tools show that its memory consumption grows up til exactly right below 1.8gigs of ram then it gives this crash. reproducable.

some days ago I think there was a post on the general channel public shared address list talking exactly about this phenomenon back then already

apparently now its happening for me.

bitmessage must not read the total database and keep too many objects in ram, but should only read the database if needed and not store too many objects in ram.

It appears that the current implementation of PyBitmessage does not support sending of messages to yourself, or other addresses that you own. (within the same client instance) When I comment this section of the code out, the client hangs on "Sending public key request. Waiting for reply."

What type of development needs to be done in order to support this? Email and Bitcoin both support sending to your own address(es), thus I think we should enable this for Bitmessage.

Thoughts?

• [x] Application Indicator This provides access to key features of Bitmessage.
  • [x] mono icon (compare /usr/share/icons/ubuntu-mono-dark/status/24)
• [x] Messaging menu The entry could look like this:
  • Pybitmessage
    • New message
    • Contacts
    • 1 new message (from John Doe)
• [x] Launcher shortcut This is very easy to implement when the application supports command line options.
• [x] Notify OSD This informs the user about new messages and connection loss.
• [x] Most importantly, Ubuntu users have no easy way to install Pybitmessage. Even though it may be too early to get Pybitmessage into the Debian repositories, there are several options to make it more convenient to install this application:
  • Provide a single official .deb file
  • Provide a portable statically linked executable
  • Provide a PPA

On my system UPnP doesn't work. UPnP is checked, some port (18XXX) is specified, but UPnP page on the router never shows bitmessage. It does show ZeroNet and Skype, just not bitmessage.

FreeBSD 10.3

(Before I was running with manually opened port and it worked fine.)

A user wanted to use HandleDisseminatePreEncryptedMsg API call and it didn't appear to work. After reviewing the code and specification, it looks like when decoding destination stream:

https://github.com/Bitmessage/PyBitmessage/blob/a5a56fe7f1af86f5b8c40ee7d6307df62e0e6b3e/src/api.py#L1313

it uses a protocol v2 specification, and not protocol v3. In v2, the offset for the stream for a message starts at byte 16, but in v3 it starts at a variable position (at the moment it usually is byte 21, which allows for a quick workaround). This API method was introduced around the same time that v3 came out so I guess someone wasn't paying attention.

References: v2 specification from wiki: https://wiki.bitmessage.org/index.php?title=Protocol_specification&oldid=23575#msg v3 specification from rtd: https://pybitmessage.readthedocs.io/en/v0.6/protocol.html#object

jsonrpclib throws errors sometimes due to the auto-generated labels that are based on the passphrases I set. Example:

(-32603, '<class 'api.APIError'>:API Error 0021: Unexpected API Failure - bad interpolation variable reference '%(793569%(4"]'')

This "%(793569%(4"]" is a substring of my label that's based on the passphrase and the error prevents any data from being received.

Because the passphrases I use are generated in a specific way, I can't just exclude certain character combinations as possibilities. Therefore, I propose adding the ability to set the label at the time of the chan creation, which will allow me to set the label to something different/safer than the passphrase.

Bumps kivymd from 1.0.2 to 1.1.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.