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

Create prelude for easier importing of Recrypt #63

Closed
clintfred opened this issue Mar 1, 2019 · 0 comments
Closed

Create prelude for easier importing of Recrypt #63

clintfred opened this issue Mar 1, 2019 · 0 comments
Assignees
Milestone

Comments

@clintfred
Copy link
Contributor

Using the 256-bit Recrypt API requires several common imports. It would be nice if these were provided as a prelude. This should not be everything, but simply a minimal set of imports to get going.

Usage should look something like
use recrypt::prelude::*;

@clintfred clintfred added this to the 2019-03-08 milestone Mar 1, 2019
@clintfred clintfred self-assigned this Mar 1, 2019
clintfred added a commit that referenced this issue Mar 1, 2019
clintfred added a commit that referenced this issue Mar 1, 2019
coltfred pushed a commit that referenced this issue Apr 30, 2019
* Api naming and visibility changes (#57)

* Api naming and visibility changes
* api::Api -> api::Recrypt
* api_480::Api480 -> api_480::Recrypt480
* ApiErr -> RecryptErr; RecryptErr is now publicly exported from the api/api_480 namespace
* api and api_480 PrivateKey::ENCODED_SIZE_BYTES now public

* [#63] Add prelude for easier importing (#64)

* [#65] update CI to rust 1.33.0; update proptest to ~0.9 (#66)

* Add to_private_key to DerivedSymmetricKey (#70)

* * added `to_private_key` to `DerivedSymmetricKey`
* make `PublicKey` arguments in public API borrows

* Update 480 bit api, tests and benches

* * added to_private_key to Recrypt480

* remove to_private_key from Recrypt480

* Move derive_private_key onto the apis

* Add as_vec function to make it easier to get to vec iterators

* Throw away the most significant bytes instead of the least, because it seems to make more sense to me

* Add known private key test for api480

* formatting

* Remove printlns

* Address Clint's concerns

* The hashable instance was unused. Remove it and add a different one. (#71)

* Change bytes property on SigningKeypair to return a borrow of the internal bytes (#72)

* releasing v0.7.0
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

No branches or pull requests

2 participants