#kittyterminal — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #kittyterminal, aggregated by home.social.
-
Kitty Terminal Security PSA
If you are using the kitty terminal @kittyterminal, go get your security update!
"The handle_compose_command() function in kitty/graphics.c performs bounds validation on composition offsets using unsigned 32-bit arithmetic that is subject to integer wrapping. An attacker who can write escape sequences to a kitty terminal (e.g., via a malicious file, SSH login banner, or piped content) can supply crafted x_offset/y_offset values that pass the bounds check after wrapping but cause massive out-of-bounds heap memory access in compose_rectangles().
No user interaction is required. No non-default configuration is required. The attacker only needs the ability to produce output in a kitty terminal window."
https://github.com/kovidgoyal/kitty/security/advisories/GHSA-qfgm-2c64-6x3x
-
Kitty Terminal Security PSA
If you are using the kitty terminal @kittyterminal, go get your security update!
"The handle_compose_command() function in kitty/graphics.c performs bounds validation on composition offsets using unsigned 32-bit arithmetic that is subject to integer wrapping. An attacker who can write escape sequences to a kitty terminal (e.g., via a malicious file, SSH login banner, or piped content) can supply crafted x_offset/y_offset values that pass the bounds check after wrapping but cause massive out-of-bounds heap memory access in compose_rectangles().
No user interaction is required. No non-default configuration is required. The attacker only needs the ability to produce output in a kitty terminal window."
https://github.com/kovidgoyal/kitty/security/advisories/GHSA-qfgm-2c64-6x3x
-
Kitty Terminal Security PSA
If you are using the kitty terminal @kittyterminal, go get your security update!
"The handle_compose_command() function in kitty/graphics.c performs bounds validation on composition offsets using unsigned 32-bit arithmetic that is subject to integer wrapping. An attacker who can write escape sequences to a kitty terminal (e.g., via a malicious file, SSH login banner, or piped content) can supply crafted x_offset/y_offset values that pass the bounds check after wrapping but cause massive out-of-bounds heap memory access in compose_rectangles().
No user interaction is required. No non-default configuration is required. The attacker only needs the ability to produce output in a kitty terminal window."
https://github.com/kovidgoyal/kitty/security/advisories/GHSA-qfgm-2c64-6x3x
-
Kitty Terminal Security PSA
If you are using the kitty terminal @kittyterminal, go get your security update!
"The handle_compose_command() function in kitty/graphics.c performs bounds validation on composition offsets using unsigned 32-bit arithmetic that is subject to integer wrapping. An attacker who can write escape sequences to a kitty terminal (e.g., via a malicious file, SSH login banner, or piped content) can supply crafted x_offset/y_offset values that pass the bounds check after wrapping but cause massive out-of-bounds heap memory access in compose_rectangles().
No user interaction is required. No non-default configuration is required. The attacker only needs the ability to produce output in a kitty terminal window."
https://github.com/kovidgoyal/kitty/security/advisories/GHSA-qfgm-2c64-6x3x
-
Kitty Terminal Security PSA
If you are using the kitty terminal @kittyterminal, go get your security update!
"The handle_compose_command() function in kitty/graphics.c performs bounds validation on composition offsets using unsigned 32-bit arithmetic that is subject to integer wrapping. An attacker who can write escape sequences to a kitty terminal (e.g., via a malicious file, SSH login banner, or piped content) can supply crafted x_offset/y_offset values that pass the bounds check after wrapping but cause massive out-of-bounds heap memory access in compose_rectangles().
No user interaction is required. No non-default configuration is required. The attacker only needs the ability to produce output in a kitty terminal window."
https://github.com/kovidgoyal/kitty/security/advisories/GHSA-qfgm-2c64-6x3x
-
⚠️ 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
-
⚠️ 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
-
⚠️ 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
-
⚠️ 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
-
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:
-
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:
-
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:
-
kitty (1)kann übrigens Bilder im Terminal darstellen. Braucht vermutlich niemand, ist aber leider geil! -
kitty (1)kann übrigens Bilder im Terminal darstellen. Braucht vermutlich niemand, ist aber leider geil! -
kitty (1)kann übrigens Bilder im Terminal darstellen. Braucht vermutlich niemand, ist aber leider geil! -
kitty (1)kann übrigens Bilder im Terminal darstellen. Braucht vermutlich niemand, ist aber leider geil! -
kitty (1)kann übrigens Bilder im Terminal darstellen. Braucht vermutlich niemand, ist aber leider geil! -
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
-
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
-
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
-
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
-
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
-
#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 overheadSimple file transmission (t=f)
Client needs access to file … Forget about #sshTemporary file transmission (t=t)
Client needs access to /tmp, /dev/shm … forget about sshShared 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”)
-
#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 overheadSimple file transmission (t=f)
Client needs access to file … Forget about #sshTemporary file transmission (t=t)
Client needs access to /tmp, /dev/shm … forget about sshShared 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”)
-
#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 overheadSimple file transmission (t=f)
Client needs access to file … Forget about #sshTemporary file transmission (t=t)
Client needs access to /tmp, /dev/shm … forget about sshShared 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”)
-
#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 overheadSimple file transmission (t=f)
Client needs access to file … Forget about #sshTemporary file transmission (t=t)
Client needs access to /tmp, /dev/shm … forget about sshShared 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”)
-
#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.
-
#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.
-
#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.
-
#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.
-
How much a #kittyterminal image protocol is deemed as superior to #sixels, it is piece of crap. It breaks color terminal sequences, literally impossible to print image move cursor on location xy and print with sequences colored text on top of image. Or at least it is so complicated close to unusable from development experience.
-
How much a #kittyterminal image protocol is deemed as superior to #sixels, it is piece of crap. It breaks color terminal sequences, literally impossible to print image move cursor on location xy and print with sequences colored text on top of image. Or at least it is so complicated close to unusable from development experience.
-
How much a #kittyterminal image protocol is deemed as superior to #sixels, it is piece of crap. It breaks color terminal sequences, literally impossible to print image move cursor on location xy and print with sequences colored text on top of image. Or at least it is so complicated close to unusable from development experience.
-
How much a #kittyterminal image protocol is deemed as superior to #sixels, it is piece of crap. It breaks color terminal sequences, literally impossible to print image move cursor on location xy and print with sequences colored text on top of image. Or at least it is so complicated close to unusable from development experience.
-
How much a #kittyterminal image protocol is deemed as superior to #sixels, it is piece of crap. It breaks color terminal sequences, literally impossible to print image move cursor on location xy and print with sequences colored text on top of image. Or at least it is so complicated close to unusable from development experience.
-
Nothing beats the buttery-smooth bliss of a minimal Linux laptop for #DevX.
Instant “I’m home” vibes every boot 🐧✨
(Main rig still Windows for my legacy bullshit though)
#Linux #CachyOS #KDE #KittyTerminal -
Nothing beats the buttery-smooth bliss of a minimal Linux laptop for #DevX.
Instant “I’m home” vibes every boot 🐧✨
(Main rig still Windows for my legacy bullshit though)
#Linux #CachyOS #KDE #KittyTerminal -
Nothing beats the buttery-smooth bliss of a minimal Linux laptop for #DevX.
Instant “I’m home” vibes every boot 🐧✨
(Main rig still Windows for my legacy bullshit though)
#Linux #CachyOS #KDE #KittyTerminal -
Did you know that you can run @ratatui_rs inside @ratatui_rs inside @kittyterminal inside @kittyterminal over #SSH?
Now you know.
Explanation in the alttext.
-
Did you know that you can run @ratatui_rs inside @ratatui_rs inside @kittyterminal inside @kittyterminal over #SSH?
Now you know.
Explanation in the alttext.
-
Did you know that you can run @ratatui_rs inside @ratatui_rs inside @kittyterminal inside @kittyterminal over #SSH?
Now you know.
Explanation in the alttext.
-
Did you know that you can run @ratatui_rs inside @ratatui_rs inside @kittyterminal inside @kittyterminal over #SSH?
Now you know.
Explanation in the alttext.
-
Did you know that you can run @ratatui_rs inside @ratatui_rs inside @kittyterminal inside @kittyterminal over #SSH?
Now you know.
Explanation in the alttext.
-
Give Kitty terminal a glow-up with our video. 🪄✨
-
Give Kitty terminal a glow-up with our video. 🪄✨
-
Give Kitty terminal a glow-up with our video. 🪄✨
-
Give Kitty terminal a glow-up with our video. 🪄✨
-
Give Kitty terminal a glow-up with our video. 🪄✨
-
I switched from Ghostty to #kittyTerminal so I could use the latest #HelixEditor light/dark mode theme functionality, but now I think I'll probably stick with kitty. It's so nice, and these custom icons are delightful! https://github.com/DinkDonk/kitty-icon
-
I switched from Ghostty to #kittyTerminal so I could use the latest #HelixEditor light/dark mode theme functionality, but now I think I'll probably stick with kitty. It's so nice, and these custom icons are delightful! https://github.com/DinkDonk/kitty-icon