You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be off topic for the JC 2.2.1 fork, as it's for yet another version, but if there is interest, I have written mods for the project to support the NXP proprietary EC functionality in the J2D081/J3D081 (and could support a few other older versions as well) to do the full precomputed hash signatures using the NXP function on those cards, even though they are only JC 3.0.1.
I can certainly distribute my code, though I doubt I could distribute the NXP library .exp (export) files necessary to compile. Is there any interest in this or would it just be pollution in the project?
@mhardeman I'm not opposed to adding that behind a compile option, possibly in its own function after the refactoring in 33819af... do you know if we would be able to distribute .cap files compiled against these exports? (I realise the exports themselves are almost certainly under the NDA)
do you know if we would be able to distribute .cap files compiled against these exports?
I'm aware of no restrictions which would prevent me providing output cap files that utilized the exports in the manner originally intended by the manufacturer.
It may be off topic for the JC 2.2.1 fork, as it's for yet another version, but if there is interest, I have written mods for the project to support the NXP proprietary EC functionality in the J2D081/J3D081 (and could support a few other older versions as well) to do the full precomputed hash signatures using the NXP function on those cards, even though they are only JC 3.0.1.
I can certainly distribute my code, though I doubt I could distribute the NXP library .exp (export) files necessary to compile. Is there any interest in this or would it just be pollution in the project?
Originally posted by @mhardeman in #2 (comment)
The text was updated successfully, but these errors were encountered: