https://github.com/MichaelSebero/CoolRune
CoolRune is a modified variant of Artix which is focused on performance, privacy and security.
The manual included with CoolRune lists all of the features which are included in this install script.
https://raw.githubusercontent.com/MichaelSebero/CoolRune/main/CoolRune%20Manual
If you have any questions or ideas message me on Element at @coolrune:matrix.org 8)
I see the you have removed the konsole and dnscrypt-proxy binaries that I had concerns about in the last thread you posted about Coolrune https://forum.artixlinux.org/index.php/topic,4922
So thanks for that.
Your own binary you install at /-CoolRune-/Programs/Login-Sound/StartSound still exists so my general security warning sort of still remains though thankfully, AFAICT, nothing your script installs actually runs this binary automatically.
I think I understand why you turn the 4 line script startup_sound.py into a self contained python executable StartSound. It depends on pydub and pydub is only available in the AUR.
Another way to approach playing your startup sound at login without needing to install a binary:
Add alsa-utils to the list of packages you install and install a valid .desktop file in ~/.config/autostart with
Exec=aplay /-CoolRune-/System_Sounds/Login.wav
Simple and zero security concerns.
Those 2 binaries earlier that you mentioned the other day were accidentally copied over when routing the configuration paths. I'll try out a better way in delivering the startup sound but as it is right now it does what it's supposed to do. The startup sound doesn't play automatically yet because I didn't know where to find the automatic startup applications config file until yesterday, StartSound will be made functional in the new update.
The reason why StartSound is an executable is due to XFCE's startup application menu not allowing a python script to run when I tried to run it. Also I know that not everyone likes startup sounds so I wanted to make it easy to disable in the startup applications menu. StartSound is just an EXE version of the python script I have on my GitHub.
https://github.com/MichaelSebero/Login-Sound-for-Linux
If someone turned my python script into an EXE through PyCharm they should get the same code as the one which is included with CoolRune.
startupsound.desktop
With pydub installed:
[Desktop Entry]
Comment=Xfce startup sound
Exec=python3 /tmp/-CoolRune-/System_Sounds/sound.py
GenericName[en_GB]=Xfce startup sound
GenericName=Xfce startup sound
Name[en_GB]=Startsound
Name=Startsound
Terminal=false
Type=Application
With alsa-utils installed
[Desktop Entry]
Comment=Xfce startup sound
Exec=aplay /tmp/-CoolRune-/System_Sounds/Login.wav
GenericName[en_GB]=Xfce startup sound
GenericName=Xfce startup sound
Name[en_GB]=Startsound
Name=Startsound
Terminal=false
Type=Application
Either work placed in ~/.config/autostart or /etc/xdg/autostart/ (but ~/.config/autostart if you want the user to be able to easily disable them) under KDE and should work in Xfce ?
But the whole point is there is no way of them knowing that the binary is truly produced from that code. And a less advanced user would just be running the the script blind. Why bother with the binary when there are arguably better, but certainly safer, solutions ?
It's nothing personal. But if someone posts a script on here that I believe is a security risk I'm going to point it out.
But I'm a nobody. You don't have to listen to me. Nor does anyone else :)
Referencing the python script works now in XFCE startup applications. I suppose prior I didn't put the 3 in or something.