cryptography

The -datacarrier and -datacarriersize options were added in #3715 and #5077. Seems like those PRs did not add tests and we still don't have tests for them...? It should be easier to test things like this now with functional tests. I see -datacarriersize used in some places to create large transactions by stuffing outputs with lots of data but that's not very thorough. We should probably add

version: OpenSSL 1.1.1f

In the following code:

EVP_PKEY_CTX *pctx = NULL;
EVP_PKEY *pkey = NULL;
EC_KEY *eckey = NULL;
const BIGNUM *order;
BIGNUM *k = NULL;
BIGNUM *r = NULL;
int ret;

pctx = EVP_PKEY_CTX_new_id(EVP_PKEY_EC, NULL);
ret = EVP_PKEY_keygen_init(pctx);
ret = EVP_PKEY_CTX_set_ec_paramgen_curve_nid(pctx, NID_secp521r1);
ret = EVP_PKEY_keygen(pctx, &pkey);
eckey = p

Hey Hackers of this spoopy month! 👻
Welcome to the Ciphey repo(s)!
This issue requires you to add a decoder.

This wiki section walks you through EVERYTHING you need to know, and we've added some more links at the bottom of this issue to detail more about the decoder.
https://github.com/Ciphey/Ciphey/wiki#adding-your-own-crackers--decoders

https://www.dcode.fr/t9-cipher
https://en.wikipe

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

The unlock failed dialog does not show the correct drive letter.

What software is involved?

• O

ioutil.WriteFile doesn't sync the data to disk, so any data written with this function can easily be lost. It's even possible that only partial writes happen. Issuing an Fsync is a better alternative. There aren't many call-sites that do this and I wasn't able to evaluate whether any of these were critical, but better to be safe than sorry.

In working on informalsystems/tendermint-rs#1144, I see that the statesync.fetchers configuration option is serialized as a string. Does it need to be a string? It seems like it should be an integer value.

Currently stratumserver has no unit tests. This will improve the quality and allow future commits to be TDD safe. All units will be tested to ensure the module as a unit itself is tested.

Bumps jsdom from 9.12.0 to 16.5.0.

Issue Description

The instructions provided on failed jobs (example) don't clearly explain where to find the generated patch file. This can be a problem for anyone who is not familiar with how Github Actions pages are organized.

The general idea is:

From the details page, click on "Summary", then scroll down to the "Artifacts" secti

Problem:

A common pattern is:

GUARD(s2n_stuffer_skip_write(stuffer, bytes_to_write));
uint8_t* ptr = suffer->blob.data + stuffer->write_cursor - bytes_to_write;

which could be simplified.

Solution:

*ptr could be an *out parameter to s2n_stuffer_skip_write

• Does this change what S2N sends over the wire? No.
• Does this change any public APIs? No.