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

Is there any porting documentation to the new API? #627

Open
darix opened this issue Aug 5, 2024 · 7 comments
Open

Is there any porting documentation to the new API? #627

darix opened this issue Aug 5, 2024 · 7 comments

Comments

@darix
Copy link

darix commented Aug 5, 2024

Some distros might want to keep yubioath-desktop because packaging is easier compared to the flutter app.

I didnt find any documentation how to port things from the removed API to the new one.

@dainnilsson
Copy link
Member

Changes and deprecations in the public API are generally documented in the NEWS file. However, yubioath-desktop uses some private APIs which are undocumented.

That said, I also want to strongly advise against packaging a much older version of the app as it lacks a lot of functionality, won't be compatible with newer devices, and may have unresolved bugs and security issues.

@darix
Copy link
Author

darix commented Aug 6, 2024

well not even the yubikey-manager-qt is fully updated as you can e.g. see here Yubico/yubikey-manager-qt#361

@dainnilsson
Copy link
Member

That is correct. As stated in the README that project is no longer under active development. Yubico Authenticator 7 has replaced it and is far more capable.

@darix
Copy link
Author

darix commented Aug 6, 2024

Which begs the question there are some PR open that would fix some of the issue to make it work with ykman > 5.0.1

will those ever be accepted or would it be better to just set the repository to archived?

@jutomation
Copy link

@dainnilsson Is the authenticator 7 app closed source?

@darix
Copy link
Author

darix commented Aug 6, 2024

https://github.com/Yubico/yubioath-flutter

@dainnilsson
Copy link
Member

@darix I'll bring the question to the team for discussion. I agree it's not great having things the way they are now. I don't really see much point in accepting the PRs with no intent to ever make a new release, so archiving seems like a good way to go.

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

No branches or pull requests

3 participants