6.0.0-beta1
9/24/25

[#13017] cant import S/MIME private certificate with czech chars
Summary cant import S/MIME private certificate with czech chars
Queue IMP
Queue Version 6.1.4
Type Bug
State No Feedback
Priority 1. Low
Owners
Requester cernik (at) fel (dot) cvut (dot) cz
Created 03/06/2014 (4220 days ago)
Due
Updated 03/21/2014 (4205 days ago)
Assigned 03/07/2014 (4219 days ago)
Resolved 03/21/2014 (4205 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
03/21/2014 12:14:33 PM Jan Schneider State ⇒ No Feedback
 
03/07/2014 09:49:44 AM Jan Schneider State ⇒ Feedback
 
03/06/2014 11:33:01 PM Michael Slusarz Comment #3 Reply to this comment
I'm assuming you have non-UTF8 text in your x.509 cert.  IIRC, X509 
certs are supposed to be UTF-8 only in the recent RFCs.
03/06/2014 02:37:59 PM cernik (at) fel (dot) cvut (dot) cz Comment #2 Reply to this comment
hm .. seen to be problem also here

\/           /
C e r n i k
03/06/2014 02:34:52 PM cernik (at) fel (dot) cvut (dot) cz Comment #1
Priority ⇒ 1. Low
Type ⇒ Bug
Summary ⇒ cant import S/MIME private certificate with czech chars
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
State ⇒ Unconfirmed
Reply to this comment
If i import private S/MIME certificate where my last name is in czech 
language then imp says Certificate was imported succesfully but 
nothing changed (technically no certificate imported).

In log is this information
2014-03-06T15:19:46+01:00 WARN: HORDE [imp] PHP ERROR: json_encode(): 
Invalid UTF-8 sequence in argument [pid 12438 on line 314 of 
"/usr/share/php/Horde/Prefs/Scope.php"]
2014-03-06T15:19:46+01:00 DEBUG: HORDE 1. Horde_Prefs->store()
2. Horde_Core_Prefs_Cache_Session->store() /usr/share/php/Horde/Prefs.php:424
3. Horde_Session->set() /usr/share/php/Horde/Core/Prefs/Cache/Session.php:34
4. serialize() /usr/share/php/Horde/Session.php:417
5. Horde_Prefs_Scope->serialize()
6. json_encode() /usr/share/php/Horde/Prefs/Scope.php:314
7. Horde_ErrorHandler::errorHandler()

When is certificate created in ascii then everything works ok.

problematic name is "Petr ?ernĂ­k"





Saved Queries