There are some independent tests that can be added:

• Fix the TODO https://github.com/bitcoin/bitcoin/pull/18334/files#diff-a77567bbc57dc1bbc033560e5cdd3b7dR400 ✔️ Done in #18593
• Add a test for msg_mempool. (Create a tx before the peer connects, then connect, then send msg_mempool)
• Check that a new peer get's disconnected when Bitcoin Core doesn't have

Our current test suite includes KAT (known answer test) for many cryptosystems, including ECDH, EC_CDH and many KDF.

We are currently missing such KAT for ECDH (or the EC_CDH cofactor variant) in combination with KDF (as described by X9.63).

The ECDH+KDF codepath is currently used mostly by the CMS command and functions, but we have none to very limited support for testing the correctness of

I'm looking at the react tutorial at https://github.com/amark/gun/wiki/React-Tutorial and noticed that the code examples are using depreciated lifecycle methods such as componentWillMount.

Following the instructions on how to build tinkey I eventually got:

failed to create directory /home/username/.ccache/tmp: Read-only file system

Fixed by:

mkdir -p ~/.ccache
bazel build tinkey --sandbox_writable_path ~/.ccache

If applicable, maybe worth mentioning it in the docs at:

https://github.com/google/tink/blob/master/docs/TINKEY.md

Thanks.

It doesn't seem intuitive to me that Aes is a stateless object. You can create an instance of it with a BlockMode, which seems to imply to me that several encrypt/decrypt of the same data would produce different results each time.

If Aes is going to remain stateless, it would be nice to be explicity about this in the docs.

On the Signup page, the first thing a new Upspin user sees, we provide a link to the Overview before diving into a discussion of the tools. The Overview document itself is long and certainly not required reading to get started with Upspin.

We should add a short overview of the system to the Signup page, perhaps including th

Is your feature request related to a problem? Please describe.

OpenMined/PySyft#2498

Describe the solution you'd like

Solution: extend nn.Module() with a .parameters_and_statistics() iterator which will look for this kind of information so that we can make sure that federated learning properly moves everything from machien to machine.

**Describe altern

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

Background

This tripped me up longer than I want to admit. I accidentally set my tor.socks port to the same port as tor.control. When this happens, lnd simply hangs with no log messages at all, even with --debuglevel=trace. When trying to kill the process with Control+C you get a shutdown message but the process doesn't actually exit. You must do kill -9 to get exit the process.

[wallet 4XXXX]: help show_transfers
Command usage: 
  show_transfers [in|out|pending|failed|pool|coinbase] [index=<N1>[,<N2>,...]] [<min_height> [<max_height>]]
...

[wallet 4XXXX]: help export_transfers
Command usage: 
  export_transfers [in|out|all|pending|failed|coinbase] [index=<N1>[,<N2>,...]] [<min_height> [<max_height>]] [output=<filepath>]
...

"all" is missing among th

When there are several encrypted scripts on the site, each one contains functions rc4(), base64(), md5().
If you added the disable include option for these functions in the CLI, I could add them only to the first script.

There's no pure-JS OpenPGP (or crypto) library of similar quality.

The crypto really merits its own project, especially as many Node.js people are using rather poorly written alternatives.

See YahooArchive/end-to-end#32 for the parallel issue.

Summary

While Debug mode is turned on, the user may (unknowinly) leak data about the structure & content of the vault, e.g. clear text file paths. To remind the user that this can happen, we should add

1. an clear warning indicator in the main window and
2. add a pop-up message when debug mode is activated

Additional Context

The first time this idea was suggested was in #798

Problem:

From time to time we run into failures with dynamic record size tests.

https://travis-ci.org/awslabs/s2n/jobs/650075690?utm_medium=notification&utm_source=github_status

Running s2n dynamic record size tests

Cipher: AES128-SHA                   Vers: TLSv1.2  ... PASSED
Cipher: DHE-RSA-AES128-SHA           Vers: TLSv1.2  ... PASSED
Cipher: AES256-SHA                

The blockchain v2 reactor utilizes concurrency to saturate the bottleneck of writing blocks to disk. This concurrency is internal to the reactor where the reactor itself will launch and manage internal state machines running as go-routines. This configuration makes testing difficult as we don't know when messages processed by internal state machines will be processed and when we can assert that th

Preface: I am not an expert in encryption, so sorry for any inaccuracies with how I am describing the issue here.

In the documentation, it states:

// Note: CBC and ECB modes use PKCS#7 padding as default

Is it possible to configure what padding is used? I am working with a system where they are not expecting padding. Is that something that even makes sense/is possible?

Several issues with the configuration options for online_delete

1. There are several undocumented features for the [node_db] config section which can be used to tune online_delete performance. These need to be documented at least in rippled-example.cfg.
   • delete_batch - number of records to delete per query
   • backOff - milliseconds to sleep between deletes
   • `age_thr

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

Currently, with usernames, there isn't a good recovery mechanism for users that lose their keys. Originally we were thinking to let a user reset their account if they haven't extracted a key in 30 days (with no further verification), but this would lead to users losing their usernames if they go offline for an extended period.

With email addresses, we could at least verify that the user owns th

It would be great to have documentation on how to associate multiple keys + email id pairs in keybase and github for people using different account for open source and closed source work.

I noticed that when I upload a .exe file, the download page does not explain at all what I am about to download.

Perhaps it should read " Download attachment (abcd.exe , 2.3MB)"

If we wish to use the Wycheproof tests in another library, is it sufficient to create a README.md file in the directory containing the JSON files that includes the Apache2-required notice and copyright statement?