Regarding that Bitcoin Core switched to bech32 as the default format for addresses recently (with release 0.19.0.1), this should also be reflected in the RPC help texts. The change was already done for the RPCs getaddressinfo (commit bitcoin/bitcoin@2ee0cb3 by jonatack, PR bitcoin/bitcoin#17283) and `validateaddre

There's no published benchmark for IOPS on S3 storage

Would it be possible to post this alongside the other benchmarks?

S3 storage would be super cheap way to get started because it's serverless (thus more folks would potentially use gun.js)

Thank you for the useful service. I would like to see more Auth/ABAC for startup usage, right now I'm using a centralized database because it's uncle

I have read the documentation available here https://google.github.io/tink/javadoc/tink-android/1.2.2/com/google/crypto/tink/integration/android/AndroidKeysetManager.html

The documentation says the master key URI must start with android-keystore://. It is unclear if the URI must be unique (in device scope) or can two apps use the same URI without tampering each other's data?

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.

The rules for using go modules have changed in go 1.13.
When running go get from outside a directory with a module file, go reverts to pulling everything from head.

go get upspin.io/cmd/...
# golang.org/x/crypto/acme/autocert
go/src/golang.org/x/crypto/acme/autocert/autocert.go:76:16: undefined: idna.Lookup
go/src/golang.org/x/crypto/acme/autocert/autocert.go:263:15: undefined: i

At present, our tutorial notebook series is only available in English, but it would be very desirable for people to be able to learn PySyft in their native language, such as Japanese.

For this PR, copy the current notebooks and translate the inline text to Japanese, placing the notebooks in a "japanese" folder within the "tutorials" folder.

https://github.com/OpenMined/PySyft/tree/master/exa

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

Currently the lncli listinvoices --reversed flag has no effect, as it
is of type cli.BoolTFlag https://github.com/lightningnetwork/lnd/blob/ad0a89b844ec9f55b3ca4ddbb4d368dd8e3c0ea9/cmd/lncli/commands.go#L2848
which is true by default.

Correct behavior can be triggered by lncli listinvoices --reversed=True
or lncli listinvoices --reversed=False.

Is this behavior intended? I get th

Using latest version 0.15.0.1. (Edit : on Ubuntu 18.04)
After the CLI wallet was locked, the prompt showed the password in clear while typing.
I'm not a big CLI user so this happened only twice so far, but I thought it's worth reporting this issue.
Not sure if a screenshot is useful, but here's one below anyway.

![image](https://user-images.githubusercontent.com/16813929/72224145-2e286100-35

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                

tendermint debug tool can be used to continuously collect data. We haven't written any documentation/tutorials for it.

Write documentation and/or a mini-tutorial on how to collect profiling data continuously

Hi there,

First off thanks for all the work in building this - crypto is a PITA.

After reading your docs, I had the following questions, which I think would be useful to cover (or clarify) for other people in the docs:

1. Have any cryptographers reviewed this library? If so who - were they internal or a hired 3rd party - which part(s) did they review? Your docs appear to be asking for a

Migrated from internal issue RIPD-1031.

By convention, the account_lines method returns booleans for flags that are in their non-default states. In the vast majority of cases, this means it returns flags when the values are true and omits them when the values are false. The NoRipple flags of a trust

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

We can make Vuvuzela immune to passive traffic analysis by implementing Karaoke's optimistic indistinguishability. This mostly involves changing the Vuvuzela client to send 2 messages in every round and to do something reasonable when messages are dropped.

https://davidlazar.org/papers/karaoke.pdf

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.

ind_cpa_test_schema.json has a tagSize field, but this isn't used in aes_cbc_pkcs5_test.json and isn't [documented](https://github.com/google/wycheproof/blob/e91db8abc22df105a2bce5be452d49acd2804525/doc/types.md#indcpatestg

https://scotthelme.co.uk/a-new-security-header-feature-policy/

I guess it will be easy to add, because we certainly don't use any of these features.
Or maybe "gyroscope" or so may be used by the random number generator in sjcl, but that's all.

instead of keeping one solitary readme I the root folder, it would be better to add separate README to each folder.
what this would achieve would be that for someone interested in ciphers should open the folder and find details in the README specific to ciphers only.
This seems like an easy process of splitting the README into separate duplicates and then adding them to individual folders, I wou