Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Encryption & connection errors when using Ed25519 PeerId #4269

Closed
aewing opened this issue Dec 16, 2022 · 2 comments
Closed

Encryption & connection errors when using Ed25519 PeerId #4269

aewing opened this issue Dec 16, 2022 · 2 comments
Assignees

Comments

@aewing
Copy link

aewing commented Dec 16, 2022

  • Version:
{
  "version": "0.17.0",
  "commit": "e8b7b66bfa98c2a1c0d0bfc19f698d7d00b6c888",
  "repo": "12",
  "ipfs-core": "0.17.0",
  "interface-ipfs-core": "^0.157.0"
}
  • Platform:

Darwin 21.6.0 arm64 & latest chrome

  • Subsystem:

libp2p?

Severity:

Critical

Description:

I generated an Ed25519 PeerId (either using createFromPrivKey or createEd25519PeerId from @libp2p/peer-id-factory [^1.0.20]), called create from ipfs-core, passing the peerId to init.privateKey with init.algorithm set to Ed25519 and passing the peerId to libp2p.peerId.
When connecting to a node process via swarm, I see encryption errors. ('ERR_ENCRYPTION_FAILED' from @chainsafe/libp2p-noise)
With the same setup but a default peerId, I do not see errors and the peers are connecting without issue.

Steps to reproduce the error:

See description.

@aewing aewing added the need/triage Needs initial labeling and prioritization label Dec 16, 2022
@welcome
Copy link

welcome bot commented Dec 16, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@SgtPooki SgtPooki added kind/unknown-in-helia and removed need/triage Needs initial labeling and prioritization labels May 16, 2023
@SgtPooki
Copy link
Member

SgtPooki commented May 16, 2023

Hello @aewing,

js-ipfs is being deprecated in favor of Helia. You can learn more about this deprecation and the corresponding migration guide here.

As a result, we are going to close this issue. If you think we have done this in error, please feel to reopen with any comments in the next week as we will circle back on the reopened issues.

We hope you will consider Helia for your IPFS in JS needs. If you believe this particular request belongs in Helia, feel free to open a Helia issue. We look forward to engaging with you more there.

Thanks,
@ipfs/helia-dev

@SgtPooki SgtPooki closed this as not planned Won't fix, can't repro, duplicate, stale May 16, 2023
@SgtPooki SgtPooki self-assigned this May 17, 2023
@SgtPooki SgtPooki moved this to ✅ Done in js-ipfs deprecation May 17, 2023
@SgtPooki SgtPooki moved this from ✅ Done to 🏃‍♀️ In Progress in js-ipfs deprecation May 17, 2023
@SgtPooki SgtPooki moved this from 🏃‍♀️ In Progress to ✅ Done in js-ipfs deprecation May 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Status: Done
Development

No branches or pull requests

2 participants