Hi: I've been surprised by the default to "no" too.
While I understand why that's the case (so there's no chance to hijack the system by a rogue puppetmaster upon puppet client installalation), I don't see why the option is not managed by debconf defaulting to "no" (won't start at boot time). This way, you can have a secured install on unmanaged environments while making things easier for those that understand the implications but still want/need the package to autoconfigure the system when installed (currently it basically blocks an automatic deploy unless you release a local puppet package). Cheers. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
