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

KVMI-6 vs KVMI-7 vs MASTER #40

Open
aghamir opened this issue Sep 15, 2020 · 3 comments
Open

KVMI-6 vs KVMI-7 vs MASTER #40

aghamir opened this issue Sep 15, 2020 · 3 comments

Comments

@aghamir
Copy link

aghamir commented Sep 15, 2020

Hi guys,
Can you explain what is the difference between these branches? I want to update my application which was written two years ago. Which branch should I work on?
Best wishes,

@Wenzel
Copy link
Member

Wenzel commented Sep 15, 2020

Hi @aghamir,

Thanks for your question, i will add a section to the documentation explaining the branches.

  • master: main stable branch, currently holding kvmi-v6 but will move to kvmi-v7 soon
  • kvmi-v6: tracks a working state of KVM-VMI for v6, currently the same as master.
  • kvmi-v7: tracks a working state of KVM-VMI for v7

If you developed your application 2 years ago, i guess it was written based on the nitro system ? (Syscall interception).

This system has been deprecated in favor of Bitdefender's KVMi.
A backup branch exists as nitro.

I hope this helps clarifly the situation of the branches which I recognize is confusing.

I'm doing my best to offer a good level of support and write new documentation.

Cheers !

@aghamir
Copy link
Author

aghamir commented Sep 15, 2020

Thanks a lot Mathieu. No I was built my application on the early kvmi release(1 or 2 months after you change the name of this repository if I remember correctly).
BTW, you helped me a lot.
Is KVMI-v7 stable now? I guess I will move to v7 too.

@Wenzel
Copy link
Member

Wenzel commented Sep 15, 2020

Yes, you should move to kvmi-v7, i shiuld post a detailed versioning between v6 and v7

Happy hacking 👌

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

No branches or pull requests

2 participants