| Both sides previous revision
Previous revision
Next revision
|
Previous revision
|
examples:example4 [2009/10/26 19:10]
aspectscript |
examples:example4 [2009/11/06 20:49] (current)
aspectscript |
| <link href="/aspectscript/external/aspectscript/paperExamples/style.css" rel="stylesheet" type="text/css"/> | <link href="/aspectscript/external/aspectscript/paperExamples/style.css" rel="stylesheet" type="text/css"/> |
| <script type="text/javascript" language="javascript" src="/aspectscript/external/aspectscript/paperExamples/lib.js"> </script> | <script type="text/javascript" language="javascript" src="/aspectscript/external/aspectscript/paperExamples/lib.js"> </script> |
| <iframe id="example1" src="/aspectscript/external/aspectscript/paperExamples/example2-1" width="810" height="470"></iframe> | <iframe id="example1" src="/aspectscript/external/aspectscript/paperExamples/example4-1" width="815" height="370"></iframe> |
| <iframe id="code1" style="display:none" src="/aspectscript/external/aspectscript/paperExamples/example2-1/script.js" width="810" height="470"></iframe> | <iframe id="code1" style="display:none" src="/aspectscript/external/aspectscript/paperExamples/example4-1/script.js" width="815" height="370"></iframe> |
| <a id="button" class="button" onclick="toggle('code1','example1')"> <span>See the code or example </span></a> | <a id="button" class="button" onclick="toggle('code1','example1')"> <span>Toggle between the code and example </span></a> |
| </html> | |
| </html> | </html> |
| |
| However, if the malicious application changes to: | \\ However, if the malicious application changes to: |
| |
| <code java> | <code java> |
| It is not possible to identify the malicious action of the application anymore, because the access to the home link is indirect. A solution to this problem is deploy the aspect with a more expressive scoping definition by means of a scoping strategy. | It is not possible to identify the malicious action of the application anymore, because the access to the home link is indirect. A solution to this problem is deploy the aspect with a more expressive scoping definition by means of a scoping strategy. |
| |
| The implementation follows: | The following window uses scoping strategies to avoid the indirect access to home link of the malicious application: |
| |
| <html> | <html> |
| <iframe src="/aspectscript/external/aspectscript/paperExamples/example4-2" width="815" height="370"></iframe> | <iframe id="example2" src="/aspectscript/external/aspectscript/paperExamples/example4-2" width="815" height="370"></iframe> |
| | <iframe id="code2" style="display:none" src="/aspectscript/external/aspectscript/paperExamples/example4-2/script.js" width="815" height="370"></iframe> |
| | <a id="button" class="button" onclick="toggle('code2','example2')"> <span>Toggle between the code and example </span></a> |
| </html> | </html> |
| |