OffSequence2d ago
⚠️ CRITICAL: kitty terminal <0.47.0 vulnerable to integer overflow (CVE-2026-33642). Malicious escape sequences can cause heap memory corruption — no user action needed. Upgrade to 0.47.0+ now! https://radar.offseq.com/threat/cve-2026-33642-cwe-190-integer-overflow-or-wraparo-3fc58bfe #OffSeq #Vuln #KittyTerminal #Infosec
SharlatanMay 14
A fresh version of #kittyterminal is available in #Guix https://codeberg.org/guix/guix/pulls/7705
gnu: kitty: Update to 0.46.2.

<!-- Below is a checklist for package-related patches. For details please refer to [the manual](https://guix.gnu.org/manual/devel/en/html_node/Submitting-Patches.html). Common issues in the contribution process are also documented in the ["Contributing" chapter](https://guix.gnu.org/manua...

Codeberg.org
Crest of LightMar 21

I installed two terminals that I see a lot of on the web: Kitty and Ghostty, today I wrote a small little config file to get started with Kitty. As one of my favorite colors is orange and fonts Lucida Console (as it's readable) I began with assigning those basic things to my Kitty config file.

I need to get comfortable with config files again, as eventually it will be an essential part of my life. I do plan on going to a Systemd free NixOS, FreeBSD, or a few other options that have cropped up.

As my laundry is nearly done (comforter is in the dryer for a long dry cycle) this is a perfect little diversion to delay my boredom.

The website for further customization is:

https://sw.kovidgoyal.net/kitty/#configuring-kitty

#KittyTerminal #config #Linux

SmokeInFogMar 21

kitty 0.46.2 released - changelog

https://midwest.social/post/44931202

SmokeInFogMar 16

kitty 0.46.1 released - changelog

https://midwest.social/post/44743378

SmokeInFogMar 11

kitty 0.46.0 released - changelog

https://midwest.social/post/44533129

Rainer "friendica" SokollMar 10

kitty (1) kann übrigens Bilder im Terminal darstellen. Braucht vermutlich niemand, ist aber leider geil!

#Linux #kittyterminal

Jan AntošJan 23
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
Show threadJan AntošJan 21

#sixels do “compress” image data by its nature design, #libsixel is highly optimized, on the other side #kittyterminal protocol

Direct transmission (t=d):
RGB/RGBA -> base64 … huge data transfer
RGB/RGBA -> PNG -> base64 … better in size, significant overhead
RGB/RGBA -> zlib compression -> base64 … also significant overhead
RGB/RGBA -> PNG -> zlib compression -> base64 .. even bigger overhead

Simple file transmission (t=f)
Client needs access to file … Forget about #ssh

Temporary file transmission (t=t)
Client needs access to /tmp, /dev/shm … forget about ssh

Shared memory object (t=s)
Client needs to have access to POSIX shared memory object/Windows named shared memory object … forget about ssh.

So yes, kitty is “superior” protocol with superior performance, except it works as “superior” only on localhost and event that is questionable at least in case of #brow6el (ok I acknowledge thats this is very specific “hack”)

Jan AntošJan 21
#kittyterminal image protocol is literally unusable on #ssh, and thats the whole point of terminal apps. If we need something we need to improve the #sixels but let’s start with broader support and don’t excuse it is legacy bad protocol, because tbh it works really well even in Microsoft terminal.