jose: Javascript Object Signing and Encryption and JSON Web Token library

[ apache, cryptography, library, program ] [ Propose Tags ]

An implementation of the Javascript Object Signing and Encryption (JOSE) and JSON Web Token (JWT; RFC 7519) formats.

The JSON Web Signature (JWS; RFC 7515) implementation is complete.

EdDSA signatures (RFC 8037) are supported (Ed25519 only).

JWK Thumbprint (RFC 7638) is supported (requires aeson >= 0.10).

JSON Web Encryption (JWE; RFC 7516) is not yet implemented.

The ECDSA implementation is vulnerable to timing attacks and should only be used for verification.


[Skip to Readme]
Versions 0.1.26.0, 0.1.27.0, 0.2.31.0, 0.2.33.0, 0.2.38.0, 0.2.38.1, 0.3.38.0, 0.3.41.0, 0.3.41.1, 0.3.41.2, 0.4.0.0, 0.4.0.1, 0.4.0.2, 0.4.0.3, 0.4.0.4, 0.5.0.0, 0.5.0.1, 0.5.0.2, 0.5.0.3, 0.5.0.4, 0.5.0.5, 0.6.0.0, 0.6.0.1, 0.6.0.2, 0.6.0.3, 0.7.0.0
Dependencies aeson (>=0.8.0.1), attoparsec, base (>=4.8 && <5), base64-bytestring (==1.0.*), bytestring (==0.10.*), concise (>=0.1), containers (>=0.5), cryptonite (>=0.7), jose, lens (>=4.3), memory (>=0.7), monad-time (>=0.1), mtl (>=2), network-uri (>=2.6), QuickCheck (>=2), quickcheck-instances, safe (>=0.3), semigroups (>=0.15), template-haskell (>=2.4), text (>=1.1), time (>=1.5), unordered-containers (==0.2.*), vector, x509 (>=1.4) [details]
License Apache-2.0
Copyright Copyright (C) 2013, 2014, 2015, 2016, 2017 Fraser Tweedale
Author Fraser Tweedale
Maintainer frase@frase.id.au
Category Cryptography
Home page https://github.com/frasertweedale/hs-jose
Bug tracker https://github.com/frasertweedale/hs-jose/issues
Source repo head: git clone https://github.com/frasertweedale/hs-jose.git
Uploaded by frasertweedale at Fri Apr 6 05:06:45 UTC 2018
Distributions Arch:0.7.0.0, LTSHaskell:0.6.0.3, NixOS:0.7.0.0, Stackage:0.7.0.0, openSUSE:0.6.0.3
Executables jose-example
Downloads 6353 total (108 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2018-04-14 [all 1 reports]
Hackage Matrix CI

Modules

[Index]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for jose-0.7.0.0

[back to package description]

jose - Javascript Object Signing and Encryption & JWT (JSON Web Token)

jose is a Haskell implementation of Javascript Object Signing and Encryption and JSON Web Token.

The JSON Web Signature (JWS; RFC 7515) implementation is complete. JSON Web Encryption (JWE; RFC 7516) is not yet implemented.

EdDSA signatures (RFC 8037) are supported (Ed25519 only).

JWK Thumbprint (RFC 7638) is supported (requires aeson >= 0.10).

Contributions are welcome.

Security

If you discover a security issue in this library, please email me the details, ideally with a proof of concept (frase @ frase.id.au ; PGP key).

Before reporting an issue, please note the following known vulnerabilities:

  • The ECDSA implementation is vulnerable to timing attacks and should therefore only be used for verification.

and the following known not-vulnerabilities:

Interoperability issues

The following known interoperability issues will not be addressed, so please do not open issues:

  • Some JOSE tools and libraries permit the use of short keys, in violation of the RFCs. This implementation reject JWS or JWT objects minted with short keys, as required by the RFCs.

  • The Auth0 software produces objects with an [invalid "x5t" parameter]( https://community.auth0.com/questions/7227/certificate-thumbprint-is-longer-than-20-bytes). The datum [should be a base64url-encoded SHA-1 digest]( https://tools.ietf.org/html/rfc7515#section-4.1.7), but Auth0 produces a base64url-encoded hex-encoded SHA-1 digest. The object can be repaired so that this library will admit it, unless the offending parameter is part of the JWS Protected Header in which case you are out of luck until Auth0 bring their implementation into compliance.

Contributing

Bug reports, patches, feature requests, code review, crypto review, examples and documentation are welcome.

If you are wondering about how or whether to implement some feature or fix, please open an issue where it can be discussed. I appreciate your efforts, but I do not wish such efforts to be misplaced.

To submit a patch, please use git send-email or open a pull request. Write a [well formed commit message]( http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html). If your patch is nontrivial, update the copyright notice at the top of the modified files