Package: tcpcryptd Version: 0.2+git20140723-1 Severity: wishlist Hi Daniel,
while it seems that the provided /usr/share/doc/tcpcryptd/examples/launch_tcpcryptd.sh seems to take care of making the user aware that starting it may interrupt existing connections, I think, it would be very useful and following the idea of opportunistic encryption if tcpcryptd would be started by default, e.g. via some init.d script. Maybe a debconf question of priority low or medium could ask the user if it should be enabled by default, with the default set to yes. TIA! -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (110, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.15-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tcpcryptd depends on: ii libc6 2.19-7 ii libcap2 1:2.24-4 ii libnetfilter-queue1 1.0.2-2 ii libnfnetlink0 1.0.1-3 ii libssl1.0.0 1.0.1i-1 ii libtcpcrypt0 0.2+git20140723-1 ii zlib1g 1:1.2.8.dfsg-1 tcpcryptd recommends no packages. tcpcryptd 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
