cryptography

I accidentally -torcontrol=1 today (instead of -listenonion=1) and was confused that it was accepted, as the argument needs to be host:port.

Expected outcome would be an error message and exiting.

Useful skills:

• C++
• Understanding of bitcoin core's initialization sequence

Want to work on this issue?

For guidance on contributing, please read [CONTRIBUTING.md](http

I'm using a /etc/cron.daily/ file that does:

#!/bin/sh

BITS=4096
GENERATOR=-2

openssl dhparam -out /etc/pki/tls/misc/dhparam.pem.new \
		$GENERATOR $BITS > /dev/null \
	&& mv -f /etc/pki/tls/misc/dhparam.pem.new /etc/pki/tls/misc/dhparam \
	&& apachectl restart

to generate daily dhparam files which I then use in ssl.conf as:

SSLOpenSSLConfCmd DHParameters /e

What about create a design pattern directory with the most popular design patterns examples?
We can create some rules like: have to be an explanation about the design pattern, the structure and one real world example.
The directory can be:

(folder) Design Patterns
-- (folder) Abstract Factory
-- -- AbstractFactory.js
-- -- AbstractFactoryTest.js
-- -- REAME.md

I can send some :

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

Background

Inspired by C-Otto/rebalance-lnd#241.

As part of pathfinding, lnd might encounter edges that have a policy specifying a zero CLTV delta (possibly because of no/outdated gossip?). Every time an edge like this is used in the pathfinding code, a warning is logged: https://github.com/lightningnetwork/lnd/blob/290b78e700021e238f7e6bdce6acc80de8d0a64f/routi

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

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.

As I was running composer to install a new library into our repo, it warned me that:

Package yzalis/identicon is abandoned, you should avoid using it. No replacement was suggested.

I'm not familiar on what packagist.org's process is to declare a package abandoned. I see that the last commit in their repo is from 2019 and there are a number of unanswered issues and pull requests.

I