On segunda-feira, 26 de agosto de 2013 13:53:38, Kurt Pattyn wrote: > So, my question is now: should we consider this as a bug, and thus file a > bug request in Jira, or can we live with it? Note that solving this issue > could have an effect an QString as well, as it needs to handle those > non-characters. Maybe, a flag could be added to QTextCodec to indicate the > handling of those characters?
We should remove the check. It was added because GLib made the mistake of forbidding them, and the mistake was imported into D-Bus, which led to remote DoS attacks in KDE applications that sent remote text via D-Bus (konversation sent the text sent by people from IRC). GLib was fixed in version 2.36 and D-Bus was fixed in 1.6.10. Since 1.6.10 is pretty new, we need to keep a version check in QtDBus. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
