We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #9637, comment 1

Timestamp:: Nov 15, 2012, 10:31:28 AM (12 years ago)
Author:: Jakub Ś
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9637, comment 1

initial	v1
1	1	1. As it has been many times explained in #8948 this is not security issue.
2	2	2. Possible solutions were provided in - http://dev.ckeditor.com/ticket/8948#comment:9
3		3. Writing a server code to filter the scripts will not help as it might corrupt the data.
4		I'm sorry but this is no argument. That is the whole point - to corrupt malicious data. It only depends on programmer whether he/she will write good code that will not corrupt non-malicious data
	3	3. "Writing a server code to filter the scripts will not help as it might corrupt the data." [[BR]] I'm sorry but this is no argument. That is the whole point - to corrupt malicious data. It only depends on programmer whether he/she will write good code that will not corrupt non-malicious data