Bug 202826 - remember the milk's register button URL uses unencrypted HTTP protocol
Summary: remember the milk's register button URL uses unencrypted HTTP protocol
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-rememberthemilk (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-06 18:12 UTC by Martin Steigerwald
Modified: 2009-10-12 18:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Steigerwald 2009-08-06 18:12:46 UTC
Version:            (using KDE 4.3.0)
OS:                Linux
Installed from:    Debian testing/unstable Packages

The remeber the milk applet uses a http:// URL instead of a https:// one for its
register button. It should be changed to a https:// as soon as possible to make
sure that users data is transferred encrypted. HTTPS works with www.rememberthemilk.com.
Comment 1 Martin Steigerwald 2009-08-06 18:16:15 UTC
Does Remember the Milk use HTTPS internally? If not, this should also be changed. I can file another bug report about this.
Comment 2 Andrew Stromme 2009-10-11 19:53:13 UTC
SVN commit 1033988 by astromme:

Use https for the signup link
BUG: 202826


 M  +1 -1      authenticate.ui  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1033988
Comment 3 Andrew Stromme 2009-10-11 20:09:19 UTC
SVN commit 1034000 by astromme:

Backport 1033988 to 4.3.x
CCBUG: 202826


 M  +1 -1      authenticate.ui  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1034000
Comment 4 Martin Steigerwald 2009-10-12 09:14:28 UTC
Thanks for fixing this. Does Remember the Milk use HTTP for its own communication with Remember the Milk also? If so, it might be wise to fix this as well. I can file a different bug report for that so that it doesn't get forgotten.
Comment 5 Andrew Stromme 2009-10-12 18:20:13 UTC
Yes, it at the moment uses https for login and http for transfer. Aaron changed it to https for transfer but that wasn't working at all for me so I reverted it. I need to investigate more, we want things secured. A separate bug report would be appreciated. If you can, feel free to set it as assigned to me right off the bat.