Skip to content
#

cryptography

Here are 3,926 public repositories matching this topic...

laanwj
laanwj commented Oct 29, 2019

boost::thread_group and its associated join/interrupt mechanism has no equivalent in any C++XX standard.

The interrupt mechanism is basically a condition variable, per thread group, that interrupts boost::this_thread::sleep_for and boost::this_thread::sleep and raises boost::thread_interrupted in the member thread when group.interrupt() is called.

Luckily, it's only used for three

GHLover
GHLover commented Aug 7, 2019

Clients that are built around the API need some additional information to work effectively. This is the following:

  1. Peer list API: show more information about connected peers including the block height / cumulative difficulty of the peer. Basically, so the API provides at least as much information as the server TUI does.

  2. Status information: Similarly, the minimum amount of info the stat

sako0938
sako0938 commented Oct 14, 2019

Background

The binaries are built with most of the build flags already set, but when building from source you must specify which tags are desired. This is an important step to building a usable binary from source.

These flags should be listed in the docs, with what their use is for the entire system, and whether or not excluding it would break the normal function of the system.

A sect

nbougalis
nbougalis commented Oct 7, 2019

We need rippled to improve its manifest support:

  1. A rippled instance configured as a validator should offer an admin-only RPC command that can report the master public key, the ephemeral public key, the manifest sequence number and, if present, the domain associated with the manifest that the server is using. The command can be validator_info. If the server is not configured as a valida
evilaliv3
evilaliv3 commented Sep 1, 2019

While experimenting within the Globaleaks application i just find out that the binding for SSL_CTX_set1_curves_list is currently not exposed.

This would be useful in order to define a preference on the order of the curves that should be used.

The feature would result particularly important especially for the fact that it seems that OpenSSL default order seems to be ```x25519, secp256r1, x448

You can’t perform that action at this time.