Summary
It looks like a vulnerability. Helix should not rely on a properly installed umask or its equivalent in the OS being used. A temporary file for writing should be created with the most secure access rights.
Reproduction Steps
- umask 0 (default umask usally is 022)
- chmod 0600 10gb_sensitive_content.txt
- hx 10gb_sensitive_content.txt
- type :w in helix
- while file saving
ls -lha 10gb_sensitive_content.txt | cut -d' ' -f1
What I see: -rw-rw-rw-
Expected: -rw-------
After saving is completed permissions is as original file, e.g. -rw-------
Helix log
No response
Platform
Linux
Terminal Emulator
Alacritty
Installation Method
source
Helix Version
helix 24.7 (2a2bc79)
Summary
It looks like a vulnerability. Helix should not rely on a properly installed
umaskor its equivalent in the OS being used. A temporary file for writing should be created with the most secure access rights.Reproduction Steps
ls -lha 10gb_sensitive_content.txt | cut -d' ' -f1What I see:
-rw-rw-rw-Expected:
-rw-------After saving is completed permissions is as original file, e.g.
-rw-------Helix log
No response
Platform
Linux
Terminal Emulator
Alacritty
Installation Method
source
Helix Version
helix 24.7 (2a2bc79)