Explore >> Select a destination
|
You are here 
|
alexn.org | ||
| | | | |
blog.deesee.xyz
|
|
| | | | | When reverse engineering an application that is shipped as compiled bytecode (jar file, war file, class files, etc.), we normally use a decompiler and then audit the resulting Java code. The catch is that the language the application was written in might not have been Java! Indeed, there are multiple languages that target the Java Virtual Machine (JVM) and produce bytecode just like Java does. On top of generating generally strange decompiled code, this has for effect that the common potentially dangerou... | |
| | | | |
darkcoding.net
|
|
| | | | | Solvitas perambulum | |
| | | | |
www.codeandunicorns.com
|
|
| | | | | The following example will go over following Github repo created specifically for this. **Github:** https://github.com/mitola/selftomator It was primarily aimed to provide a bit of exploration space since I was looking at several ways to automate a couple of my workflows, so I explored through Java, Node. | |
| | | | |
vannevel.net
|
|
| | | With the release of Visual Studio 2015 RC, we also received the pretty much final implementation of the Diagnostics implementation. This SDK allows us to create our own diagnostics to help us write proper code that's being verified against those rules in real-time: you don't have to perform the verification at a separate build-step. What's more is that we can combine that with a code fix: a shortcut integrated in Visual Studio that provides us a solution to what we determine to be a problem. | ||
