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

doc: Add link badges #179

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rzr
Copy link

@rzr rzr commented Nov 11, 2018

Change-Id: I3975007242c5171b2bfcdb3884150ec61cc7749d
Signed-off-by: Philippe Coval rzr@users.sf.net

Change-Id: I3975007242c5171b2bfcdb3884150ec61cc7749d
Signed-off-by: Philippe Coval <rzr@users.sf.net>
@rzr
Copy link
Author

rzr commented Nov 11, 2018

To show how master is late to npm.org

@rzr rzr mentioned this pull request Nov 11, 2018
@rzr
Copy link
Author

rzr commented Nov 20, 2018

Is this projects still maintained ? @JoshKaufman @coolaj86 ?

@coolaj86
Copy link
Contributor

coolaj86 commented Nov 23, 2018

@rzr Now that both node and browsers support RSA and EC pretty well I've switched to using native node and webcrypto for the heavy lifting and I have a well-tested suite of tools for other tasks.

So for things like these:

  • PEM-to-JWK
  • JWK-to-PEM
  • SSH pubkey conversion
  • CSR generation

I'm now using lightweight, zero dependency libraries that I wrote from scratch and tested against openssl, ssh-keygen, and webcrypto:

I'm so grateful that they've existed and have served so well for so long, but I personally think it's time to abandon ursa, forge, elliptic, pkijs, asn1js, and the others in favor lightweight wrappers around node-native and web-native algorithms and that's where I'm putting my time and attention.

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

Successfully merging this pull request may close these issues.

2 participants