cryptography

importaddress (and possibly other legacy-only wallet functions), when used on a descriptor wallet, return a fairly nondescript error:

$ ./bitcoin-cli -regtest importaddress test
error code: -4
error message:
This type of wallet does not support this command

The RPC help of importaddress doesn't mention nor further explain this incompatibility, nor what alternative to use inste

OpenSSL 1.1.1h introduces a behavior change wherein one can no longer set an EC_KEY's private_key to NULL.

This behavior changes in 6a01f6f4b41d045e2a3abcb10163633d769db76a. Based on the original PR (openssl/openssl#11127), it appears that this is hardening backported from 3.0.0 that unintentionally introduced a regression.

From https://github.com/openssl/openssl/comm

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.

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

Bumps jsdom from 9.12.0 to 16.5.0.

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.