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

Vulnerable to Freak Attack #30

Open
smurfy opened this issue Mar 6, 2015 · 9 comments
Open

Vulnerable to Freak Attack #30

smurfy opened this issue Mar 6, 2015 · 9 comments

Comments

@smurfy
Copy link

smurfy commented Mar 6, 2015

Webprirate is vulnerable to the Freak attack. See: https://freakattack.com/
Stock browser is safe.

@llelectronics
Copy link

See this as a reference: https://together.jolla.com/question/85049/sailfish-freaked-out/
From a security standpoint it isn't a pressuring issue as there are only theoretical ways to use this vulnerability (because QtWebkit itself does not support RSA_EXPORT and you need extra complicated hacks [hacking your access point/router/modem and the website] to get this working). And this is all theory for the moment.

@smurfy
Copy link
Author

smurfy commented Mar 6, 2015

@llelectronics
sure, i think its not that big of a problem too, still it should be fixed. (if possible)

About qtwebkit not supporting it, if you test with https://cve.freakattack.com the stock browser refuses the connection (invalid server key, i'm aware stock is gecko), my desktop chrome does the same.

Webpirate allows the unsecure key.

@Dax89
Copy link
Owner

Dax89 commented Mar 6, 2015

I know this issue but I can't do anything atm.

I don't know when Jolla release Qt >= 5.4 on Sailfish, so this week I have worked on an experimental version of WebPirate which uses Blink instead of the obsolete/buggy QtWebKit.

I have (almost) successfully ported the Chromium Embedded Framework (https://code.google.com/p/chromiumembedded/) on Qt/QML.

CEF uses Chromium 42 code base, it's updated and faster, and a very good alternative to QtWebKit.

@llelectronics
Copy link

Yeah same as webcat.
Therefor cooperating with Jolla is necessary hopefully the problem will be fixed with an update of qtwebkit && openssl .
I also hope sslv3 will be fixed aswell as I see this as a bigger issue atm.

@Dax89 : Great news that you are working on chromiumembedded. That will bring in lots of cool new stuff and speed. I personally believe Qt 5.4 will be part of the SailfishOS 2.0 update coming in June.

@smurfy
Copy link
Author

smurfy commented Mar 6, 2015

Thanks to you both for creating an alternative browser for sailfish.
I just wasn't sure about if its on your radar. I also think that the freak attack can and should be mitigated primarily by the server owner.

Keep up your great work.

@Dax89
Copy link
Owner

Dax89 commented Mar 6, 2015

@llelectronics I will upload the porting here on GitHub when it starts to become usable, so we can benefit both :)
@smurfy Thanks! :)

@Dax89
Copy link
Owner

Dax89 commented Mar 15, 2015

This is the repository containing my work done with Chromium Embedded (currently based on Chromium 42): https://github.com/Dax89/QtCEF

I'm giving priority on QtQuick implementation (the QWidget part is stubbed), I'm able to render web pages and playing HTML5 videos without issues (the rendering part needs a rewrite, but is low priority atm).

This is the result using the example contained in the repository:
https://dl.dropboxusercontent.com/u/40206233/Screenshots/QtCEF/Chromium_QtQuick.png

A lot of work still needs to be done :)

@smurfy
Copy link
Author

smurfy commented Mar 16, 2015

Cool, very nice

@Dax89 Dax89 added this to the WebPirate 2.0 (QtWebEngine) milestone Aug 19, 2015
@Mikaela
Copy link
Contributor

Mikaela commented Oct 9, 2015

POODLE & others too. https://www.ssllabs.com/ssltest/viewMyClient.html :(

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

No branches or pull requests

4 participants