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 libsixel fork with CVE fixes #184

Closed
wants to merge 1 commit into from
Closed

Conversation

ctrlcctrlv
Copy link

img2sixel had two CVE's, and its maintainer disappeared. See saitoha/libsixel#154.

Myself and @dankamongmen are maintaining it now at libsixel/libsixel. Link to new repository.

Arch Linux etc. are distributing this version (libsixel 1.9+) now.

`img2sixel` had two CVE's, and its maintainer disappeared. See saitoha/libsixel#154.

Myself and @dankamongmen are maintaining it now at libsixel/libsixel. Link to new repository.

Arch Linux etc. are distributing this version (libsixel 1.9+) now.
tats added a commit that referenced this pull request Jun 21, 2021
@tats
Copy link
Owner

tats commented Jun 21, 2021

Instead, I've added the information of Debian's libsixel.
I expect it will follow the de fact upstream.

BTW, what do you think about CVE-2020-36120?
cf. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-36120
saitoha/libsixel#143

Anyway, thank you for fixing the bugs in libsixel.

@tats
Copy link
Owner

tats commented Apr 8, 2022

Debian's libsixel switched to the new upstream https://github.com/libsixel/libsixel.
Closing.

@tats tats closed this Apr 8, 2022
bptato pushed a commit to bptato/w3m that referenced this pull request Jul 29, 2023
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

Successfully merging this pull request may close these issues.

2 participants