Feature/issue 16

[omibo]

This pull request addresses the following issues:

• Implemented save_to_file functionality for KeyPair.
• Added corresponding CLI support.

To execute the command, use the following syntax:
capycrypt new_keypair "pw" "owner" -b 256 --output "output.json"

Note: The curve input has been excluded for now as it is not part of the KeyPair::new() method.

[Dustin-Ray]

this looks awesome so far, thanks for all of the effort on this! the next step would be to make sure you can open a file, and include a unit test showing a round trip test of some operation involving a keypair like signing and verifying a message, or encrypting and decrypting, existing tests for these already exist in integration tests

[omibo]

@drcapybara
I added integration test for reading from and writing to a file. Also, I implemented deserialization for keypair struct.

[Dustin-Ray]

@drcapybara I added integration test for reading from and writing to a file. Also, I implemented deserialization for keypair struct.

Perfect! Everything looks great! Thanks so much for this. The last thing to do on this to merge this in is to do the exact same thing for the Message type. All you need to do is:

• update Cargo.toml, bump version of tiny_ed448_goldilocks = "0.1.8"
• derive Serialize, Deserialize for the Message type in lib.rs. You also need to add the derive macro to the SecParam type as well.
• A round trip test: 1. create a new message, 2. create a new keypair 3. save them to a file, 4. load them back into the program, sign the message with key, 5. save the message to a file, 6. load it back into memory 7. verify the signature exactly how you did it with the keypair roundtrip test
• saving the keypair to a file should always include the public key. it should optionally include the private key. in save keypair to file, include an argument to the function "save_private_key: bool". if true, the private key is saved as Some(key), if false, private key is saved as None.

Then this is ready to merge in! You're doing great work so far!

[Dustin-Ray]

Looks great, you can merge if you would like! This is a great foundation to introduce the rest of the commands into the library