Dear Philipp,
On 07.11.2015 14:48, Philipp Hübner wrote:
> Anyway, I opened an issue with this feature request in the upstream bug
> tracker at https://github.com/processone/ejabberd/issues/826 .
Many thanks!
Greetings,
Paul
Hi,
Am 06.11.2015 um 21:10 schrieb martin f krafft:
> Having both the key and cert in one file could be considered a
> feature. But since the two data have different security models, and
> we do not have in-file differentiation (e.g. protect the key while
> let people read the cert), using two fil
also sprach Rhonda D'Vine [2015-11-07 01:03 +1300]:
> Hmm, the PEM format isn't that uncommon, shouldn't that (also) be
> turned into a feature request to Let's Encrypt? There for sure is more
> than just ejabberd using PEM format, I've seen and touched a fair amount
> of services over time that
* Paul Muster [2015-11-06 13:50:28 CET]:
> On 06.11.2015 13:03, Rhonda D'Vine wrote:
> > * Paul Muster [2015-11-04 21:21:39 CET]:
>
> >> It's especially _necessary_ to split key, cert and chain to different
> >> files to be able to use Let's Encrypt certificates.
>
> This mistakable wording has
On 06.11.2015 13:03, Rhonda D'Vine wrote:
> * Paul Muster [2015-11-04 21:21:39 CET]:
>> It's especially _necessary_ to split key, cert and chain to different
>> files to be able to use Let's Encrypt certificates.
This mistakable wording has been clarified >4 hours before your e-mail.
> Said th
* Paul Muster [2015-11-04 21:21:39 CET]:
> It's especially _necessary_ to split key, cert and chain to different
> files to be able to use Let's Encrypt certificates.
Hmm, the PEM format isn't that uncommon, shouldn't that (also) be
turned into a feature request to Let's Encrypt? There for sure
On 04.11.2015 21:57, Holger Weiß wrote:
> * Paul Muster [2015-11-04 21:21]:
>> It's especially _necessary_ to split key, cert and chain to different
>> files to be able to use Let's Encrypt certificates.
>
> I haven't played with Let's Encrypt yet, but I guess you could just run
>
> $ cat key.p
also sprach Holger Weiß [2015-11-05 09:57 +1300]:
> I haven't played with Let's Encrypt yet, but I guess you could just run
> $ cat key.pem cert.pem chain.pem > ejabberd.pem
> after doing whatever has to be done to maintain their certificates, no?
Yes, of course, but that's an additional step tha
* Paul Muster [2015-11-04 21:21]:
> It's especially _necessary_ to split key, cert and chain to different
> files to be able to use Let's Encrypt certificates.
I haven't played with Let's Encrypt yet, but I guess you could just run
$ cat key.pem cert.pem chain.pem > ejabberd.pem
after doing wha
Dear Ejabberd-Team,
On Thu, 4 Dec 2014 15:11:41 +0100 martin f krafft wrote:
> Package: ejabberd
> Version: 14.07-3
> Severity: wishlist
> Tags: upstream
>
> SSL cert and key usually are not in the same file. The key usually
> has tighter security. Please let me poit ejabberd to a separate
> keyf
Package: ejabberd
Version: 14.07-3
Severity: wishlist
Tags: upstream
SSL cert and key usually are not in the same file. The key usually
has tighter security. Please let me poit ejabberd to a separate
keyfile, not just the certfile, such that it then loads the key from
there.
-- System Information
11 matches
Mail list logo
