From: Van de B. <van...@gm...> - 2011-07-24 22:58:38
|
Yaron and all, I am not sure this as a "new" bug, but searching WikiMedia bugzilla for keywords "Semantic Forms" did not show such a problem. Usually Semantic Forms are used in cooperation with templates. Definition of a form requires template name: {{{for template|template-name}}} {{{field|Param1|...}}} ... Values entered into input fields are passed to template as parameters. But there are some special symbols, e. g. |, {, } (may be some more), which can easily break the generated code. If user enter value "aaa|bbb" to filed Param1, following code is saved as page content: {{template-name |Param1=aaa|bbb ... }} It is obvious that "bbb" is not a part of "Param1" parameter value but another parameter with name "bbb" and empty value. Value "aaa}} bbb" will also have disaster effect. By default MediaWiki declares characters #<>[]|{} are illegal for page titles (see http://www.mediawiki.org/wiki/Manual:$wgLegalTitleChars). If input field declaration specifies a property, and property type is "Page", Semantic Forms should validate user input and reject input which is not suitable for a page name. At least input should contain only characters declared as valid ones. For strings allowed input is not required to be a valid page name, but in any case, result must be valid template invocation, so some characters should be rejected or properly escaped/encoded. Since existing templates does not expect escaped/encoded characters, the simplest approach would be rejecting input containing invalid characters. I know that any user can edit page source directly and broke it. However, when user edits source code, it is assumed s/he knows basics and responsible for result. With form situation is opposite. It is not supposed users know what is template, which characters are allowed and which are not and how correct source looks like. It is a form responsibility to validate input and generate valid page source. Van. |
From: badon <fas...@gm...> - 2011-07-24 23:27:41
|
I added this bug to bugzilla: https://bugzilla.wikimedia.org/show_bug.cgi?id=30042 Van de Bugger wrote: > > Yaron and all, > > I am not sure this as a "new" bug, but searching WikiMedia bugzilla for > keywords "Semantic Forms" did not show such a problem. > > Usually Semantic Forms are used in cooperation with templates. > Definition of a form requires template name: > > {{{for template|template-name}}} > {{{field|Param1|...}}} > ... > > Values entered into input fields are passed to template as parameters. > But there are some special symbols, e. g. |, {, } (may be some more), > which can easily break the generated code. If user enter value "aaa|bbb" > to filed Param1, following code is saved as page content: > > {{template-name > |Param1=aaa|bbb > ... > }} > > It is obvious that "bbb" is not a part of "Param1" parameter value but > another parameter with name "bbb" and empty value. Value "aaa}} bbb" > will also have disaster effect. > > By default MediaWiki declares characters #<>[]|{} are illegal for page > titles (see http://www.mediawiki.org/wiki/Manual:$wgLegalTitleChars). If > input field declaration specifies a property, and property type is > "Page", Semantic Forms should validate user input and reject input which > is not suitable for a page name. At least input should contain only > characters declared as valid ones. > > For strings allowed input is not required to be a valid page name, but > in any case, result must be valid template invocation, so some > characters should be rejected or properly escaped/encoded. Since > existing templates does not expect escaped/encoded characters, the > simplest approach would be rejecting input containing invalid > characters. > > I know that any user can edit page source directly and broke it. > However, when user edits source code, it is assumed s/he knows basics > and responsible for result. With form situation is opposite. It is not > supposed users know what is template, which characters are allowed and > which are not and how correct source looks like. It is a form > responsibility to validate input and generate valid page source. > > Van. > > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > -- View this message in context: http://old.nabble.com/Semantic-Forms%3A-Need-better-input-checking.-tp32128157p32128246.html Sent from the Semantic Mediawiki - User mailing list archive at Nabble.com. |
From: Yaron K. <ya...@wi...> - 2011-07-25 19:40:47
|
Hi, Indeed, I've known about the problem with pipes in form inputs for a long time, but I never thought to do Javascript validation on it - that's a very good idea. For creating page titles, I think that's a much smaller problem - forms already display an error message if you try to create a title with invalid characters, so this would just be Javascript validation in addition to the existing PHP validation; which barely seems worth it. So if I'm not mistaken, I think pipes in form inputs are the only real issue; I made a comment in the Bugzilla page to that effect. -Yaron On Sun, Jul 24, 2011 at 7:27 PM, badon <fas...@gm...> wrote: > > I added this bug to bugzilla: > > https://bugzilla.wikimedia.org/show_bug.cgi?id=30042 > > > > Van de Bugger wrote: > > > > Yaron and all, > > > > I am not sure this as a "new" bug, but searching WikiMedia bugzilla for > > keywords "Semantic Forms" did not show such a problem. > > > > Usually Semantic Forms are used in cooperation with templates. > > Definition of a form requires template name: > > > > {{{for template|template-name}}} > > {{{field|Param1|...}}} > > ... > > > > Values entered into input fields are passed to template as parameters. > > But there are some special symbols, e. g. |, {, } (may be some more), > > which can easily break the generated code. If user enter value "aaa|bbb" > > to filed Param1, following code is saved as page content: > > > > {{template-name > > |Param1=aaa|bbb > > ... > > }} > > > > It is obvious that "bbb" is not a part of "Param1" parameter value but > > another parameter with name "bbb" and empty value. Value "aaa}} bbb" > > will also have disaster effect. > > > > By default MediaWiki declares characters #<>[]|{} are illegal for page > > titles (see http://www.mediawiki.org/wiki/Manual:$wgLegalTitleChars). If > > input field declaration specifies a property, and property type is > > "Page", Semantic Forms should validate user input and reject input which > > is not suitable for a page name. At least input should contain only > > characters declared as valid ones. > > > > For strings allowed input is not required to be a valid page name, but > > in any case, result must be valid template invocation, so some > > characters should be rejected or properly escaped/encoded. Since > > existing templates does not expect escaped/encoded characters, the > > simplest approach would be rejecting input containing invalid > > characters. > > > > I know that any user can edit page source directly and broke it. > > However, when user edits source code, it is assumed s/he knows basics > > and responsible for result. With form situation is opposite. It is not > > supposed users know what is template, which characters are allowed and > > which are not and how correct source looks like. It is a form > > responsibility to validate input and generate valid page source. > > > > Van. > > > > > > > ------------------------------------------------------------------------------ > > Magic Quadrant for Content-Aware Data Loss Prevention > > Research study explores the data loss prevention market. Includes > in-depth > > analysis on the changes within the DLP market, and the criteria used to > > evaluate the strengths and weaknesses of these DLP solutions. > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > -- > View this message in context: > http://old.nabble.com/Semantic-Forms%3A-Need-better-input-checking.-tp32128157p32128246.html > Sent from the Semantic Mediawiki - User mailing list archive at Nabble.com. > > > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > Semediawiki-user mailing list > Sem...@li... > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Van de B. <van...@gm...> - 2011-07-26 21:40:40
|
On Mon, 2011-07-25 at 15:40 -0400, Yaron Koren wrote: > Hi, > > Indeed, I've known about the problem with pipes in form inputs for a long > time, but I never thought to do Javascript validation on it - that's a very > good idea. > > For creating page titles, I think that's a much smaller problem - forms > already display an error message if you try to create a title with invalid > characters, so this would just be Javascript validation in addition to the > existing PHP validation; which barely seems worth it. I am not about creating titles, I am about entering titles. An example from my site: {{{field | Home region | property = Home region | input type = text with autocomplete | values from namespace = Region: | existing values only | remote autocompletion }}} It seems "existing values only" affects only "combobox" inputs, and has no effect for "text with autocomplete". I expect: (1) users will be able to enter name of existing page from namespace "Region"; (2) in case of non-existing page user will see an error message, (3) in case of entering invalid characters ({, |, }, ...). users will see an error message. Autocompletion works, but input is not validated. I can enter any string into this field: a name of non-existing page, or even incorrect name at all (e. g. string with bar or braces). The first kind of mistakes is acceptable, because I can handle in it a template and notify user with {{ #info: ... | warning }} (a bit late to my taste -- I would like to notify user before saving, not after), but the second kind of mistakes cannot be handled in template. > So if I'm not mistaken, I think pipes in form inputs are the only real > issue; I made a comment in the Bugzilla page to that effect. Not only pipes, braces also. For example, double closing braces will definitely break generated code, double opening braces may have undesired effect as well, . This, braces and bar should be rejected in input fields of any type. Van. > > -Yaron > > On Sun, Jul 24, 2011 at 7:27 PM, badon <fas...@gm...> wrote: > > > > > I added this bug to bugzilla: > > > > https://bugzilla.wikimedia.org/show_bug.cgi?id=30042 > > > > > > > > Van de Bugger wrote: > > > > > > Yaron and all, > > > > > > I am not sure this as a "new" bug, but searching WikiMedia bugzilla for > > > keywords "Semantic Forms" did not show such a problem. > > > > > > Usually Semantic Forms are used in cooperation with templates. > > > Definition of a form requires template name: > > > > > > {{{for template|template-name}}} > > > {{{field|Param1|...}}} > > > ... > > > > > > Values entered into input fields are passed to template as parameters. > > > But there are some special symbols, e. g. |, {, } (may be some more), > > > which can easily break the generated code. If user enter value "aaa|bbb" > > > to filed Param1, following code is saved as page content: > > > > > > {{template-name > > > |Param1=aaa|bbb > > > ... > > > }} > > > > > > It is obvious that "bbb" is not a part of "Param1" parameter value but > > > another parameter with name "bbb" and empty value. Value "aaa}} bbb" > > > will also have disaster effect. > > > > > > By default MediaWiki declares characters #<>[]|{} are illegal for page > > > titles (see http://www.mediawiki.org/wiki/Manual:$wgLegalTitleChars). If > > > input field declaration specifies a property, and property type is > > > "Page", Semantic Forms should validate user input and reject input which > > > is not suitable for a page name. At least input should contain only > > > characters declared as valid ones. > > > > > > For strings allowed input is not required to be a valid page name, but > > > in any case, result must be valid template invocation, so some > > > characters should be rejected or properly escaped/encoded. Since > > > existing templates does not expect escaped/encoded characters, the > > > simplest approach would be rejecting input containing invalid > > > characters. > > > > > > I know that any user can edit page source directly and broke it. > > > However, when user edits source code, it is assumed s/he knows basics > > > and responsible for result. With form situation is opposite. It is not > > > supposed users know what is template, which characters are allowed and > > > which are not and how correct source looks like. It is a form > > > responsibility to validate input and generate valid page source. > > > > > > Van. > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Magic Quadrant for Content-Aware Data Loss Prevention > > > Research study explores the data loss prevention market. Includes > > in-depth > > > analysis on the changes within the DLP market, and the criteria used to > > > evaluate the strengths and weaknesses of these DLP solutions. > > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > > _______________________________________________ > > > Semediawiki-user mailing list > > > Sem...@li... > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > -- > > View this message in context: > > http://old.nabble.com/Semantic-Forms%3A-Need-better-input-checking.-tp32128157p32128246.html > > Sent from the Semantic Mediawiki - User mailing list archive at Nabble.com. > > > > > > > > ------------------------------------------------------------------------------ > > Magic Quadrant for Content-Aware Data Loss Prevention > > Research study explores the data loss prevention market. Includes in-depth > > analysis on the changes within the DLP market, and the criteria used to > > evaluate the strengths and weaknesses of these DLP solutions. > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > _______________________________________________ > > Semediawiki-user mailing list > > Sem...@li... > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > |
From: Yaron K. <ya...@wi...> - 2011-07-26 23:07:42
|
Hi, Ah - now I understand: you want validation for "Page" properties. That's a good idea, and it would fit in with the existing validation for properties of type Number, URL and Email. As to the pipes thing - that's actually quite a bit trickier than I first thought; there's a discussion about it on the Bugzilla bug report. Pipes are actually alright if they're within double curly brackets; and so are brackets, as long as they're not mismatched. So basically there would have to be Javascript parsing to match MediaWiki's own parsing, which could be rather difficult. -Yaron On Tue, Jul 26, 2011 at 5:40 PM, Van de Bugger <van...@gm...>wrote: > > > On Mon, 2011-07-25 at 15:40 -0400, Yaron Koren wrote: > > Hi, > > > > Indeed, I've known about the problem with pipes in form inputs for a long > > time, but I never thought to do Javascript validation on it - that's a > very > > good idea. > > > > For creating page titles, I think that's a much smaller problem - forms > > already display an error message if you try to create a title with > invalid > > characters, so this would just be Javascript validation in addition to > the > > existing PHP validation; which barely seems worth it. > > I am not about creating titles, I am about entering titles. An example > from my site: > > {{{field > | Home region > | property = Home region > | input type = text with autocomplete > | values from namespace = Region: > | existing values only > | remote autocompletion > }}} > > It seems "existing values only" affects only "combobox" inputs, and has > no effect for "text with autocomplete". I expect: (1) users will be able > to enter name of existing page from namespace "Region"; (2) in case of > non-existing page user will see an error message, (3) in case of > entering invalid characters ({, |, }, ...). users will see an error > message. Autocompletion works, but input is not validated. I can enter > any string into this field: a name of non-existing page, or even > incorrect name at all (e. g. string with bar or braces). The first kind > of mistakes is acceptable, because I can handle in it a template and > notify user with {{ #info: ... | warning }} (a bit late to my taste -- I > would like to notify user before saving, not after), but the second kind > of mistakes cannot be handled in template. > > > So if I'm not mistaken, I think pipes in form inputs are the only real > > issue; I made a comment in the Bugzilla page to that effect. > > Not only pipes, braces also. For example, double closing braces will > definitely break generated code, double opening braces may have > undesired effect as well, . This, braces and bar should be rejected in > input fields of any type. > > Van. > > > > > -Yaron > > > > On Sun, Jul 24, 2011 at 7:27 PM, badon <fas...@gm...> wrote: > > > > > > > > I added this bug to bugzilla: > > > > > > https://bugzilla.wikimedia.org/show_bug.cgi?id=30042 > > > > > > > > > > > > Van de Bugger wrote: > > > > > > > > Yaron and all, > > > > > > > > I am not sure this as a "new" bug, but searching WikiMedia bugzilla > for > > > > keywords "Semantic Forms" did not show such a problem. > > > > > > > > Usually Semantic Forms are used in cooperation with templates. > > > > Definition of a form requires template name: > > > > > > > > {{{for template|template-name}}} > > > > {{{field|Param1|...}}} > > > > ... > > > > > > > > Values entered into input fields are passed to template as > parameters. > > > > But there are some special symbols, e. g. |, {, } (may be some more), > > > > which can easily break the generated code. If user enter value > "aaa|bbb" > > > > to filed Param1, following code is saved as page content: > > > > > > > > {{template-name > > > > |Param1=aaa|bbb > > > > ... > > > > }} > > > > > > > > It is obvious that "bbb" is not a part of "Param1" parameter value > but > > > > another parameter with name "bbb" and empty value. Value "aaa}} bbb" > > > > will also have disaster effect. > > > > > > > > By default MediaWiki declares characters #<>[]|{} are illegal for > page > > > > titles (see http://www.mediawiki.org/wiki/Manual:$wgLegalTitleChars). > If > > > > input field declaration specifies a property, and property type is > > > > "Page", Semantic Forms should validate user input and reject input > which > > > > is not suitable for a page name. At least input should contain only > > > > characters declared as valid ones. > > > > > > > > For strings allowed input is not required to be a valid page name, > but > > > > in any case, result must be valid template invocation, so some > > > > characters should be rejected or properly escaped/encoded. Since > > > > existing templates does not expect escaped/encoded characters, the > > > > simplest approach would be rejecting input containing invalid > > > > characters. > > > > > > > > I know that any user can edit page source directly and broke it. > > > > However, when user edits source code, it is assumed s/he knows basics > > > > and responsible for result. With form situation is opposite. It is > not > > > > supposed users know what is template, which characters are allowed > and > > > > which are not and how correct source looks like. It is a form > > > > responsibility to validate input and generate valid page source. > > > > > > > > Van. > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > Magic Quadrant for Content-Aware Data Loss Prevention > > > > Research study explores the data loss prevention market. Includes > > > in-depth > > > > analysis on the changes within the DLP market, and the criteria used > to > > > > evaluate the strengths and weaknesses of these DLP solutions. > > > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > > > _______________________________________________ > > > > Semediawiki-user mailing list > > > > Sem...@li... > > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > > > > > -- > > > View this message in context: > > > > http://old.nabble.com/Semantic-Forms%3A-Need-better-input-checking.-tp32128157p32128246.html > > > Sent from the Semantic Mediawiki - User mailing list archive at > Nabble.com. > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Magic Quadrant for Content-Aware Data Loss Prevention > > > Research study explores the data loss prevention market. Includes > in-depth > > > analysis on the changes within the DLP market, and the criteria used to > > > evaluate the strengths and weaknesses of these DLP solutions. > > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > > _______________________________________________ > > > Semediawiki-user mailing list > > > Sem...@li... > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > > > -- WikiWorks · MediaWiki Consulting · http://wikiworks.com |
From: Van de B. <van...@gm...> - 2011-09-27 08:18:35
|
Hi Yaron, I am back. Please consider a simple patch for Semantic Forms. It adds validation for input fields: "{", "|", and "}" are rejected because they will likely lead to incorrect template call. I know that curly braces and bars can be used for calling parser functions and templates, but I think in such a case it is much easier to edit wiki code directly without forms. At the same time, a form must produce correct template call, so making "{", "|", and "}" the prohibited characters is the right thing to do. Van. On Tue, 2011-07-26 at 19:07 -0400, Yaron Koren wrote: > Hi, > > Ah - now I understand: you want validation for "Page" properties. > That's a good idea, and it would fit in with the existing validation > for properties of type Number, URL and Email. > > As to the pipes thing - that's actually quite a bit trickier than I > first thought; there's a discussion about it on the Bugzilla bug > report. Pipes are actually alright if they're within double curly > brackets; and so are brackets, as long as they're not mismatched. So > basically there would have to be Javascript parsing to match > MediaWiki's own parsing, which could be rather difficult. > > -Yaron > > On Tue, Jul 26, 2011 at 5:40 PM, Van de Bugger > <van...@gm...> wrote: > > > On Mon, 2011-07-25 at 15:40 -0400, Yaron Koren wrote: > > Hi, > > > > Indeed, I've known about the problem with pipes in form > inputs for a long > > time, but I never thought to do Javascript validation on it > - that's a very > > good idea. > > > > For creating page titles, I think that's a much smaller > problem - forms > > already display an error message if you try to create a > title with invalid > > characters, so this would just be Javascript validation in > addition to the > > existing PHP validation; which barely seems worth it. > > > I am not about creating titles, I am about entering titles. An > example > from my site: > > {{{field > | Home region > | property = Home region > | input type = text with autocomplete > | values from namespace = Region: > | existing values only > | remote autocompletion > }}} > > It seems "existing values only" affects only "combobox" > inputs, and has > no effect for "text with autocomplete". I expect: (1) users > will be able > to enter name of existing page from namespace "Region"; (2) in > case of > non-existing page user will see an error message, (3) in case > of > entering invalid characters ({, |, }, ...). users will see an > error > message. Autocompletion works, but input is not validated. I > can enter > any string into this field: a name of non-existing page, or > even > incorrect name at all (e. g. string with bar or braces). The > first kind > of mistakes is acceptable, because I can handle in it a > template and > notify user with {{ #info: ... | warning }} (a bit late to my > taste -- I > would like to notify user before saving, not after), but the > second kind > of mistakes cannot be handled in template. > > > So if I'm not mistaken, I think pipes in form inputs are the > only real > > issue; I made a comment in the Bugzilla page to that effect. > > > Not only pipes, braces also. For example, double closing > braces will > definitely break generated code, double opening braces may > have > undesired effect as well, . This, braces and bar should be > rejected in > input fields of any type. > > Van. > > > > > > -Yaron > > > > On Sun, Jul 24, 2011 at 7:27 PM, badon > <fas...@gm...> wrote: > > > > > > > > I added this bug to bugzilla: > > > > > > https://bugzilla.wikimedia.org/show_bug.cgi?id=30042 > > > > > > > > > > > > Van de Bugger wrote: > > > > > > > > Yaron and all, > > > > > > > > I am not sure this as a "new" bug, but searching > WikiMedia bugzilla for > > > > keywords "Semantic Forms" did not show such a problem. > > > > > > > > Usually Semantic Forms are used in cooperation with > templates. > > > > Definition of a form requires template name: > > > > > > > > {{{for template|template-name}}} > > > > {{{field|Param1|...}}} > > > > ... > > > > > > > > Values entered into input fields are passed to template > as parameters. > > > > But there are some special symbols, e. g. |, {, } (may > be some more), > > > > which can easily break the generated code. If user enter > value "aaa|bbb" > > > > to filed Param1, following code is saved as page > content: > > > > > > > > {{template-name > > > > |Param1=aaa|bbb > > > > ... > > > > }} > > > > > > > > It is obvious that "bbb" is not a part of "Param1" > parameter value but > > > > another parameter with name "bbb" and empty value. Value > "aaa}} bbb" > > > > will also have disaster effect. > > > > > > > > By default MediaWiki declares characters #<>[]|{} are > illegal for page > > > > titles (see http://www.mediawiki.org/wiki/Manual: > $wgLegalTitleChars). If > > > > input field declaration specifies a property, and > property type is > > > > "Page", Semantic Forms should validate user input and > reject input which > > > > is not suitable for a page name. At least input should > contain only > > > > characters declared as valid ones. > > > > > > > > For strings allowed input is not required to be a valid > page name, but > > > > in any case, result must be valid template invocation, > so some > > > > characters should be rejected or properly > escaped/encoded. Since > > > > existing templates does not expect escaped/encoded > characters, the > > > > simplest approach would be rejecting input containing > invalid > > > > characters. > > > > > > > > I know that any user can edit page source directly and > broke it. > > > > However, when user edits source code, it is assumed s/he > knows basics > > > > and responsible for result. With form situation is > opposite. It is not > > > > supposed users know what is template, which characters > are allowed and > > > > which are not and how correct source looks like. It is a > form > > > > responsibility to validate input and generate valid page > source. > > > > > > > > Van. > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > Magic Quadrant for Content-Aware Data Loss Prevention > > > > Research study explores the data loss prevention market. > Includes > > > in-depth > > > > analysis on the changes within the DLP market, and the > criteria used to > > > > evaluate the strengths and weaknesses of these DLP > solutions. > > > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > > > _______________________________________________ > > > > Semediawiki-user mailing list > > > > Sem...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > > > > > -- > > > View this message in context: > > > http://old.nabble.com/Semantic-Forms% > 3A-Need-better-input-checking.-tp32128157p32128246.html > > > Sent from the Semantic Mediawiki - User mailing list > archive at Nabble.com. > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Magic Quadrant for Content-Aware Data Loss Prevention > > > Research study explores the data loss prevention market. > Includes in-depth > > > analysis on the changes within the DLP market, and the > criteria used to > > > evaluate the strengths and weaknesses of these DLP > solutions. > > > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > > > _______________________________________________ > > > Semediawiki-user mailing list > > > Sem...@li... > > > > https://lists.sourceforge.net/lists/listinfo/semediawiki-user > > > > > > > > > > > > > > > > -- > WikiWorks · MediaWiki Consulting · http://wikiworks.com |