3 ms·
I can think of some uses: * Some package managers use it to sign binary packages. (Think apt-get) * I personally use it in shell scripts to avoid storing som
by asveikau 8y ago
I can think of some uses:
* Some package managers use it to sign binary packages.
(Think apt-get)
* I personally use it in shell scripts to avoid storing some secrets in the clear on disk. (Use case similar to ssh-agent)
- jancsika 8y agoNeither of those classes of user has the expertise to avoid picking "the weak algorithms."
- asveikau 8y agoI more or less trust the maintainers of dpkg and similar can figure it out or have someone point it out to them. My own shell scripts are maybe more iffy, as I am not myself an expert, but my personal use doesn't see wide distribution.
- moosingin3space 8y agoUnfortunately, even the maintainers of dpkg/apt, who rely on GPG extensively, don't manage to plug all holes: https://blog.packagecloud.io/eng/2018/02/21/attacks-against-secure-apt-repositories/ https://blog.packagecloud.io/eng/2018/02/21/attacks-against-... Personally, I'm of the opinion that APIs should be as misuse-resistant as possible, and GPG is notoriously intransigent about actually acting as a well-designed API. Additionally, The Update Framework (TUF, https://theupdateframework.github.io/ https://theupdateframework.github.io/) prevents these issues by design.
- asveikau 8y agoThanks for that. I know that Debian has had security blunders in the past (RNG problems anyone?) so as I typed it I had some hunches, but... Importantly though, it's a big project which in this specific instance meant that someone on earth did end up scrutinizing and publishing exactly the sort of thing you linked.