6.0.0-alpha10
▾
Tasks
New Task
Search
Photos
Wiki
▾
Tickets
New Ticket
Search
dev.horde.org
Toggle Alerts Log
Help
5/16/25
H
istory
A
ttachments
C
omment
W
atch
Download
Comment on [#13730] Implementation of peer verification in TLS connections
*
Your Email Address
*
Spam protection
Enter the letters below:
__.._.. ..__.. (__ | |\ || || .__)_|_| \||__||___
Comment
> $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).
Attachment
Watch this ticket
N
ew Ticket
M
y Tickets
S
earch
Q
uery Builder
R
eports
Saved Queries
Open Bugs
Bugs waiting for Feedback
Open Bugs in Releases
Open Enhancements
Enhancements waiting for Feedback
Bugs with Patches
Enhancements with Patches
Release Showstoppers
Stalled Tickets
New Tickets
Horde 5 Showstoppers