Monday Calls: Dec 11-17

[ipfs-helper]

For information about these calls and how they work, read the ipfs/pm README.

Calendar

Zoom and Stream links will be updated directly before the calls. Links to them will also be dropped in IRC, at the start of each call. If the link below seems to link to this issue, the link has not been updated yet.

Video Conference link

Monday

Endeavour	Lead	Notetaker	Time (PST - UTC - CET)	Pad
All Hands Call	@ipfs-helper	TBD	9:00 17:00 18:00	agenda and notes

Please add any agenda items you have to the pad before the project-specific sprint call starts.

Note that the agenda notes do not automatically have content added to them (see tracking issue). Add this template.

The sprints for the week are available to view in the WaffleBoard for ipfs/roadmaps.

[victorb]

Recording: https://ipfs.io/ipfs/QmVpmbvkEkgMPMJjBMPzQPvuosoiUK2unWHN29rZdxM3Aa

[daviddias]

@richardschneider could you list here the issues you want me to review on ipfs key management and crypto?

[richardschneider]

libp2p-keychain is required (an NPM release) to implement ipfs key management. The key management is in PR ipfs/js-ipfs#1133. With these PRs merged, the key management tests PR ipfs-inactive/js-ipfs-http-client#641 will pass.

keychain uses node.forge for PKCS 7 (CMS) and PKCS 8 (key exchange). While I am not pushing forge it does the current job]. Issue libp2p/js-libp2p-crypto#114 discusses moving PKCS 8 into libp2p-crypto.

I do not think forge is a long term solution. However, it is useful in the short term to get ipfs key management implemented.

keychain is about using PKCS standards. So internally swapping forge for libp2p-crypto (when it has the features) will not affect js-ipfs or the js-ipfs-repo.

[daviddias]

Thanks @richardschneider, followed up here ipfs/js-ipfs#1133 (comment)