[Pkg-postgresql-public] Bug#743918: Bug#743918: Adding a debconf question to control default ssl behaviour?

[Martin Pitt]

Christoph Berg [2014-04-08 12:38 +0200]:
> 1) leave ssl = on
> 2) add a low priority debconf question about the default, defaulting to "on"
> 3) add a high priority debconf question about the default, defaulting to "on"
> 4) add a high priority debconf question about the default, defaulting to "off"
> 5) add a low priority debconf question about the default, defaulting to "off"
> 6) set ssl = off


I'm fine with 1 or 2. I'd veto a high-priority question as there
really is a sensible default that works, and a debconf question is
quite a burden to see (especially in environments which want to set up
everything noninteractively).

Also, this shouldn't affect local connections -- you'd usually talk
through the Unix socket for that, which is much less overhead and also
has better credential management?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20140408/20a432f8/attachment.sig>