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

RUSTSEC-2024-0419: gtk-rs GTK3 bindings - no longer maintained #1033

Open
github-actions bot opened this issue Dec 10, 2024 · 2 comments
Open

RUSTSEC-2024-0419: gtk-rs GTK3 bindings - no longer maintained #1033

github-actions bot opened this issue Dec 10, 2024 · 2 comments

Comments

@github-actions
Copy link
Contributor

gtk-rs GTK3 bindings - no longer maintained

Details
Status unmaintained
Package gtk3-macros
Version 0.18.2
URL gtk-rs/gtk3-rs@508a69b
Date 2024-03-04

The gtk-rs GTK3 bindings are no longer maintained.

The maintainers have archived the repository, and added a note to the crate
description and its README.md that the crates are no longer maintained.

Please take a look at gtk4-rs instead.


See [advisory page](https://rustsec.org/advisories/RUSTSEC-2024-0419.html) for additional details.
@Eaterminer
Copy link

Eaterminer commented Jan 18, 2025

@FabianLars Why was this closed? it appears Tauri and Tao still depend on gtk3. I'm constantly getting dependabot security warnings about a library GTK3 depends on being vulnerable, because GTK3 requires an old version of that library.

Looking at the crates.io page for this project shows that it's still in use.

In WRY it was closed as not planned, and it is rather confusing as to why anyone would want a potential security issue to be treated as "not planned".

@FabianLars
Copy link
Member

no worries, we plan to downgrade to gtk2 asap. that should get rid of the dependabot warnings :)

In WRY it was closed as not planned, and it is rather confusing as to why anyone would want a potential security issue to be treated as "not planned".

Not Planned is for duplicate issues:
{0B606BFB-2405-45E9-A813-D703F80D7956}

I used github refined's batch close feature for those which sadly means that the issue they were closed as a duplicate of wasn't linked. That's ofc my bad, i didn't have that in mind.

In tao i wanted to do the same but misclicked on Close as completed. I also didn't mean to close all 10 of them in this repo as there's no , so thanks for reaching out. I'll reopen this one here then.


See tauri-apps/tauri#11928 (comment) for a general roadmap for gtk4 support (no timelines). At this point in time i doubt we can get rid of gtk3 in 2025 unless we get some serious help.

@FabianLars FabianLars reopened this Jan 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants