The certificate is disabled both in the config file /etc/ca-certificates.conf and not present in /etc/ssl/certs. Afaics, there's no way to tell if this was disabled by the sysadmin or by the 20090624 version.
Can be "fixed" by enabling it in the postinst:
# do nothing when upgrading from intrepid or earlier
if ! dpkg --compare-versions "$2" lt 20080808'; then
# upgrading from karmic
if dpkg --compare-versions "$2" lt 20090625'; then
sed -i 's,^!\(mozilla/Equifax_Secure_Global_eBusiness_CA\.crt\)$,\1,' /etc/ca-certificates.conf
update-ca-certificates
fi
fi
but then, somebody might have disabled it by intent.
Given that this version was only present in the archive for a week early in the karmic release cycle, and not part of any release, the chance that end users are affected is very low.
not sure, how and if we want to fix this:
The certificate is disabled both in the config file /etc/ca- certificates. conf and not present in /etc/ssl/certs. Afaics, there's no way to tell if this was disabled by the sysadmin or by the 20090624 version.
Can be "fixed" by enabling it in the postinst:
# do nothing when upgrading from intrepid or earlier mozilla/ Equifax_ Secure_ Global_ eBusiness_ CA\.crt\ )$,\1,' /etc/ca- certificates. conf ca-certificates
if ! dpkg --compare-versions "$2" lt 20080808'; then
# upgrading from karmic
if dpkg --compare-versions "$2" lt 20090625'; then
sed -i 's,^!\(
update-
fi
fi
but then, somebody might have disabled it by intent.
Given that this version was only present in the archive for a week early in the karmic release cycle, and not part of any release, the chance that end users are affected is very low.