Description

The description will be further updated.

There is a high CPU usage when SMTP and POP3 enabled in the configuration.
The high load disappears when both are disabled.

Additionally

It is necessary to check the behavior when switching on one by one.

Description

• It is necessary to use the OpenSSL EVP functions
• Sign, verify, set flag in <UID>.meta file

The description will be further updated.

Description

The Java version allows you to store a package for 100 days, if during this time the package has not been removed by a corresponding request upon receipt.
Need to add this logic to application, otherwise it will affect saving relevant new packages.

Necessary

• add removal of stored packages upon expiration of the retention period (100 days)

@majestrate raised very important question about the rationality of using BOOST in the project.
The project architecture allows us to replace BOOST with alternatives at this stage.

I prepared small table about used components:

Regarding BOOST in parts of libi2pd - these components are not used by the application and have been removed.

I'll post all latest changes soon.

At the moment, I see only one requirement for any BOOST alternatives:
users should not notice any changes and should not be required to make any changes themselves to be compatible with new components.

Decision will be made on the future fate of BOOST in the project after the discussion.

Let me know if anyone has ideas about it.

Thanks

Description

As it stands, the application allows you to add packages until the disk limit is reached.

Necessary

• add the corresponding parameter to the configuration
• add logic for processing packets after reaching the limit

Optional

• error handling when the disk limit is reached

Description

Apparently there is a difference in the name assignment when saving DHT data to files.
When reading the DHT key from the file name and converting it from base64 the names does not match.

Description

This class was rather crudely borrowed.

Necessarily

• Unused code must be removed (it will be added if necessary).
• Check anything that might interfere with the implementation of Ed25519.
• The class must be renamed to BoteIdentity.
• Loading and parsing of Bote Identity should be optimized whenever possible.

Description

Add ZLIB support to compress packages (preparing to remove LZMA support)

For greater security, it is necessary to add support for one of the post-quantum encryption and signature algorithms.

So far, only NTRU Encrypt/Sign support are in mind, because it was available for Java I2P-Bote applications.
It will also add backwards compatibility and allow users to more easily migrate to pboted.

Any proposed algorithms will be considered.
The decision to add will be made after discussion.

Description

At the moment, the application can only work over IPv4.

Necessarily

• Add support for IPv6
• Add correct error handling
• Add functionality to handle disconnection: re-create UDP sockets, re-create SAM session

Optional

• Consider using Boost instead of STL sockets
• Optimization

Description

The protocol allows to determine that the message has been delivered.
To do this, the presence of sent packets is checked on the closest nodes.
If the message is delivered (there are no packets for the bote identity) - the corresponding header is added to it.

False positive delivery is possible if the packages were removed after the expiration date.

Just officially requesting binaries for Debian Bullseye. Thank you for this consideration.