Releases: BusKill/buskill-app
Releases · BusKill/buskill-app
Public Build Artifact: Windows 10135110827
10135110827_windows add exception to log
Public Build Artifact: Mac 10135110827
10135110827_mac add exception to log
Public Build Artifact: Linux 10135110827
10135110827_linux add exception to log
Public Build Artifact: Windows 10128180705
10128180705_windows better exception handling in root child harden
Public Build Artifact: Mac 10128180705
10128180705_mac better exception handling in root child harden
Public Build Artifact: Linux 10128180705
10128180705_linux better exception handling in root child harden
Public Build Artifact: Windows 10127826629
attempt to self-harden root_child This commit adds a step to the start of the root_child_mac binary to harden the root_child_mac binary. Basically it's self-hardening The reason we do this is because (due to technical restrictions in .dmg files), we can't distribute a .dmg with a file that's owned by root. When the user first installs BusKill, the root_child_mac binary will be owned by their user. This isn't the worst thing in the world, and we do allow spawning a root_child process as root if it's owned by the current user. But, it's safer if it's owned by root:root, so we harden it the first time it launches. * https://github.com/BusKill/buskill-app/issues/77#issuecomment-2254299923
Public Build Artifact: Mac 10127826629
attempt to self-harden root_child This commit adds a step to the start of the root_child_mac binary to harden the root_child_mac binary. Basically it's self-hardening The reason we do this is because (due to technical restrictions in .dmg files), we can't distribute a .dmg with a file that's owned by root. When the user first installs BusKill, the root_child_mac binary will be owned by their user. This isn't the worst thing in the world, and we do allow spawning a root_child process as root if it's owned by the current user. But, it's safer if it's owned by root:root, so we harden it the first time it launches. * https://github.com/BusKill/buskill-app/issues/77#issuecomment-2254299923
Public Build Artifact: Linux 10127826629
attempt to self-harden root_child This commit adds a step to the start of the root_child_mac binary to harden the root_child_mac binary. Basically it's self-hardening The reason we do this is because (due to technical restrictions in .dmg files), we can't distribute a .dmg with a file that's owned by root. When the user first installs BusKill, the root_child_mac binary will be owned by their user. This isn't the worst thing in the world, and we do allow spawning a root_child process as root if it's owned by the current user. But, it's safer if it's owned by root:root, so we harden it the first time it launches. * https://github.com/BusKill/buskill-app/issues/77#issuecomment-2254299923
Public Build Artifact: Windows 10127516447
bump libusb-1.0.23 to libusb-1.0.27 * https://github.com/BusKill/buskill-app/issues/87