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

Support for NXP proprietary EC? #35

Open
arekinath opened this issue Jun 2, 2020 · 4 comments
Open

Support for NXP proprietary EC? #35

arekinath opened this issue Jun 2, 2020 · 4 comments

Comments

@arekinath
Copy link
Owner

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)

@arekinath
Copy link
Owner Author

@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)

@martinpaljak
Copy link

It would not hurt to have it source-wise at least (for those who can compile themselves)

@mhardeman
Copy link

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.

@mhardeman
Copy link

It would not hurt to have it source-wise at least (for those who can compile themselves)

I'll see if I can do a new version of it in keeping with the above referenced refactoring. If I put that together, I'll submit a pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants