> > [debhelper] should check whether the corresponding file exists under
> > /etc/rc?.d before starting them in postinst or stopping them in postrm.
>
> (That is, we should check whether /etc/rcN.d/{S,K}??script exists
> where N is the current runlevel and start or stop the script
> appropriately
Ok,
I checked current situation and looked in to rpm.
[EMAIL PROTECTED] pwd
/pub/debian/dists/potato
[EMAIL PROTECTED] for i in */binary-i386/*/*.deb; do echo $i; done | wc -l \
> 2>/dev/null
3282
[EMAIL PROTECTED] for i in */binary-i386/*/*.deb; do dpkg-deb -I $i|grep
md5sums \
> 2>/dev/null;
> I have a different memory of events. This proposal was brought
> up on this list, and was shot down because
> a) It really provides no security.
It is not for *this* security reason (crackers, hackers and others)
> b) It would bloat the packaging system, when it does not really
> I doubt the usefullness (dpkg is no backup system). But I will not object.
> Indeed, I see some usefulness, but I want to know more about the drawbacks:
> How do you want to verify the sums (using cruft, maybe?). How long will it
> need to check the whole fs, how much disk space will the md5sums
I think DEBIAN/md5sums file should be required for all packages.
md5sums is very useful for security reasons (trojans, fs crash,
unexpected file modification) but a lot of important packages
(sysvinit, dpkg, debianutils, bash, adduser, etc.) don't have
this integrity verification.
I propose any D
5 matches
Mail list logo
