Quoting Anthony DeRobertis (2015-11-20 03:06:20)
> On 08/05/2015 07:11 AM, Thorsten Glaser wrote:
>> Bas Wijnen debian.org> writes:
>>
>>> Certificates are placed in /etc/ssl/certs/.
>> No, in /etc/ssl. /etc/ssl/certs/ is for Root CA certificates *only*.
>
> (sorry for responding to a very old mes
On 08/05/2015 07:11 AM, Thorsten Glaser wrote:
Bas Wijnen debian.org> writes:
Certificates are placed in /etc/ssl/certs/.
No, in /etc/ssl. /etc/ssl/certs/ is for Root CA certificates *only*.
(sorry for responding to a very old message)
Really? I've often put the local machine's cert(s) in
On 05/08/15 13:11, Thorsten Glaser wrote:
> Bas Wijnen debian.org> writes:
>
>> Certificates are placed in /etc/ssl/certs/.
>
> No, in /etc/ssl. /etc/ssl/certs/ is for Root CA certificates *only*.
>
Now that Let's Encrypt is progressing (they are almost in beta[1] now),
I thought it would be
Bas Wijnen debian.org> writes:
> Certificates are placed in /etc/ssl/certs/.
No, in /etc/ssl. /etc/ssl/certs/ is for Root CA certificates *only*.
bye,
//mirabilos
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@li
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Aug 02, 2015 at 05:44:06PM +0200, Christoph Anton Mitterer wrote:
> Some ideas that pop up in my mind:
> - Would be yet another location of privacy leak in Debian, where the
> system automatically calls "home" to some more commercial than
> com
Quoting Daniel Pocock (2015-08-02 18:49:16)
> On 02/08/15 17:44, Christoph Anton Mitterer wrote:
>> - Would be yet another location of privacy leak in Debian, where the
>> system automatically calls "home" to some more commercial than
>> community organisations.
>
> This would not be automatic.
On 02/08/15 17:44, Christoph Anton Mitterer wrote:
> On Sun, 2015-08-02 at 16:37 +0200, Daniel Pocock wrote:
>> I apologize for not being more explicit, this is the sort of thing I
>> was thinking too, it wouldn't be up to dpkg or postinst to guess or
>> insist on a particular CA. Rather, it w
On Sun, 2015-08-02 at 16:37 +0200, Daniel Pocock wrote:
> I apologize for not being more explicit, this is the sort of thing I
> was thinking too, it wouldn't be up to dpkg or postinst to guess or
> insist on a particular CA. Rather, it would be an optional prompt
> and there would be some scri
On 2 August 2015 16:20:51 CEST, Jonas Smedegaard wrote:
>Quoting Marco d'Itri (2015-08-02 12:36:19)
>> On Aug 02, Daniel Pocock wrote:
>>
>>> Does anybody prefer to see packages create certificates during
>>> postinst or is there any preference not to try that and let people
>do
>>> so manually
Quoting Marco d'Itri (2015-08-02 12:36:19)
> On Aug 02, Daniel Pocock wrote:
>
>> Does anybody prefer to see packages create certificates during
>> postinst or is there any preference not to try that and let people do
>> so manually?
> There is no point in trying to get a certificate from letsen
On Aug 02, Daniel Pocock wrote:
> Does anybody prefer to see packages create certificates during postinst
> or is there any preference not to try that and let people do so manually?
There is no point in trying to get a certificate from letsencrypt every
time you install a package if you already
On Sun, Aug 2, 2015 at 4:51 PM, Daniel Pocock wrote:
> Does anybody prefer to see packages create certificates during postinst
> or is there any preference not to try that and let people do so manually?
I certainly would not expect packages to call out to the Internet in
this situation, at least
Does anybody prefer to see packages create certificates during postinst
or is there any preference not to try that and let people do so manually?
The Let's Encrypt CA also has a client utility, letsencrypt[1], that
could be very useful from the postinst script.
With any CA, there can sometimes
13 matches
Mail list logo
