Re: Bug#592115: apt seems to somehow use ~/.gnupg dir when checking package integrity which might be used for security attacks

On Sat, 2010-08-07 at 21:27 +0200, Julian Andres Klode wrote: > As everyone should know, dpkg unpacks the source packages and verifies > them using gpg. APT knows that the package is secure, because the source > is secure. Ah I've missed that this is from the debsig, and not from checking the integ

cleaning up dead triggers

Hey. I've recently noted that my systems have files in /var/lib/dpkg/triggers, which are no longer there on fresh installations. For example: /var/lib/dpkg/triggers/resolvconf-event /var/lib/dpkg/triggers/rkhunter-update-database which seem to have been previously used by their respective packag

PATH in maintainer scripts taken from env that calls dpkg

Hey. Not sure whether this is a bug or intended behaviour,... but I've just noticed that is seems that when e.g. purging a package postrm will see the PATH as it was set in the env from which dpkg --pruge was invoked. I.e. there is no "sanitisation" to some static value like "/usr/sbin:/usr/bin:/