-
Notifications
You must be signed in to change notification settings - Fork 195
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
Key warning when initiating echo chat #440
Comments
As far as i know it's a feature not a bug ;-) |
This is a messenger. Not a memo tool... ts |
Writing to yourself is perfectly normal for an XMPP service, especially because it allows you to exchange messages and data between all the devices connected to the account. |
@Norbert80 I'm using this feature still this way and I like it :-P I'm also use it to send me memos to (e.g. Hyperlinks) my PC via Kontalk Desktopclient (like @daniele-athome said). |
@webratte there are apps like Google Keep that are synchronising. |
@Norbert80 Maybe. But why should I install another App if Kontalk do the same work for me? ;-) But I think this is not the right place for this discussion. |
@daniele-athome does your patch just accept each key when chatting with onselfe? Or does it really use the local stored key? Background of my question is to ensure to recognise man-in-the-middle attacks also for echo chats. |
@Norbert80 it uses the server-provided key for encrypting, but it still uses the local key for decrypting. That way, if decryption or signature verification fail, you're probably facing a MITM attack. Although the user is not explicitly warned in this case (just the usual red alert badge on the message; you need to open message details to know more). |
Kontalk lists myself as contact. I started a conversation with myself. First I had to confirm a red message about accepting changed keys. Now I get my own echo. :-)
The text was updated successfully, but these errors were encountered: