Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[2.6][T4] Core unable to decrypt passphrase #3269

Closed
biolypl opened this issue Nov 18, 2019 · 5 comments
Closed

[2.6][T4] Core unable to decrypt passphrase #3269

biolypl opened this issue Nov 18, 2019 · 5 comments

Comments

@biolypl
Copy link

biolypl commented Nov 18, 2019

Expected Behavior
Command ark forger:start should decrypt the passphrase and run the forging plugin.

Current Behavior
The command starts forging plugin with none delegate. INFO : Loaded 1 inactive delegate:

Possible Solution

Steps to Reproduce (for bugs)

  1. Config encrypted BIP38 passphrase with CLI: ark config:forger
  2. Try to start the ark-forger.

Context

The issue hits me on fresh installed node (but synced). The encryption is correct (the same bip38 string in delegates.json as on my other nodes). Forging with plain text passphrase works on the node.

Your Environment

  • Version used: @arkecosystem/core/2.5.28
  • Environment name and version (e.g. node.js v10.15.3): node.js v11.15.0
  • Server type and version: -
  • Operating System and version: Ubuntu 18.04
  • Link to your project:
@ghost
Copy link

ghost commented Nov 18, 2019

Thanks for opening this issue! A maintainer will review this in the next few days and explicitly select labels so you know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

@samharperpittam
Copy link

Hi @biolypl ,

Thanks for reporting this issue.

We have tested internally and the only way we can reproduce the INFO : Loaded 1 inactive delegate: message on a bip38 encrypted forger is to enter an incorrect password when starting the forger process.

Just to double confirm, is it possible to stop your forger process, configure your bip38 forger and start the forger process again please?

Let us know the results, thanks!

@biolypl
Copy link
Author

biolypl commented Nov 18, 2019

Hello,
as you ask I reconfigured my bip38 forger. To minimize possible typo I used very easy 8 characters password and the issue stays.
I also reinstalled core but no luck.

The only interesting thing I can add here is the situation after reinstall, set bip38 encryption, start forger (still no delegates loaded), stop forger, configure forger without encryption and forger starts with:

Loaded 1 active delegate: my_delegate (my_correct_public_key)
Loaded 1 inactive delegate:

Where the delegates.json file is:

{
  "secrets": [
    "my_correct_passphrase"
  ]
}

So I don't get why it runs 2 delegates.

@faustbrian
Copy link
Contributor

Should've been fixed in the latest devnet release from last week. Reopen if the issue still occurs when using the correct password.

@ghost
Copy link

ghost commented Dec 5, 2019

This issue has been closed. If you wish to re-open it please provide additional information.

@faustbrian faustbrian changed the title Core unable to decrypt passphrase [T4][2.6] Core unable to decrypt passphrase Jan 8, 2020
@faustbrian faustbrian changed the title [T4][2.6] Core unable to decrypt passphrase [2.6][T4] Core unable to decrypt passphrase Jan 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants