Package: ladder Version: 0.0.2 Severity: wishlist So that I don't forget to implement it and in case someone else thinks of the same enhancement...
ladder is a bit awkward in that the secret part of the signing key needs to be accessible to the root user, but that assumes that the signing key already exists. ladder should accept an exported secret key as a file and export the public component to the ladder step itself. Scripting support could then just add that key before adding the step repository as an apt source. Each step would then have a particular key inside each step repository tarball and therefore easier to track what has been done just be checking the output of apt-key list. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ladder depends on: ii apt 0.8.15.9 ii gnupg 1.4.11-3 ii libconfig-inifiles-perl 2.68-1 ii liblocale-gettext-perl 1.05-7+b1 ii perl 5.14.2-7 ii reprepro 4.9.0-1 ladder recommends no packages. ladder suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
