https://bugs.openldap.org/show_bug.cgi?id=8628
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8205
--- Comment #16 from OndÅ™ej KuznÃk <ondra(a)mistotebe.net> ---
Everything except attachment 671 is already applied as part of
https://bugs.openldap.org/show_bug.cgi?id=8205
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8205
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8628
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8485
--- Comment #11 from ahnolds(a)gmail.com <ahnolds(a)gmail.com> ---
(In reply to Howard Chu from comment #10)
> (In reply to Michael Ströder from comment #9)
> > I concur that lacking support for encrypted private keys is a real
> > deficiency!
> >
> > In general OpenLDAP should aim to reach more flexibility for the TLS
> > configuration, e.g. like Apache httpd. Encrypted private keys for both
> > server and client side is one aspect of that.
>
> We have never needed to add explicit support, since OpenSSL prompted for
> a passphrase itself, when needed.
>
> https://www.openldap.org/lists/openldap-software/200210/msg00718.html
It prompts for the passphrase on the controlling terminal, which is only
helpful for command-line based applications. For any application run through a
GUI/web server/etc, there won't be any way for the user to enter the passphrase
as is. And in fact, the call to use the key will hang (forever IIRC) waiting
for a passphrase to be typed on the terminal.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8485
--- Comment #10 from Howard Chu <hyc(a)symas.com> ---
(In reply to Michael Ströder from comment #9)
> I concur that lacking support for encrypted private keys is a real
> deficiency!
>
> In general OpenLDAP should aim to reach more flexibility for the TLS
> configuration, e.g. like Apache httpd. Encrypted private keys for both
> server and client side is one aspect of that.
We have never needed to add explicit support, since OpenSSL prompted for
a passphrase itself, when needed.
https://www.openldap.org/lists/openldap-software/200210/msg00718.html
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8485
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=7221
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=7221
Ryan Tandy <ryan(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8485
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8446
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |VERIFIED
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8734
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8734
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugs.openldap.org/s
| |how_bug.cgi?id=8446
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8446
OndÅ™ej KuznÃk <ondra(a)mistotebe.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8446
--- Comment #10 from nivanova(a)symas.com <nivanova(a)symas.com> ---
This ITS is no longer relevant, since a lot of changes were made to the design
and implementation, and all changes were already submitted as ITS#8734.
asyncmeta in master is currently up-to-date.
--
You are receiving this mail because:
You are on the CC list for the bug.