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

Question about toxcore #735

Closed
zezaku opened this issue May 19, 2021 · 2 comments
Closed

Question about toxcore #735

zezaku opened this issue May 19, 2021 · 2 comments
Labels
question Further information is requested

Comments

@zezaku
Copy link

zezaku commented May 19, 2021

Hello.
What u think about this TokTok/c-toxcore#426
?Is this issue fixed on aTox?
Thank you.

@robinlinden robinlinden added the question Further information is requested label May 19, 2021
@robinlinden
Copy link
Collaborator

Hi!
I think you're better off reading the comments in the thread, but in brief, while it's not good that Tox is vulnerable to KCI, and there is work ongoing that would solve this issue, it also requires your secret key to be compromised.

aTox uses TokTok/c-toxcore (v0.2.12 right now) with no special patches, so if your Tox profile is stolen from aTox, the attacker can both impersonate you to your contacts, and impersonate your contacts to you. aTox does however store your profile in the internal storage area, meaning that no other apps can access the files, and that the profile is stored encrypted on newer Android versions.

TL;DR: It's not good, but requires your profile to have been compromised, and aTox has no special safeguards against it.

@robinlinden
Copy link
Collaborator

Closing this since it's been over 2 months with no follow-up questions or activity. Feel free to reopen or open a new issue if there was anything else! :)

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

No branches or pull requests

2 participants