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

when calling EVP_PKCS82PKEY or d2i_PKCS8PrivateKey ...
added PBE algorithm call app is crash. After adding the new PBE algorithm.

because dynamic memory allocation in OPENSSL_malloc is return garbage value.
"pbe_tmp->keygen_ex" not initialized function pointer. so EVP_PBE_CipherInit_ex alway call
invalid pointer function keygen_ex.

if (keygen_ex != NULL) // always true

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

Custom shorteningThreshold during vault creation

Motivation

When creating a new vault it's not

Background

Postgresql backend would allow for very fast data access, by directly querying the database with your coding language of choice and a DB driver, instead of using lnd as intermediary with gRPC. This will need previous knowledge of things to look for in the database.
I did open the DB with an explorer, and the contents are... overwhelming to say the least.
I personally have no ad

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.

The custom parseUrl() implementation contains a potential edge case issue regarding the parsing of ports.

Consider the following group in the regular expression that determines basic acceptance of the URL: StringUtilities.cpp#L61-L62

 // optional port

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.

The mail option does not have a subject. It would be nice to have a customizable subject.

<a href="mailto:someone@yoursite.com?subject=themailsubjecthere">Email Us</a>