-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
qtwebkit: Mark known vulnerable #201028
qtwebkit: Mark known vulnerable #201028
Conversation
The browser engine is based off an old Webkit version, receives no security backports, does no releases. The WebKitGTK people have counted over 500 CVEs they fixed since 2016. Adding known vulnerable to make people aware they're using a browser engine that is not up to todays standards and could very likely be easily compromised. Projects are recomended to migrate to qtwebengine instead. https://blogs.gnome.org/mcatanzaro/2017/02/08/an-update-on-webkit-security-updates/ qutebrowser/qutebrowser#4039 (comment) https://blogs.gnome.org/mcatanzaro/2022/11/04/stop-using-qtwebkit/
52 packages affected:
|
Our fork is somewhat more maintained, but still not particularly well maintained, definitely not on the same level as Chromium or others. Also, just checking the list of things that depend on it, the only thing that jumps out at me is kdevelop, and that can use qtwebengine so should probably just be switched over (it currently depends on both for some reason). |
Also checked |
|
Isn't used anyway.
Also seems unused.
apitrace update here: #201032 |
There is PR goldendict/goldendict#1542 to upstream. |
Does this PR count towards progress for #53079? |
Well, it drops at least two packages, so I'd say yes. |
|
Feel free to provide a follow-up PR! |
Some of the newly disappeared packages still have
|
Yeah without that some qml parts of calamares break, but should be possible to pinpoint exactly which packages are needed instead. I'll look into it |
Looks like kmymoney is affected by this because it takes |
See PR NixOS#201028 and issue NixOS#53079
PR to switch kmymoney from qtwebkit to qtwebengine: #201953 |
I believe |
|
due to NixOS#201028 and the deprecation of qtwebkit teamviewer refuses to evaluate. qtwebkit isn't needed for teamviewer and is therefore removed. Signed-off-by: Florian Brandes <[email protected]>
Note that qtwebengine currently depends on long-vulnerable python2, so it would also get dropped "soon", e.g. by PR #201859 |
Arch has patches for building it with Python3, maybe we should yoink those: https://github.com/archlinux/svntogit-packages/tree/packages/qt5-webengine/trunk |
(to get rid of transitive dependency on qtwebkit) See PR NixOS#201028 and issue NixOS#53079
Thanks everyone for helping clean up! |
due to #201028 and the deprecation of qtwebkit teamviewer refuses to evaluate. qtwebkit isn't needed for teamviewer and is therefore removed. Signed-off-by: Florian Brandes <[email protected]> (cherry picked from commit b9a8eae)
I'm beaten by this bug when I put Edit: I ended up adding |
The package you want is |
Ahah thanks, I come up to the same conclusion using |
I'd say we should have never had a |
The browser engine is based off an old Webkit version, receives no security backports, does no releases.
The WebKitGTK people have counted over 500 CVEs they fixed since 2016.
Adding known vulnerable to make people aware they're using a browser engine that is not up to todays standards and could very likely be easily compromised.
https://blogs.gnome.org/mcatanzaro/2017/02/08/an-update-on-webkit-security-updates/
qutebrowser/qutebrowser#4039 (comment)
https://blogs.gnome.org/mcatanzaro/2022/11/04/stop-using-qtwebkit/
Description of changes
Things done
sandbox = true
set innix.conf
? (See Nix manual)nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)nixos/doc/manual/md-to-db.sh
to update generated release notes