Is it possible to have only the public key? about steel_crypt HOT 4 CLOSED

And to you. Quite honestly, I don't really care if you used this package. What matters is that you were able to achieve the functionality on dart, which you did.
Good luck on all your future coding endeavors.

from steel_crypt.

1. As for keeping only the public key, it's fairly simple, only fetch the public key. The private key will still be encoded into a keypair in the class itself, meaning you only need the one. However, I might ask, why do you need to encrypt only and not decrypt? (This is so that I might be able to improve runtime efficiency and/or features of the package.)

2. Alright, so I assume you did something like this (post a code snippet if it's a different issue):
   var encrypter = new RsaCrypt(); var pubKey = encrypter.pubKey; print(pubKey); //Which prints "Instance of RSAPublicKey"
   SteelCrypt exposes PointyCastle's RSA AsymmetricKeyPair class, which in turn contains two keys, one of which is an RSAPublicKey and the other is an RSAPrivateKey. However, both of these classes contain no useful string representation, meaning that there is no way to "see" the value of the keys. The keys still exist, so, while you can't really print them, you can definitely use the public key to encrypt by using the .pubKey getter of the RsaCrypt() class.

I hope this answers your questions, but on the chance it didn't, make sure to comment back ASAP, as I have a relatively free schedule the next couple days. Cheers!

from steel_crypt.

Thanks for your kind reply. I will try to explain the situation more detailed and as simple as I can:
I have a mobile app. The user has to login and send his credentials. I am not using firebase, so I have to ensure myself that those credentials are sent securely. To do that, I want the mobile app to get the public key from my backend, encrypt the credentials with it, and send them back to the backend.
So what I really want to do is have a RsaCrypt()-object that uses the public key sent from my backend.

Cheers!

from steel_crypt.

Just wanted to let you know that I found a work around (sadly, not by using this package...).
Anyway, thanks and jolly coding!

from steel_crypt.