hashes | cryptographic hash functions written in pure Rust | Cryptography library

The referenced Python code uses P-384 (aka secp384r1) as elliptic curve. This is compatible with the WebCrypto API, which supports three curves P-256 (aka secp256r1), P-384 and P-521 (aka secp521r1), see EcKeyImportParams.

The following WebCrypto code generates a shared secret using ECDH and derives an AES key from the shared secret using HKDF. In detail the following happens:

• To allow comparison of the derived key with that of the referenced Python code, predefined EC keys are applied. The private key is imported as PKCS#8, the public key as X.509/SPKI. Note that due to a Firefox bug concerning the import of EC keys, the script below cannot be run in the Firefox browser.
• After the import the shared secret is created with ECDH using deriveBits() (and not deriveKey()).
• The shared secret is imported with importKey() and then the AES key is derived using HKDF, again with deriveBits().

|| is the or operator. It examines the left-hand-side for truthiness, not for definedness. For a binary operator that tests definedness, you want // (available since Perl v5.10).

More in perlop

The answer is it depends and it requires several trade-offs to be made for each project

• Performance: RedisJSON uses a tree structure for storing all elements in a document.
  • Comparing to a string: the advantage is that updating sub-elements of a document will be faster than manipulating a string containing a serialised JSON object. But retrieving (reassembling) and writing the entire document will be more expensive compared to Strings. Read more here.
  • Comparing to Hash: when manipulating a flat document (1 level deep), RedisJSON and HSET performance are comparable.
• Maintainability: using several native data types in Redis to represent your object can be really performing, but the code will be more complex to maintain. There can be additional migration/refactoring work when the structure of the document is altered.
• Querying: RediSearch will soon add support for indexing and querying the content RedisJSON documents. This is, of course, if your use case requires secondary indexing and querying documents other than with their key. You can still build your own secondary indexing with Redis data structures, but this is also a trade-off in maintainability

disclaimer: I work for RedisLabs, creator and maintainer of RediSearch and RedisJSON

Use

It is well written in the documentation;

Implementation

Fernet is built on top of a number of standard cryptographic primitives. Specifically it uses:

• AES in CBC mode with a 128-bit key for encryption; using PKCS7 padding.
• HMAC using SHA256 for authentication.
• Initialization vectors are generated using os.urandom().

For complete details consult the specification.

Therefore you cannot use AES-256 with Fernet

• Cryptography.io library has other modes too, in the hazardous material layer including CBC, CTR, and GCM for AES-256, too.

PyCrypto can use a wide range of mode of operations for AES-256 including CBC, CTR, GCM, SIV, and OCB

Not clear how you get 44 bytes, here is the way to get the 32-bytes;

AFAIK.. Reviewboard doestn't just display/highlight "uploaded diffs". It needs a local (back-end) repo, and displays the changes as diffs against this repo. As such, it needs to have in its local repo the base commit that you're diffing against. You can post C1..C3 because the back-end repo has C1's parent C0. But you can't post C2 or C3 on their own because RB does not have their parent in its db.

If the decimal aren't important, you could try something like that:

something like this will replace: "answer"=>"0" with "answer"=>"Yes" and return updated answers hash

Use .hex() on a bytes object to get a str value suitable for a CSV, and .fromhex() on that str to get bytes again: