Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
    Oussama Chaabouni
    hello . i am trying to start ethsigner after creating the password file and the key file ... but he sait that file password is not found althought i am sure that the path is true , it s in the same path of the key file
    that s my error
    2020-05-31 17:53:19.655+02:00 | main | INFO | SignerSubCommand | Version = ethsigner/v0.6.1-dev-82352575/linux-x86_64/oracle-java-13
    2020-05-31 17:53:19.669+02:00 | main | ERROR | FileBasedSignerFactory | File not found: /config/password
    Failed to construct a signer from supplied arguments.
    Cause: File not found: /config/passwor
    Oussama Chaabouni
    now he gace me this error
    020-05-31 18:48:22.623+02:00 | main | INFO | SignerSubCommand | Version = ethsigner/v0.6.1-dev-82352575/linux-x86_64/oracle-java-13
    2020-05-31 18:48:23.515+02:00 | vert.x-eventloop-thread-2 | ERROR | HttpServerService | HTTP server service failed to listen
    java.net.BindException: Adresse déjà utilisée
    Oussama Chaabouni
    can someone please explain to me how to use ethsigner ... i juste want to interact with my contract via a script node js .. trying to execute a function of my contract vi eth.send ... but he said to me that i must use sendRawTransaction .... i am using Besu on localhost:8545
    Trent Mohay
    Hi @oussamachaabouni, from the initial log, it looks like the /config/password file is indeed missing - can I ask you to rerun ethsigner, but with "-l trace" in the command line? That will provide much more information regarding the issue.
    With regard your second issue - I'm suspecting that the port you've requested (defaults to 8545) is already in use, and the HTTP server is unavailable. Have you set the --http-listen-port on the EthSigner commandline?
    Oussama Chaabouni
    thank you , your answer help me to understand my problem . actualy i am just trying to interact with my contract , i want to call a set function to add some infomation in my contract ; i am using web3.js library
    Trent Mohay
    If you ensure that the ethsigner port is free - does it now work? If need be - you can set "--http-listen-port=0", then a file called ethsigner.ports will be created, and will show which free ports were selected by EthSigner for listening on.
    Manuel Montenegro

    Hi! I have a problem that I'm unable to resolve... I'm trying to connect Remix (Web3 provider) to EthSigner, because I'm working with a permissioned Besu network. In order to get that, I'm running EthSigner on a Docker container. I know that EthSigner - Besu node connection is working properly, because if I run this command, I can get this result:

    curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":51}'

    "jsonrpc" : "2.0",
    "id" : 51,
    "result" : "0xfe89"

    But if I try to connect with Remix (Web3 provider), I get this error from Remix pop-up: Cannot get account list: Error: Invalid JSON RPC response: ""

    And if I open the firefox console, i get this: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at (Reason: CORS header 'Access-Control-Allow-Origin' missing)

    I'm using http version of Remix, so I don't know what is the problem. What can I do? Maybe EthSigner isn't compatible with Remix Web3 Provider? Any ideas?

    Manuel Montenegro
    Update: I installed firefox add-on: "Allow CORS: Access-Control-Allow-Origin" and it's working now. But I think EthSigner should have any option for setting up this
    3 replies
    Lucas Saldanha
    This message was deleted
    2 replies
    Trent Mohay
    @/all Ethsigner 0.7.0 has just been released:
    Binaries = https://bintray.com/consensys/pegasys-repo/ethsigner/0.7.0#files
    Source = https://github.com/PegaSysEng/ethsigner/releases/tag/0.7.0
    Changes =
    Features Added
    • Added "eth_sign" JSON RPC
    • Added "--http-cors-origins" commandline option to allow browser based apps (remix/metamask) to connect to EthSigner
    • Added "--downstream-http-path" commandline option to allow Ethsigner to connect to a downstream web3 provider not on root path (eg web3 provider running in infura)
    • If inbound request contains the "Host" header, it is renamed to "X-Forwarded-Host" and added to downstream request
    • Code base split, crypto operations moved to "Signers" repository
    • First line of Password file (stripping EOL) is treated as the password (rather than whole file content)
      Bugs Fixed
    • Create invalid signature when Signature field was treated as negative BigInteger #247
      Thanks to @sprect8 and @diega for the submissions :) This release is mostly your work.
    Diego López León
    awesome! I'll try to work on eth_signTypedData for the next release!
    Trent Mohay
    @diega - we were going to wait, but figured releases are cheap so can do them as necessary - let us know if we can help out
    Is it needed to unlock an Account in ethsigner (like using personal_unlockAccount of web3) , after creating one using the instructions at https://docs.ethsigner.pegasys.tech/en/stable/Tutorials/Multifile/ at Create Passwords and Key Files section ?
    Trent Mohay
    @PavithraCP there's no need to explicitly unlock an account, any account configured in Ethsigner (either via TOML or the commandline) will automatically be used to sign a transaction (as based on the "From" field).
    @rain-on Thanks!
    Vinod Damle
    Hi @rain-on hope you are doing well! I wanted to let you know that the io.vertx:* deps in ethsigner need to be updated to at least 3.9.0 to address a critical vulnerability. vertx-core pulls in netty*:4.1.39.Final which is vulnerable to https://nvd.nist.gov/vuln/detail/CVE-2020-11612 . netty needs to be at 4.1.46 or higher (ref: https://mvnrepository.com/artifact/io.vertx/vertx-core)
    Trent Mohay
    Hey @vdamle, thanks for brining this up - will see if we can get this shortly :thumbsup:
    3 replies
    To improve the experience of users across our product suite, we're moving over to Discord. Here's the invite for the EthSigner channel - https://discord.gg/5U9Jwp7 - would love to see everyone over there. We'll be monitoring and active in this channel for the next 4 weeks and post a few reminders about the move.
    David Ammouial
    Hi all! Is is possible to set up Azure KeyVault once and share the configuration across multiple keys? My backend service needs to be able to create keys dynamically so it feels a little bit wrong to create many physical files with the same Azure secret replicated in each one.
    especially since Azure KeyVault gives the ability to a client to manage multiple keys
    Trent Mohay
    Hey @davux, at the moment, every key gets its own config file - so yes, unfortunately, you have to put the secret in multiple places. It's basically due to how EthSigner evolved, in that it treats every key as an independent entity, and thus gets its own config file.
    I really like the idea of a single "vault config", with multiple keys, but given our current workload, it's unlikely to be considered for development in the near future.
    Otherwise - I should mention, this gitter is deprecated, and we're moving all of our communications across to the Consensys Discord - specifically the invite for the ethsigner channel is https://discord.gg/5U9Jwp7 (as above).
    Alexander C.
    Hi there! I am trying to use Hashicorp Vault for signing arbitrary Strings. In dev mode this works fine, but in prod mode I can't start ethsigner, it stops with "Cause: Failed to extract secret from Hashicorp vault." I enabled secrets, but to no avail. I can put and get the key manually, my error seems identical to this: https://ethereum.stackexchange.com/questions/84594/failed-to-extract-secret-from-hashicorp-vault-production-mode-ethsigner-hash