> Are there any known workarounds for rpm 4.11.3 (as it's a system version so
> I'm stuck with it in the office)?
> Maybe there is a patch that could be applied to 4.11.3 without a full upgrade
> (so I could convince our admins to apply it)?
RPM 4.11.3 is horribly insecure, so unless you are using `repo_gpgcheck=1` on
all of your repositories you have bigger problems.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1770#issuecomment-912684405
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
