-
Notifications
You must be signed in to change notification settings - Fork 4
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
libfreefare 0.4.0 does not contains MifareKeyDeriver #9
Comments
Thanks for the info. I have written this library many years ago and don't remember all the details. Please consider it to be experimental and essentially unmaintained. As of now I do not even have the hardware to test the code, so it is difficult for me to continue development on it. I will however go ahead and amend the README to be more clear about the demands (which I don't quite recall). |
@maitredede
|
Yes, you'll need a newer version of libfreefare or an older version of this package. If you would like to continue to work with libfreefare 0.4.0, I can tag an older version in the new Go module style so you can use this package with libfreefare 0.4.0. |
What is a sufficiently new version of libfreefare?
I don't have a requirement to use a particular version of any library. Thanks for being so prompt on responding to this, I understand that you have not maintained this library for some time. |
Version faac4ae5d881a12d7fb81fc831629ae1d1f10929 should work. That's the last commit before the breaking changes of 1.0.0. |
I have prepared a new release based on the 0.3.1 branch that should work with Go modules and libfreefare version 0.4.0. Could you check if everything works fine if you change the freefare dependency to
? If you report success, I'll go ahead and push a v0.3.2 release for use with libfreefare 0.4.0 ASAP. |
This commit has now been pushed as v0.3.2. Please downgrade to v0.3.2 to use this wrapper with libfreefare-0.4.0. |
Sorry I was taking a while to respond but I am still having some issues. I'm not that familiar with go but I think I'm performing this correctly so I made a reproduction of my steps for how I have installed the components.
|
This does not look like you have libfreefare 0.4.0 on your system. Rather, these symbols look like they are from after the symbol name change. |
In my log I show that I have no other version of libfreefare installed on my system:
and then install the version you've indicated:
and it appears to complete successfully with
Maybe when I am performing make install I am relinking to a dormant version of libfreefare? but besides that I don't know how this would be happening |
For reference...
|
I repeat: the new v0.3.2 (which is what c4129c5 is) is for libfreefare-0.4.0. The release. Not any intermediate or development version. What I was asking you to try earlier was to build v0.4.0 with libfreefare faac4ae5d881a12d7fb81fc831629ae1d1f10929. But it seems like I was wrong and picked too late of a commit. Perhaps try d946230aec3e81a9b641b49f4a8bf5845c246e1a with v0.4.0 if you want to stay on v0.4.0? |
Ah apologies, I completely missed that this repository's tag numbering is similar to libfreefare's tag numbering and so I equated any reference to v0.4.0 or similar range with only that library. Thanks for the help |
Great! Could you also test v0.4.0 of this package with libfreefare commit faac4ae5d881a12d7fb81fc831629ae1d1f10929? If you use libfreefare commit faac4ae5d881a12d7fb81fc831629ae1d1f10929, then you have everything that should be needed to build |
github.com/clausecker/[email protected] + faac4ae5d881a12d7fb81fc831629ae1d1f10929 github.com/clausecker/[email protected] + faac4ae5d881a12d7fb81fc831629ae1d1f10929
github.com/clausecker/[email protected] + d946230aec3e81a9b641b49f4a8bf5845c246e1a
|
Fascinating. This should definitely build. Will have to investigate. |
Seems like libfreefare commit b83cbcbb09b3467f455f3e1617f711d9327d4ed8 or later is needed for v0.4.0 of this wrapper. Apparently PR #8 had followed through with some of the upstream symbol renames. |
This clarifies the questions raised in #9.
Hi,
I have built libfreefare 0.4.0 from sources : https://github.com/nfc-tools/libfreefare/releases/tag/libfreefare-0.4.0
The type
MifareKeyDeriver
has been added after (year 2018) the tag 0.4.0 has been released (year 2015). Maybe you should state in your doc that your lib needs a self-built version of libfreefare, until a release is done (see nfc-tools/libfreefare#121)The text was updated successfully, but these errors were encountered: