home.social

#decompiler — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #decompiler, aggregated by home.social.

  1. Decomp2dbg:

    "decomp2dbg aims to shorten the gap of context switching between decompiler and debugger by introducing a generic API for decompiler-to-debugger symbol syncing."

    github.com/mahaloz/decomp2dbg

    #reverseengineering #debugger #decompiler

  2. Decomp2dbg:

    "decomp2dbg aims to shorten the gap of context switching between decompiler and debugger by introducing a generic API for decompiler-to-debugger symbol syncing."

    github.com/mahaloz/decomp2dbg

    #reverseengineering #debugger #decompiler

  3. Decomp2dbg:

    "decomp2dbg aims to shorten the gap of context switching between decompiler and debugger by introducing a generic API for decompiler-to-debugger symbol syncing."

    github.com/mahaloz/decomp2dbg

    #reverseengineering #debugger #decompiler

  4. Decomp2dbg:

    "decomp2dbg aims to shorten the gap of context switching between decompiler and debugger by introducing a generic API for decompiler-to-debugger symbol syncing."

    github.com/mahaloz/decomp2dbg

    #reverseengineering #debugger #decompiler

  5. Decomp2dbg:

    "decomp2dbg aims to shorten the gap of context switching between decompiler and debugger by introducing a generic API for decompiler-to-debugger symbol syncing."

    github.com/mahaloz/decomp2dbg

    #reverseengineering #debugger #decompiler

  6. github.com/Hexorg/Ouroboros #decompiler written in #rust can now open PE32 files and decompile them. Decompiler isn’t complete of course - expect unresolved expressions and crashes too. But basics work. Open a file, then hover over a byte And press D to disassemble from from that byte onwards. Then hover over instruction address and press F to define function start there. This will show the function in decompile view.

  7. @myfear Oh no, comes with a ? 🫨 Better uninstall it before visiting Germany, because simply having one on your computer could get you thrown in ! 🚔

    👉 heise.de/news/Bundesverfassung 🇩🇪

  8. 🤦‍♂️ Behold the #Fernflower Java #Decompiler, where #JetBrains bravely attempts to turn inscrutable #bytecode gibberish back into Java—truly the hero we neither asked for nor needed. Meanwhile, #GitHub leaps in with #AI wizardry to help developers write "better" code, because clearly, human-written code just isn't confusing enough. 🌟
    github.com/JetBrains/fernflower #CodeDevelopment #HackerNews #ngated

  9. One Open-source Project Daily

    Python decompiler for 3.7-3.8 Stripped down from uncompyle6 so we can refactor and start to fix up some long-standing problems

    https://github.com/rocky/python-decompile3

    #1ospd #opensource #bytecode #decompiler #python

  10. Aside of the awesome diagrams that Mermaid.js can generate I'd like to highlight this script that is really helpful when you want to figure out how #decompiler represents different pieces of code:

    https://github.com/v-p-b/ghidra-cheat-sheet/blob/main/scripts/dump_clang.py

    Sample output:

    https://scrapco.de/ghidra-cheat-sheet/decompiler/structure_samples/
  11. Time for another blog post!

    This time we are tackling .NET debuggers and make them display garbage data with the help of proxy objects and debugger display attributes.

    Full post: washi.dev/blog/posts/debugger-
    PoC Implementation: github.com/Washi1337/ProxyObje

    #dotnet #obfuscation #reversing #asmresolver #cil #dnspy #decompiler #debugger #poc

  12. Time for another blog post!

    This time we are tackling .NET debuggers and make them display garbage data with the help of proxy objects and debugger display attributes.

    Full post: washi.dev/blog/posts/debugger-
    PoC Implementation: github.com/Washi1337/ProxyObje

    #dotnet #obfuscation #reversing #asmresolver #cil #dnspy #decompiler #debugger #poc

  13. 🪲 Heads up, Bug Hunters 🪲 We’re still searching for vulnerabilities in IDA and the Decompiler. Help us find one, and you might earn a nice cash reward. Read more 🌐 hex-rays.com/bugbounty/?utm_so

    #HexRays #BugBounty #IDA #Decompiler #SecurityBug

  14. 🔎​🐞​ We are on the lookout for vulnerabilities in IDA and the Decompiler, and if you find one, you might earn a reward. Learn more about our Bug Bounty Program and start hunting today 🌐 hex-rays.com/bugbounty/?utm_so

    #HexRays #BugBounty #IDA #Decompiler #SecurityBug

  15. Dear everyone in the academia (and maybe elsewhere) doing #bindiffing research: #SymbolicExecution does not work for comparing different architectures, unless you are using as input for your symbolic execution tool *decompiled code*.

    If you are using assembly or using an IR (Intermediate Representation) based on assembler (like Ghidra' p-code, IDA's microcode, LLVM's IR, etc), it will inevitably produce different outputs.

    Your best IR for #diffing is pseudo-code, the #decompiler's output.

  16. Optionally, if I have enough time and it proves to be really useful: use #symbolic #execution to determine if #decompiled code corresponds to original sources code. It doesn't look trivial at all, as codes written by humans tends to be much more verbose, logical, etc, than codes generated by compilers.

    In summary: it's hard to compare, say, humans written Abstract Syntax Trees against the #AST given by an optimising #decompiler taking as input code optimised by a #compiler.

  17. We know that Rust is gaining more popularity, and we will enhance our support. We’ve reached the first milestone–string literals recovery 🎉 It is a valuable addition that can benefit many of you right away. Give it a try 🌐 hex-rays.com/blog/rust-analysi

    #idapro #decompiler #idaplugin