Summary | String contains non-ASCII characters. |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Bug |
State | Resolved |
Priority | 2. Medium |
Owners | slusarz (at) horde (dot) org |
Requester | azurit (at) pobox (dot) sk |
Created | 09/08/2014 (3950 days ago) |
Due | |
Updated | 09/17/2014 (3941 days ago) |
Assigned | 09/09/2014 (3949 days ago) |
Resolved | 09/16/2014 (3942 days ago) |
Github Issue Link | |
Github Pull Request | |
Milestone | |
Patch | No |
commit 77acd38f939d3b1642ea72d210790466320f9a48
Author: Michael M Slusarz <slusarz@horde.org>
Date: Tue Sep 16 14:36:50 2014 -0600
[mms] IMAP driver needs to explicitly search for UTF-8 text,
since we don't restrict charset input at the UI level (
Bug #13554).Conflicts:
ingo/docs/CHANGES
ingo/package.xml
ingo/docs/CHANGES | 3 +++
ingo/lib/Script/Imap.php | 5 +++++
ingo/package.xml | 3 ++-
3 files changed, 10 insertions(+), 1 deletions(-)
http://github.com/horde/horde/commit/77acd38f939d3b1642ea72d210790466320f9a48
commit ecea895075319793c034a30a625be1bc5db60a6c
Author: Michael M Slusarz <slusarz@horde.org>
Date: Tue Sep 16 13:59:50 2014 -0600
[mms] Better error handling when attempting to authenticate via
IMAP LOGIN command with non-ASCII credentials (
Bug #13554)..../Imap_Client/lib/Horde/Imap/Client/Socket.php | 16 ++++++++++++++--
framework/Imap_Client/package.xml | 2 ++
2 files changed, 16 insertions(+), 2 deletions(-)
http://github.com/horde/horde/commit/ecea895075319793c034a30a625be1bc5db60a6c
State ⇒ Resolved
This is the best thing that could have happened. IMAP driver was
completely broken for non-ASCII searches in ingo since forever, so the
recent change in Horde_Imap_Client easily/quickly identified that issue.
This still won't work as expected though. e.g. blacklisting IDN
addresses probably won't work due to the way IDN messages are
sent/stored. There's a bunch of recent RFCs involved with trying to
handle this better and, in fact, I'm working with at least one Gmail
guy right now in terms of trying to get more widespread support for
non-ASCII data at both the client and server level.
commit bbdbdc665cb631104eaab305212384880d58b829
Author: Michael M Slusarz <slusarz@horde.org>
Date: Tue Sep 16 14:36:50 2014 -0600
[mms] IMAP driver needs to explicitly search for UTF-8 text,
since we don't restrict charset input at the UI level (
Bug #13554).ingo/docs/CHANGES | 2 ++
ingo/lib/Script/Imap.php | 5 +++++
ingo/package.xml | 2 ++
3 files changed, 9 insertions(+), 0 deletions(-)
http://github.com/horde/horde/commit/bbdbdc665cb631104eaab305212384880d58b829
the email
noreply@körung.com
in the blacklist list that causes the error.
of the filtering rules - don't know if this is ascii or non-ascii
char.
information. This needs to be investigated.
#13555, can I safely assumethat everybody that has this problem is both:
- using imap filtering in ingo
- has a non-ascii character in one of their filter strings?
of the filtering rules - don't know if this is ascii or non-ascii char.
information. This needs to be investigated.
#13555, can I safely assume thateverybody that has this problem is both:
- using imap filtering in ingo
- has a non-ascii character in one of their filter strings?
explicitly points to what I said. Plus, I can reproduce this as soon
as I provide a non-ascii password.
failure. Which should be done internally in Horde_Imap_Client.
control elements disappears, this is 'useless state' which he/she
doesn't know how to correct and is usually contacting technical support
Assigned to Michael Slusarz
can you reproduce this cases too?
- folder name contain special chars
Now they brake the whole application.
We're using client side filtering (no sieve or similar). I'm not
sure if the new sanitizing process is necessary in that case. From
my view it should degrade graceful instead of just throwing an
exception and leave the application in an useless state.
information. This needs to be investigated.
I don't see how this "leaves the application in an useless state" though.
login and random password which will contain unicode chars and the
whole horde crashes. i don't think this is correct behavior of any
application.
and you are just saying there's no problem, how typical to Horde
project..
you said, and is indeed not a problem with Horde.
That doesn't mean that others may not weigh in with further reports,
like it just happened.
and you are just saying there's no problem, how typical to Horde
project..
can you reproduce this cases too?
- folder name contain special chars
- filter contain special chars
Both cases weren't problematic before this commit (At least here). Now
they brake the whole application.
We're using client side filtering (no sieve or similar). I'm not sure
if the new sanitizing process is necessary in that case. From my view
it should degrade graceful instead of just throwing an exception and
leave the application in an useless state.
explicitly points to what I said. Plus, I can reproduce this as soon
as I provide a non-ascii password.
explicitly points to what I said. Plus, I can reproduce this as soon
as I provide a non-ascii password.
report. after i delete that folder (via shell), login start to work
again.
Version ⇒ Git master
Queue ⇒ Horde Framework Packages
are using a password that contains non-ascii characters which is not
supported.
https://github.com/horde/horde/commit/10a822329f9fcaa8026de4c1e56de637554cf261
For exapmle if the Blacklist of an user contain non-ascii chars he's
not able to access webmail anymore.
2014-09-08T21:01:48+02:00 EMERG: HORDE [horde] String contains
non-ASCII characters. [pid 25718 on line 73 of
"/usr/share/php/Horde/Imap/Client/Data/Format/String.php"]
2014-09-08T21:01:48+02:00 DEBUG: HORDE 1.
Horde_Core_Auth_Application->authenticate()
/usr/share/horde/login.php:155
2. Horde_Core_Auth_Application->authenticate()
/usr/share/php/Horde/Core/Auth/Application.php:126
3. Horde_Auth_Base->authenticate()
/usr/share/php/Horde/Core/Auth/Application.php:129
4. Horde_Core_Auth_Application->_authenticate()
/usr/share/php/Horde/Auth/Base.php:160
5. Horde_Registry->callAppMethod()
/usr/share/php/Horde/Core/Auth/Application.php:158
6. call_user_func_array() /usr/share/php/Horde/Registry.php:1201
7. IMP_Application->authAuthenticate()
8. IMP_Auth::authenticate() /usr/share/horde/imp/lib/Application.php:371
9. IMP_Imap->login() /usr/share/horde/imp/lib/Auth.php:86
10. IMP_Imap->__call() /usr/share/horde/imp/lib/Auth.php:86
11. call_user_func_array() /usr/share/horde/imp/lib/Imap.php:718
12. Horde_Imap_Client_Base->login()
13. Horde_Imap_Client_Socket->_login()
/usr/share/php/Horde/Imap/Client/Base.php:794
14. Horde_Imap_Client_Socket->_tryLogin()
/usr/share/php/Horde/Imap/Client/Socket.php:497
15. Horde_Imap_Client_Data_Format_String->__construct()
/usr/share/php/Horde/Imap/Client/Socket.php:730
2014-09-04T18:13:37+02:00 EMERG: HORDE [imp] String contains non-ASCII
characters. [pid 25850 on line 73 of
"/usr/share/php/Horde/Imap/Client/Data/Format/String.php"]
do you need something more?
State ⇒ Feedback
Priority ⇒ 2. Medium
Priority ⇒ 3. High
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Summary ⇒ String contains non-ASCII characters.
Type ⇒ Bug
Queue ⇒ IMP
String contains non-ASCII characters.
How to reproduce:
1.) Login into account.
2.) Create folder 'Odoslaná po?ta' (without quotes)
3.) Logout and try to login again.