Dave Longley
Dave Longley
Prepending the leading `0x00` byte is correct according to [PKCS#1 v2.1](https://www.ietf.org/rfc/rfc3447.txt). This is a change from 2.0, but it should be backwards compatible. So the patch in this PR would...
The latest, [PKCS#1 v2.2](https://tools.ietf.org/html/rfc8017#section-7.1.1), also prepends a `0x00` byte to the encoded message.
I may have misread these changes ... looking back over it again.
Related to #283.
Thanks, stesie, this is great. It will take some time for me to review this and the MGF1 API changes -- I want to ensure they work with the direction...
@wottpal, This PR needs to be rebased because it has conflicts. @stesie, are you able to rebase it? If not, @wottpal, could you submit a new PR that has the...
Thanks @gkellogg! This is great. A few minor changes needed plus one architectural thing we need some feedback from @davidlehn on (regarding how to pull in a dom parser).
@davidlehn -- can you see if this is fixed and close if so?
Partially supported with `expansionMap` and `compactionMap` here: bcae96153a1e7da6669eeaf25f856ab93d833cd8 Still need something for `toRDF`.
Specifically, when converting to RDF, relative URIs are dropped and this should be handled by another map or similar mechanism.