While ccxt does a great job unifying most functions / settings, not everything is or can be unified.
I think it would be good to provide a separate wiki/documentation page which documents exchange-specific properties.

The behavior is there now and all is working well - but to find it users need to search through issues (which are not easy to navigate) to find certain exchange-specifics - and o

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.

The C++ howto and //examples/helloworld/cc:hello_world target depend on //cc:cleartext_keytext_handle which does not have public visibility in Bazel. As far as I can tell it is not

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:

When you initialize a stuffer with an existing blob, the typical pattern is to write

struct s2n_blob blob;
struct s2n_stuffer stuffer;

GUARD(s2n_stuffer_init(&stuffer, &blob));
GUARD(s2n_stuffer_write(&stuffer, &blob));

This causes a memcpy to write to overlapping pages, which is undefined behavior. A workaround is to use s2n_stuffer_raw_write, but this st

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?

Currently, we only support sharing keychain items with Keychain Access Groups.

We should also support keychain sharing via App Groups.

More information on the differences between Keychain Access Groups and App Groups can be found in Apple's [documentation](https://developer.apple.com/documentation/security/keychain_services/keychain_items/sharing_access_to_keychain_items_among_a_collection_o

WARNING - A relative path to 'crypto / blockcipher / des-zh.md' is included in the 'nav' configuration, which is not found in the documentation files
WARNING - A relative path to 'crypto / blockcipher / mode / ofb-zh.md' is included in the 'nav' configuration, which is not found in the documentation files
WARNING - A relative path to 'crypto/asymmetric/discrete-log/ecc-zh' is included in the

Description

• Type: Bug
• Priority: Minor

Bug

This document should be updated and/or renamed now that mbed-crypto has been merged back in mbedtls.

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)"

See https://github.com/square/keywhiz/blob/master/server/src/main/resources/keywhiz-development.yaml#L49

It's a dropWizard thing, but we should document why it exists in Keywhiz and how to configure it (or link to the DropWizard docs).

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?

In line
https://github.com/square/go-jose/blob/643bdf8caec0de8a54ec3e8f8601d57992f35510/jwk.go#L112
if key is nil error message is
'square/go-jose: unknown key type '%!s()''
If change this line to
'return nil, fmt.Errorf("square/go-jose: unknown key type '%T'", key)'
then everything is OK. Message will be
'square/go-jose: unknown key type '''
From fmt package docs:
'%T a

The -s flag is very useful, on smaller terminals, to limit output.

Would it be possible to add a feature: ability to limit the coin price accuracy to a fixed amount of decimal places (or better yet, total digits - useful for low value coins)

Example: The current bitcoin price shows "6282.25189496", but just "6282" would be fine...

Note: The screenshot on Readme.MD shows bitcoin price limi

socket.cpp, socket_udp.cpp and cli/socket_utils.h have a lot of shared/duplicated code for handling differences in socket interface between BSD and Windsock. Consolidate into a single internal header which can be used across all three.

The tool should be smart enough to support reading pkcs8 private keys.

Ideally, we should support writing pkcs8 private keys if the user desires.

Include a script that can generate weekly status reports to dev's leadership. The report should have enough buzzwords to make leadership feel as if progress is being made without providing any specific detail that defines said progress.

This is a Feature Proposal

🎩 De

Expected Behavior

Leave the mountPoint directory mtime unchanged if no file operations are carried out in it

Actual Behavior

mountPoint directory timestamps are constantly changing

Steps to Reproduce the Problem

1. $ cryfs wdir1.cry workdir1 (answer: yes yes yes ...)
2. $ stat workdir1
3. $ stat workdir1
   ...

Specifications

• CryFS Version: 0.10.2+159.g87a253ad