Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introducing Script For Updating Spotube Binaries Via .tar.xz On Linux #1988

Closed

Conversation

ksaadDE
Copy link
Contributor

@ksaadDE ksaadDE commented Oct 10, 2024

Hi, with regard to the last updates in a row, due to the 403 API issue fix.

The current approach is not time efficient. I wanted something more automated. Therefore I am contributing and sharing it among yall.

  • adds the bash script to update spotube either on aarch64 or on x86_64
  • adds a logfile, using iso datetimes and the download url (for knowing when the last update was and what version)
  • Script creates necessary folder (if not existent) and symlink /usr/bin/spotube

Script can be moved to /usr/bin/updatespotube with chmod 0700 /usr/bin/updatespotube&& chown root:root /usr/bin/updatespotube`, as a root only executable (tested). Possibly it can be run with a cronjob within crontab (untested).

Untared files can be run as group and "other" (so non-root). Editing only works as root-user. The lastupdate.txt is locked to root-access only.

@KRTirtho
Copy link
Owner

Thanks for the contribution

But sorry but this requires super user permissions (/usr/** usage) and can be vulnerable for users if not maintained correctly.
Also, Spotube generally prefers Flatpak over distro package managers. So for automated updates, using Flatpak instead of manually updating through a script is preferred.

@KRTirtho KRTirtho closed this Oct 17, 2024
@ksaadDE
Copy link
Contributor Author

ksaadDE commented Nov 12, 2024

Hi @KRTirtho,

The directory and user is changeable, and the whole script is a super user script.
There stems no imminent security issue from that.

AppImage would be great, flatpak requires installation of an additional tool that introduces new vulnerability possibilities, and seems unnecessary.

That's why I opted for the tar.xz, its easier and has no prerequisites. It can be fully automated and adjusted.

@ksaadDE
Copy link
Contributor Author

ksaadDE commented Nov 12, 2024

BTW the flatpak repos were longer outdated than the tar, so thats another plus for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants