The default behavior is unchanged, we remove some logging on things
like release builds, they simply don't get compiled in.
This feature is for people wanting to make a build with the libraries
including all levels of logging, while not compromising on something
like using a release build.
We parse a date/time for headers now with a specific
method that returns a QDateTime
We added a partial (incremental) download feature to avoid the need to
wait until completed. This also allows us to lower mem usage by spooling
to disk as data comes in.
We decided to avoid the stupid issue of looping infinitely on error by
forwarding past the end of the string on said error.
This now is reflected in the unit test too.
The server allows a wallet to store or restore wallet data, but it
requires the application to have access to the identity address of
the wallet.
So it should be made clear that we do NOT expect anyone to store
a wallet seed in here, as that would create a circular dependency.
Can't get the wallet-identity without the seed and thus without
the seed you can't find nor decrypt the actual file.
Boost now no longer wants header only sections to be added here,
presumably because we won't link to any library.
This fixes compilation against Boost 1.89
this matches the PrivateKey::signCompact and the
PublicKey::recoverCompact to handle all parts of compact (read:
recoverable) ECDSA type of signatures.
The server should keep some revisions and as such we put all revisions
together in a dir, and manage that per 'user'.
This deletes older revisions (keeping a max num of revisions per user)
and sets a symlink to the latest.
A rather simple server that allows POST uploads of small files that
have to be signed and owned by a bitcoin address.
The data embedded in this file is the backup of a (bitcoin cash) wallet.
Which should be made available by the wallet if it knows the address.
Prevent a trivial acceptor DoS in the network layer by never shutting down
the listener due to a single bad inbound socket (or banned IP). Instead we
close just that socket and keep accepting.
In NetworkManagerServerBase::acceptConnection(tcp::socket&&), two paths that
previously called shutdown() (which closes the acceptor) now only close the
offending socket:
- When an inbound connection is from a banned IP.
- When an exception occurs while inspecting the just-accepted socket (e.g.,
remote_endpoint throws because the peer vanished).
Patch is from John Galt.
This is a patch from John Galt to fix the problem that multiple
connections could end up getting settings from one connection
applied to the reply of another.
tomFlowee