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

draft for release v1.1 #23

Closed
iceman1001 opened this issue Jan 19, 2018 · 5 comments
Closed

draft for release v1.1 #23

iceman1001 opened this issue Jan 19, 2018 · 5 comments
Labels

Comments

@iceman1001
Copy link
Owner

iceman1001 commented Jan 19, 2018

With this draft I open up for discussions about which functionality the next release should have.

Current firmware works with existing GUI. As of this release we are free to deviate from old legacy and bring new/fixs into action!

original idea

  • merge MF_DETECTION functionality into MIFARE_CLASSIC_nK , partly to save space and since it really doesn't need its own function.
  • MF_CLASSIC 1K should not react to magic command default. It should be an option.
  • MF_CLASSIC 1K SAK 0x08 - 0x88 , optional to set SAK , not to be read for Sector0-Block0.
  • MF_CLASSIC 1K crypto1 enhancements.
  • tag slots, only allow two slots to have 4K support, in order to save memory

What currently is implemented

  • firmware naming a new firmware name to better indicate which version
  • MF_CLASSIC 1K should not react to magic command default. Compiler-directive
  • MF_CLASSIC 1K optional ATQA/SAK. Can be set per slot individually
  • MF_CLASSIC 1K crypto1 enhancements.
  • tag slots, only allow two slots to have 4K support, in order to save memory
@kevin2008-01
Copy link

waouuu! fine. thank you iceman1001

@iceman1001
Copy link
Owner Author

@bogiton
So what do you think?

@bogiton
Copy link
Collaborator

bogiton commented Feb 22, 2019

Should we also remove the "MY" extension for this release?
Are there 2 slots that support 4K? I thought it was only the first one.

@iceman1001
Copy link
Owner Author

Should be one, but all this extra memory we now have... Question is if we should be able to do 4k everywhere..
4*8kb in flash mem
and the active slot is downloaded to ram ?
..
but when to save the potential changes made by reader to flashmem?
and the powerdown...

@bogiton
Copy link
Collaborator

bogiton commented Feb 22, 2019

That needs some thought. And definitely some testing.

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

No branches or pull requests

3 participants