[Tickets #11822] Subscribing to remote calendars returns SSL error

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/11822
------------------------------------------------------------------------------
  Ticket           | 11822
  Erstellt Von     | waste at lugh.ch
  Zusammenfassung  | Subscribing to remote calendars returns SSL error
  Warteschlange    | Kronolith
  Version          | 4.0.2
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


waste at lugh.ch (2012-12-06 10:43) hat geschrieben:

When subscribing to remote ICal calendars, the following error popup  
is returned when you activate the checkbox to display that remote  
calendar:

Zimbra error:
Problem with  
https://mail.example.org/service/user/username@example.org/Calendar:  
fopen(): SSL operation failed with code 1. OpenSSL Error messages:  
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate  
verify failed. fopen(): Failed to enable crypto.  
fopen(https://...@example.org/Calendar): failed to open stream:  
operation failed

Google Calendar error:
Problem with  
https://www.google.com/calendar/ical/user%40gmail.com/private-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/basic.ics: fopen(): SSL operation failed with code 1. OpenSSL Error messages: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed. fopen(): Failed to enable crypto. fopen(https://www.google.com/calendar/ical/user%40gmail.com/private-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/basic.ics): failed to open stream: operation  
failed

This has been tested with:
- Google unauthenticated ICal, valid certificate (I suppose)
- Zimbra authenticated ICal, self-signed certificate
- Both with HTTPS URLs

Server OS: Debian stable (squeeze) 64bit

This worked in Horde 4, so I suspect the error could even be in a PEAR  
package.