4 ms·
This broke apt-get update on my system, by adding an https update method. I assume the author must have apt-transport-https installed, or something.
by nickodell 10y ago
This broke apt-get update on my system, by adding an https update method. I assume the author must have apt-transport-https installed, or something.
- mherrmann 10y agoSorry about that :/ It adds /etc/apt/sources.list.d/fman.list so you can update fman with apt. Isn't non-https unsafe?
- dewey 10y agoNo, because the packages are already signed with gpg. That way you can verify the checksum already.
- mherrmann 10y agoInteresting (sorry, I'm new to Linux packaging). So would it be safe then to replace by http? (Not that I'd take this at face value, but I am interested in your opinion)
- dewey 10y agoHere's some more information that sums that up quite nicely, most default mirrors are http so I'd say it's safe enough. http://unix.stackexchange.com/questions/90227/why-there-is-no-https-transport-for-debian-apt-tool/90321#90321 http://unix.stackexchange.com/questions/90227/why-there-is-n...
- mherrmann 10y agoThanks!
- rawfan 10y agoWhile we're at it, you absolutely need to remove that cronjob. No package should run their own update. That's the domain of the systems package manager.
- mherrmann 10y agoI've removed it: https://fman.io/blog/an-apology-to-linux-users/ https://fman.io/blog/an-apology-to-linux-users/