scayt security in CKEDitor
I work on a WYSIWYG plugin for DokuWiki that uses the CKEditor. It's been in use since FCKeditor days, and no one has ever raised any security before. But a user recently raised the question as to whether the Scayt spell checker was a security risk because of how it is implemented, i.e. passing textin parameters from the wiki to the Scayt servers in order to check spelling. On a public wiki this would not matter. But when a wiki is closed, internal to a company or on a personal LAN, does this potentially open up the closed wiki to a third party? I would appreciate any information or views.
For the complete exchange of views on this topic see: https://github.com/turnermm/ckgedit/issues/434
ckeditor scayt
asked Nov 11 at 23:20
turnermm
64
add a comment |
I work on a WYSIWYG plugin for DokuWiki that uses the CKEditor. It's been in use since FCKeditor days, and no one has ever raised any security before. But a user recently raised the question as to whether the Scayt spell checker was a security risk because of how it is implemented, i.e. passing textin parameters from the wiki to the Scayt servers in order to check spelling. On a public wiki this would not matter. But when a wiki is closed, internal to a company or on a personal LAN, does this potentially open up the closed wiki to a third party? I would appreciate any information or views.
For the complete exchange of views on this topic see: https://github.com/turnermm/ckgedit/issues/434
ckeditor scayt
asked Nov 11 at 23:20
turnermm
64
I have replied in github.com/turnermm/ckgedit/issues/434 directly. Basically it is safe but if someone doesn't like the idea of his data being sent to remote services, he can use SCAYT on his dedicated server. It should be possible to switch licenses provided that DokuWiki plugins allows its users to modify editor instance freely (this is where SCAYT configuration can be set).
– j.swiderski
Nov 13 at 15:14
add a comment |
I work on a WYSIWYG plugin for DokuWiki that uses the CKEditor. It's been in use since FCKeditor days, and no one has ever raised any security before. But a user recently raised the question as to whether the Scayt spell checker was a security risk because of how it is implemented, i.e. passing textin parameters from the wiki to the Scayt servers in order to check spelling. On a public wiki this would not matter. But when a wiki is closed, internal to a company or on a personal LAN, does this potentially open up the closed wiki to a third party? I would appreciate any information or views.
For the complete exchange of views on this topic see: https://github.com/turnermm/ckgedit/issues/434
ckeditor scayt
asked Nov 11 at 23:20
turnermm
64
I work on a WYSIWYG plugin for DokuWiki that uses the CKEditor. It's been in use since FCKeditor days, and no one has ever raised any security before. But a user recently raised the question as to whether the Scayt spell checker was a security risk because of how it is implemented, i.e. passing textin parameters from the wiki to the Scayt servers in order to check spelling. On a public wiki this would not matter. But when a wiki is closed, internal to a company or on a personal LAN, does this potentially open up the closed wiki to a third party? I would appreciate any information or views.
For the complete exchange of views on this topic see: https://github.com/turnermm/ckgedit/issues/434
ckeditor scayt
ckeditor scayt
asked Nov 11 at 23:20
turnermm
64
asked Nov 11 at 23:20
turnermm
64
asked Nov 11 at 23:20
turnermm
64
asked Nov 11 at 23:20
turnermm
64
asked Nov 11 at 23:20
turnermm
64
64
I have replied in github.com/turnermm/ckgedit/issues/434 directly. Basically it is safe but if someone doesn't like the idea of his data being sent to remote services, he can use SCAYT on his dedicated server. It should be possible to switch licenses provided that DokuWiki plugins allows its users to modify editor instance freely (this is where SCAYT configuration can be set).
– j.swiderski
Nov 13 at 15:14
add a comment |
I have replied in github.com/turnermm/ckgedit/issues/434 directly. Basically it is safe but if someone doesn't like the idea of his data being sent to remote services, he can use SCAYT on his dedicated server. It should be possible to switch licenses provided that DokuWiki plugins allows its users to modify editor instance freely (this is where SCAYT configuration can be set).
– j.swiderski
Nov 13 at 15:14
I have replied in github.com/turnermm/ckgedit/issues/434 directly. Basically it is safe but if someone doesn't like the idea of his data being sent to remote services, he can use SCAYT on his dedicated server. It should be possible to switch licenses provided that DokuWiki plugins allows its users to modify editor instance freely (this is where SCAYT configuration can be set).
– j.swiderski
Nov 13 at 15:14
I have replied in github.com/turnermm/ckgedit/issues/434 directly. Basically it is safe but if someone doesn't like the idea of his data being sent to remote services, he can use SCAYT on his dedicated server. It should be possible to switch licenses provided that DokuWiki plugins allows its users to modify editor instance freely (this is where SCAYT configuration can be set).
– j.swiderski
Nov 13 at 15:14
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254237%2fscayt-security-in-ckeditor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254237%2fscayt-security-in-ckeditor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I have replied in github.com/turnermm/ckgedit/issues/434 directly. Basically it is safe but if someone doesn't like the idea of his data being sent to remote services, he can use SCAYT on his dedicated server. It should be possible to switch licenses provided that DokuWiki plugins allows its users to modify editor instance freely (this is where SCAYT configuration can be set).
– j.swiderski
Nov 13 at 15:14