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

Use HTTPS for communication #90

Open
GoogleCodeExporter opened this issue Mar 17, 2015 · 0 comments
Open

Use HTTPS for communication #90

GoogleCodeExporter opened this issue Mar 17, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Start wireshark with apprioriate filters to reduce entries
2. Refresh Google contacts resource in KAddressbook

What is the expected output? What do you see instead?
I would expect that all traffic goes over an encrypted HTTPS channel. Instead, 
I see that contacts are transferred over plain HTTP with all an authentication 
token in it.

What version of the product are you using? On what operating system?
I am using 0.9.6 on Arch Linux (https://aur.archlinux.org/packages.php?ID=24286)

Please provide any additional information below.
I also checked with openssl' s_server whether the implementation was vulnerable 
to a MITM attack. Luckily, this was not the case: it simply aborts the 
connection setup. I did not receive any feedback however in KAddressbook, 
though I saw an "invalid password" message in akonadiconsole.
The attached patch is tested and did not cause regressions in the contacts 
retrieval functionality.

Original issue reported on code.google.com by [email protected] on 23 Jun 2012 at 9:12

Attachments:

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

No branches or pull requests

1 participant