Hi Axel-- On 08/08/2014 09:28 AM, Axel Beckert wrote: > 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.
yes, this is definitely on the agenda for the package. (see debian/TODO
for additional packaging work plans). I hope to get a sensible systemd
tcpcryptd.service file sorted out during debconf (anyone who wants to
help think this through should find me and we can find some hacking time).
there are a lot of possible nuances of how things could go wrong with
enabling such a service by default -- from making sure it handles
changes in network status properly, to questions about "phone-home"
behavior on startup, to concerns about client linkability, to
interaction with existing firewall rules, to the scary possibility of
locking out the administrator of a remote machine if something goes wrong.
We also probably need to do some work with upstream to improve some
details, and we probably need to add a system tcpcryptd user for program
to drop privileges to.
So for the moment, the package will be a tools-only package, not one
that supplies a system service in any automated way. But i'd be very
happy for help/suggestions/patches to add a system service that address
any of the above concerns.
--dkg
signature.asc
Description: OpenPGP digital signature
