As mentioned in #3854, Let's Encrypt now provides two different chains when acquiring a certificate: one with a cross-signed root certificate (default) and one with a self-signed root certificate.

I'd like to use the alternative chain, which seems to be possible using the preferred_chains option in Caddy. From what I'v

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

On my rpi4 (Linux liumeo-rpi4 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux), all test errors fixed now.

pi@liumeo-rpi4:~/github/radare2/test $ r2 -v
radare2 4.6.0-git 25454 @ linux-arm-32 git.
commit: 8c742b28f089385cd76fd6b7a35cb658eb911237 build: 2020-12-20__14:25:02
pi@liumeo-rpi4:~/github/radare2/test $ r2r -L
Skipping db/archos/linux-x64 because it does not ma

The upstream pull got closed. It is referenced in:

• driver/registry_base.go#L246

This issue was created by the ORY Closed Reference Notifier GitHub action.

🎉 Description

The ECDSA contract has a function toEthSignedMessage(bytes32), but we should have a function that works for any length of a bytes array:

function toEthSignedMessage(bytes s) pure internal returns (bytes32) {
  return keccak256(
    "\x19Ethereum Signed Message:\n",
    uintToBytes(s.length),
    s);
}

Where uintToBytes is implemented from an ideally