|
|
|
|
|
by subway
3133 days ago
|
|
After initially recoiling in horror at running a `curl|bash` installer, I opened the installer in a browser planning on reading the install script. "Helpfully" the script is served up as `binary/octet-stream`, so instead of looking at it in the browser, I got to open it in an editor. From there, it looks like the script does little more than add the `rpmfusion-free-release`, `rpmfusion-nonfree-release` and `folkswithhats-release` repositories. Of course since we started the install process through a shady insecure means, we should add the repos the same way. So every repo gets added via `dnf -y --nogpgcheck install https://url-to-repo-release-package`. I went to browse the `folkswithhats` repo, but found it's hosted on AWS S3 and doesn't provide a directory index. |
|
https://github.com/folkswithhats/fedy
If the "--nogpgcheck" bothers you, a simple text replace over the source code solves it.
Same with the "curl|bash" thing, you are not obligated to run it that way, you can just clone the repo and run it however you want, it is open source!
It is funny the way people overreact with things like this with projects that are open source but are ok installed closed source software and feel safe because they got them from the official repos...