[Tickets #13730] Re: Implementation of peer verification in TLS connections

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: https://bugs.horde.org/ticket/13730
------------------------------------------------------------------------------
  Ticket             | 13730
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Implementation of peer verification in TLS connections
  Queue              | Horde Framework Packages
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-12-01 15:44) wrote:

$GLOBALS['conf'] does not exist in Socket_Client.  Socket_Client is an  
independent library from the Horde application, so it cannot use  
Horde-specific variables like $conf.  So you will need to add these as  
config options to the Horde_Socket constructor (which, in turn, means  
they need to be added as config options in both the Horde_Imap_Client  
library and the Horde_Smtp library).

And this means that these options cannot be globally defined in  
Horde's conf.xml.  Well, actually they can (and be used as defaults),  
but there also has to be options to be able to override these defaults  
in every location where we are using the Socket Client library.  i.e.  
these defaults can be defined with IMAP authentication, POP3  
atuhentication, SMTP authentication, and in IMP both when configuring  
the IMAP/POP3 backend and the SMTP backend.

That's really the main reason this hasn't been added to Horde  
previously - since it's the configuration code that is both messy and  
a PITA.  (Unfortunately, this is an issue with security/encryption  
options in general, so there's not a ton we can do about that).