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

7.0.0 #91

Merged
merged 63 commits into from
Jan 29, 2020
Merged

7.0.0 #91

merged 63 commits into from
Jan 29, 2020

Conversation

Keats
Copy link
Owner

@Keats Keats commented May 25, 2019

No description provided.

kellenff and others added 8 commits April 1, 2019 12:11
Using `chrono`'s `serde` feature uses ISO 8601 instead of a Unix 
timestamp as specified in RFC 7519 section 2, "NumericDate". This 
example uses  custom de/serialize functions as shown in the [serde.rs 
example, "Custom Date 
Format"](https://serde.rs/custom-date-format.html).

NOTE: Currently fractional values are not supported in the example, 
though they are in the spec.
@Keats Keats mentioned this pull request May 25, 2019
kanru and others added 5 commits June 8, 2019 03:08
As specified in https://tools.ietf.org/html/rfc7518#section-3.5

- PS256 - RSASSA-PSS using SHA-256 hash algorithm
- PS384 - RSASSA-PSS using SHA-384 hash algorithm
- PS512 - RSASSA-PSS using SHA-512 hash algorithm
@Keats Keats mentioned this pull request Jun 22, 2019
@ronanyeah
Copy link

Could ring be bumped to 0.15.0 in this release?

error: failed to select a version for `ring`.
    ... required by package `jsonwebtoken v6.0.1`
    ... which is depended on by `drivesheet v0.1.0 (/home/ronan/repos/drivesheet)`
versions that meet the requirements `^0.14.4` are: 0.14.6, 0.14.5, 0.14.4

the package `ring` links to the native library `ring-asm`, but it conflicts with a previous package which links to `ring-asm` as well:
package `ring v0.15.0`
    ... which is depended on by `drivesheet v0.1.0 (/home/ronan/repos/drivesheet)`

failed to select a version for `ring` which could resolve this conflict

@Keats
Copy link
Owner Author

Keats commented Jul 15, 2019

It will

@LeviSchuck
Copy link
Contributor

There’s been no activity from Keats since this last message, can a PR be forked to just include the ring bump?

@briansmith
Copy link
Contributor

Could ring be bumped to 0.15.0 in this release?

It should be 0.16.5 now.

Cargo.toml Outdated Show resolved Hide resolved
src/crypto.rs Outdated Show resolved Hide resolved
src/crypto.rs Outdated Show resolved Hide resolved
src/crypto.rs Outdated Show resolved Hide resolved
@briansmith
Copy link
Contributor

I will take 30 minutes to try to update this to ring 0.16.5.

@briansmith
Copy link
Contributor

You can merge #96 into the next branch to update this PR to use ring 0.16.5.

Thanks for all your work on jsonwebtoken. I am planning to submit some more PRs soon to help you out.

@Keats
Copy link
Owner Author

Keats commented Nov 15, 2019

An alpha version has been released: https://docs.rs/jsonwebtoken/7.0.0-alpha.1/jsonwebtoken/index.html

If anyone has some time to try it and give feedback it would be great. The main change is that the encode/decode functions now take the .pem instead of the der format, it can decode using RSA pub key components and adds RSA PSS.

@Keats Keats merged commit e89fa41 into master Jan 29, 2020
@Keats Keats deleted the next branch January 29, 2020 07:02
JadedBlueEyes referenced this pull request in JadedBlueEyes/jsonwebtoken Apr 13, 2023
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.

8 participants