11 | 11 |
Architecture: all
|
12 | 12 |
Depends: ${misc:Depends}, default-jdk
|
13 | 13 |
Description: Intercept Java applications locally
|
14 | |
Normally, without access to the original source code,
|
15 | |
testing the security of a Java client is unpredictable at
|
16 | |
best and unrealistic at worst. With access the original
|
17 | |
source, you can run a simple Java program and attach a
|
18 | |
debugger to it remotely, stepping through code and changing
|
19 | |
variables where needed. Doing the same with an applet is a
|
20 | |
little bit more difficult.
|
21 | |
JavaSnoop attempts to solve this problem by allowing you
|
22 | |
attach to an existing process (like a debugger) and
|
23 | |
instantly begin tampering with method calls, run custom
|
24 | |
code, or just watch what's happening on the system.
|
|
14 |
Normally, without access to the original source code,
|
|
15 |
testing the security of a Java client is unpredictable at
|
|
16 |
best and unrealistic at worst. With access the original
|
|
17 |
source, you can run a simple Java program and attach a
|
|
18 |
debugger to it remotely, stepping through code and changing
|
|
19 |
variables where needed. Doing the same with an applet is a
|
|
20 |
little bit more difficult.
|
|
21 |
JavaSnoop attempts to solve this problem by allowing you
|
|
22 |
attach to an existing process (like a debugger) and
|
|
23 |
instantly begin tampering with method calls, run custom
|
|
24 |
code, or just watch what's happening on the system.
|