1. Environment

1a. Operating system and version

Manjaro 21.1.0 Pahvo (x86_64 Linux 5.4.135-1-MANJARO)

1b. Caddy version (run caddy version or paste commit SHA)

2.4.3

1c. Go version (if building Caddy from source; run go version)

1.16.6

2. Description

data race found

Caddy config:

{
	"admin": {
		"config":

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

r_anal_esil_pushnum uses snprintf, sdb_itoa is faster

Feature request

Feature description

The generated and installed config files permission are too open, any user logined on the system can read and write them. So i suggest append a chmod command into Extract tar step to keep config files more safty.

How the feature is useful

🎉 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

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.