You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to contribute and add encryption support to the standard library. I am still new to gleam and would appreciate some guidance as it seems to be a pretty big undertaking. I will use this issue to track my progress and write down how I build this API.
Before I start, here are a few questions I had:
One main issue, is there a proper way to handle algorithms that are supported by one platform (erlang crypto) and not by the other (WebCrypto)?
Should we separate asymmetric and symmetric encrypt?
The text was updated successfully, but these errors were encountered:
If we're unable to support both platforms then we'll have to defer that addition until we can.
I don't have any particular opinions on the scope on this library beyond wanting to cover the most generally useful crypto bits and bobs one might want in a typical application.
Sorry, I wasn't clear in my question, but if one platform supports only RSA encryption while the other supports many more, should I just implement RSA?
Hi @lpil!
I want to contribute and add encryption support to the standard library. I am still new to gleam and would appreciate some guidance as it seems to be a pretty big undertaking. I will use this issue to track my progress and write down how I build this API.
Before I start, here are a few questions I had:
The text was updated successfully, but these errors were encountered: