Currently the install_trust option for CAs from the pki module can only be configured via JSON/API.

Setting TLS to internal with option on_demand is easily possible with a Caddyfile and allows for a quick and simple internal setup. Trust store installation on the machine itself is not necessary and only leads to startup errors being logged from both sudo and caddy.

Therefore it w

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 Ubuntu 20.10 x64

sys/sanitize.sh
export ASAN_OPTIONS=detect_odr_violation=0
export LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libasan.so.6

Then run tests. Memory leak everywhere.

Either way, this is a nice-to-have, so it's not 100% necessary - just wanted to get the idea out there and looked at just in case a contributor comes along and wants to contribute. Happy to help when I have the time though!

Is your feature request related to a problem? Please describe.

When I'm testing the auth flow locally with the custom IdP I'm developing, I'd like for the token clien

🎉 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