socel.net is one of the many independent Mastodon servers you can use to participate in the fediverse.
Socel is a place for animation professionals, freelancers, independents, students, and fans to connect and grow together. Everyone in related fields are also welcome.

Server stats:

320
active users

#ghidra

0 posts0 participants0 posts today
Jack C.<p>Another detour on the Time Machine <a href="https://indieweb.social/tags/Pinball" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pinball</span></a> <a href="https://indieweb.social/tags/disassembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>disassembly</span></a> project, I think the processor specification I've been using is incomplete. There are a lot of instances of indexed addressing being interpreted as an offset from the current address. This is making it hard to figure out where in RAM different pieces of data live without manually calculating the address.</p><p>Time to learn <a href="https://indieweb.social/tags/Sleigh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Sleigh</span></a> and patch the processor definition. Maybe the extension author will even accept a pull request.</p><p><a href="https://indieweb.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> <a href="https://indieweb.social/tags/MC6800" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MC6800</span></a></p>
Jack C.<p>Cool. After my productivity speedbump of last night, my Time Machine <a href="https://indieweb.social/tags/pinball" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pinball</span></a> <a href="https://indieweb.social/tags/disassembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>disassembly</span></a> project has moved forward. I now have a python script which exports the <a href="https://indieweb.social/tags/ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ghidra</span></a> program into an info file which a real 6800 disassembler reads to produce assembly which should actually be able to be reassembled into a final binary.</p><p>I'll use ghidra to continue analyzing the code, and when I'm ready to actually start writing my own patches, I'll do that outside of ghidra as though it were a source file.</p>
Jack C.<p>Perusing the <a href="https://indieweb.social/tags/documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documentation</span></a> for JPype as it's the translation layer letting me write my <a href="https://indieweb.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> script in <a href="https://indieweb.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Python</span></a>, and I'm enjoying the conversational style of the introduction in the user guide </p><p><a href="https://jpype.readthedocs.io/en/latest/userguide.html#case-1-access-to-a-java-library" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jpype.readthedocs.io/en/latest</span><span class="invisible">/userguide.html#case-1-access-to-a-java-library</span></a></p><p><a href="https://indieweb.social/tags/ReverseEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReverseEngineering</span></a> <a href="https://indieweb.social/tags/Disassembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Disassembly</span></a> <a href="https://indieweb.social/tags/Motorola68xx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Motorola68xx</span></a></p>
Washi<p>After <a href="https://infosec.exchange/tags/flareon11" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>flareon11</span></a> challenge 7, I got inspired to build tooling for <a href="https://infosec.exchange/tags/dotnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dotnet</span></a> Native AOT reverse engineering.</p><p>As such, I built a <a href="https://infosec.exchange/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> Analyzer that can automatically recover most .NET types, methods and frozen objects (e.g., strings).</p><p>👉<a href="https://blog.washi.dev/posts/recovering-nativeaot-metadata/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.washi.dev/posts/recoverin</span><span class="invisible">g-nativeaot-metadata/</span></a></p>
Jack C.<p>Working on getting my toolchain put together of <a href="https://indieweb.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> -&gt; f9dasm disassembler -&gt; AS macro assembler -&gt; EPROM programmer software (??) is taking a lot of work on the frontend. </p><p>The goal is to keep working on exploring the code with Ghidra, then re-disassembling with the labels and comments with a dedicated 6800 disassembler, editing the assembly source and reassembling. I'll also have to write a little code to generate values to adjust the ROM checksum. </p><p>Just a lot of work 😝</p>
Jack C.<p>Haven't worked on my <a href="https://indieweb.social/tags/Pinball" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pinball</span></a> code <a href="https://indieweb.social/tags/disassembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>disassembly</span></a> much directly, but I have been working to get all the tools I need collected. It seems like once I've used <a href="https://indieweb.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> to annotate and explore the code I'll want to bring the disassembled "source" into a real editor to actually make my changes. </p><p>To ensure the actual disassembly is compatible with assembling back to EPROM images, I plan to write a script to convert ghidra's code representation into a file that will drive a dedicated 68xx disassembler</p>
Damien Cauquil<p>Hey fedi, if someone knows how to correctly define parallelized instructions in Ghidra's SLEIGH, well, I'm more than interested !</p><p>Or if you are aware of any decent documentation on how to define parallelized instructions in SLEIGH and want to share some pointers, that would be awesome too 😊 </p><p><a href="https://mamot.fr/tags/reverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reverse</span></a> <a href="https://mamot.fr/tags/ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ghidra</span></a></p>
Jack C.<p>Well, since I was last working on my Time Machine <a href="https://indieweb.social/tags/Pinball" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pinball</span></a> reverse engineering project, <a href="https://indieweb.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> updates have blown away whatever I did to install mc6800 processor support, and of course I didn't document what I did. Time to pick up the pieces so I can actually get into the meat of the project.</p><p>Ideally this time I'll set it up so it isn't overridden when the <a href="https://indieweb.social/tags/flatpak" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>flatpak</span></a> is updated.</p><p><a href="https://indieweb.social/tags/ReverseEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReverseEngineering</span></a> <a href="https://indieweb.social/tags/Motorola68xx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Motorola68xx</span></a> <a href="https://indieweb.social/tags/Assembly" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Assembly</span></a> <a href="https://indieweb.social/tags/Documentation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Documentation</span></a></p>
buheratorAs you probably know loadlibrary by <span class="h-card"><a class="u-url mention" href="https://social.sdf.org/@taviso" rel="nofollow noopener noreferrer" target="_blank">@<span>taviso</span></a></span> can load Windows DLL's - including Windows Defenders mpengine.dll - on Linux. <br><br>Since the loader needed some debugging I ended up figuring out how to load the Linux-native mpclient into <a class="hashtag" href="https://infosec.place/tag/ghidra" rel="nofollow noopener noreferrer" target="_blank">#Ghidra</a>'s debugger and use it to debug the PE module too:<br><br><a href="https://github.com/v-p-b/loadlibrary/blob/x64_waffle/GHIDRA.md" rel="nofollow noopener noreferrer" target="_blank">https://github.com/v-p-b/loadlibrary/blob/x64_waffle/GHIDRA.md</a><br><br>This can spare an IDA license and performing dark arts with awk and gas...which is actually pretty badass, so if you want to keep doing that without IDA here's a Ghidra script too:<br><br><a href="https://gist.github.com/v-p-b/c7d934234297158047b678f655c7d99f" rel="nofollow noopener noreferrer" target="_blank">https://gist.github.com/v-p-b/c7d934234297158047b678f655c7d99f</a>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://toot.io/@hisold" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>hisold</span></a></span> OFC <a href="https://infosec.space/tags/Cheats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Cheats</span></a> are a way to learn how to <em>"<a href="https://infosec.space/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hack</span></a>"</em> as in <em>"What if I change the value at this address?"</em></p><ul><li><a href="https://infosec.space/tags/CheatEngine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CheatEngine</span></a> is like the old tool everyone who didn't have a cracked <a href="https://infosec.space/tags/IDE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IDE</span></a> / <a href="https://infosec.space/tags/debugger" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>debugger</span></a> at hand in the days before <a href="https://infosec.space/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a>.</li></ul><p>And I still do recommend anyone interested in <a href="https://infosec.space/tags/IT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IT</span></a> and espechally <a href="https://infosec.space/tags/ITsec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ITsec</span></a> to build themselves their own <em><a href="https://infosec.space/tags/airgapped" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>airgapped</span></a></em> <a href="https://infosec.space/tags/HomeLab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HomeLab</span></a> to <em>"<a href="https://infosec.space/tags/FuckAroundAndFindOut" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FuckAroundAndFindOut</span></a>!"</em> safely within.</p><ul><li>Kinda like a "Dojo" (something that costs $$ per hour in terms of a <em>"remote lab"</em> to even be given access in)...</li></ul><p>And with <a href="https://infosec.space/tags/AntiP2W" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AntiP2W</span></a> becoming mainstream as well as Players despising <a href="https://infosec.space/tags/P2W" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>P2W</span></a> / <a href="https://infosec.space/tags/PayToWin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PayToWin</span></a> / <a href="https://infosec.space/tags/Pay2Win" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pay2Win</span></a> (aka. <a href="https://infosec.space/tags/P2L" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>P2L</span></a> / <a href="https://infosec.space/tags/PayToLoose" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PayToLoose</span></a> / <a href="https://infosec.space/tags/Pay2Loose" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Pay2Loose</span></a>) as well as literal <a href="https://infosec.space/tags/gambling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>gambling</span></a> on some <a href="https://infosec.space/tags/Minecraft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Minecraft</span></a> servers, I don't blame Kids that feel shafted (harder than <a href="https://infosec.space/tags/Millenials" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Millenials</span></a> like myself <a href="https://www.youtube.com/watch?v=hE6jxjKPNZQ" rel="nofollow noopener noreferrer" target="_blank">back</a> in <a href="https://www.youtube.com/watch?v=HiDPTiFHfcs" rel="nofollow noopener noreferrer" target="_blank">the days</a> of <a href="https://infosec.space/tags/HabboHotel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HabboHotel</span></a>) if they decide to fuck with servers <a href="https://www.youtube.com/watch?v=3ARx93JDEaw" rel="nofollow noopener noreferrer" target="_blank">rather than scamming other players</a>…</p>
cryptax<p>That guy hacked his air purifier, reversed part of the Android app, then the PCB, downloaded the firmware and reversed everything .. to integrate it to HomeAssistant! :o</p><p>Didn't know about MessagePack nor esp32knife.</p><p><a href="https://jmswrnr.com/blog/hacking-a-smart-home-device" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">jmswrnr.com/blog/hacking-a-sma</span><span class="invisible">rt-home-device</span></a></p><p><a href="https://mastodon.social/tags/IoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IoT</span></a> <a href="https://mastodon.social/tags/homeassistant" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homeassistant</span></a> <a href="https://mastodon.social/tags/reverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reverse</span></a> <a href="https://mastodon.social/tags/esp32" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>esp32</span></a> <a href="https://mastodon.social/tags/ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ghidra</span></a></p>
Kevin Thomas ✅<p>🚀 Ghidra 11.3 is here! 🚀</p><p>For those of us in reverse engineering, vulnerability research, and malware analysis, this latest release from the NSA brings some important updates:</p><p>🔹 Backward Compatibility – Existing projects from previous versions will work, but programs and data type archives created in 11.3 won’t be usable in older Ghidra versions.<br>🔹 Java 21 Required – If you’re upgrading, make sure your system is running at least JDK 21.<br>🔹 Python 3.9–3.13 Support – Debugging and full-source builds require Python 3 on your system.<br>🔹 Fix for XWindows Server Crashes – If you’ve experienced full logouts or instability, it’s likely due to CVE-2024-31083. The issue is patched in xwayland 23.2.6 and xorg-server 21.1.13—make sure your system is updated!<br>🔹 Ghidra Server Compatibility – Ghidra 11.x clients remain compatible with Ghidra 9.2+ servers, but for best results, servers older than 10.2 should be upgraded.<br>🔹 Native Component Support – Each build includes native decompiler components, but if you’re running on older shared libraries (e.g., CentOS 7.x), you might need to rebuild certain native components like the GNU Demangler.</p><p>If you’re using Ghidra for binary analysis, firmware reversing, or vulnerability research, this update brings stability improvements and potentially better import/analysis results compared to previous versions.</p><p>🔍 Pro tip: If you’ve analyzed binaries in a beta or self-built Ghidra version, re-import and reanalyze them with 11.3 to ensure accuracy.</p><p>🔥 Excited to test out the latest features! Who else is upgrading? What’s your go-to reverse engineering setup?</p><p><a href="https://defcon.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> <a href="https://defcon.social/tags/ReverseEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReverseEngineering</span></a> <a href="https://defcon.social/tags/VulnerabilityResearch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>VulnerabilityResearch</span></a> <a href="https://defcon.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberSecurity</span></a> <a href="https://defcon.social/tags/MalwareAnalysis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MalwareAnalysis</span></a></p><p><a href="https://github.com/NationalSecurityAgency/ghidra/releases" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/NationalSecurityAge</span><span class="invisible">ncy/ghidra/releases</span></a></p>
Kevin Thomas ✅<p><a href="https://defcon.social/tags/GhidraBytes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GhidraBytes</span></a> 0x03 - ATmega328P Blink Driver: We continue our journey with <a href="https://defcon.social/tags/AVR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AVR</span></a> <a href="https://defcon.social/tags/Assembler" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Assembler</span></a> with <a href="https://defcon.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a> by finding the main function, DAT_mem_0025 is a mem mapped IO reg sets the PB5 for the LED and we can see it in the Assembler and Decomple views. <a href="https://defcon.social/tags/Embedded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Embedded</span></a> <a href="https://defcon.social/tags/ReverseEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReverseEngineering</span></a></p>
Luke T. Shumaker<p>Ugg, ret-sync is useless here. It relies on gdb `info proc mappings`, which doesn't work on remote targets. But I have already put the mappings in <a href="https://fosstodon.org/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a>!</p>
postmodern<p>Neat, someone used JRuby to add Ruby scripting support to Ghidra.<br><a href="https://github.com/goatshriek/ruby-dragon#readme" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/goatshriek/ruby-dra</span><span class="invisible">gon#readme</span></a></p><p><a href="https://infosec.exchange/tags/ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ghidra</span></a> <a href="https://infosec.exchange/tags/jruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>jruby</span></a> <a href="https://infosec.exchange/tags/ruby" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ruby</span></a></p>
Kevin Thomas ✅<p>Really excited about teaching my, "Hacking Bits", course to the 91st Cyber Brigade w/ the Virginia National Guard! It will be jam-packed with <a href="https://defcon.social/tags/ReverseEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ReverseEngineering</span></a> with <a href="https://defcon.social/tags/Ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ghidra</span></a>, in addition to learning Embedded C++ using an ATmega128p with AVR Assembler! See you all in April!</p>
cryptax<p>I've been running decai with Claude AI on a malware named Goldoon.</p><p>Ghidra is usually quite good to decompile, but just compare the decompiled output with r2 (<span class="h-card" translate="no"><a href="https://infosec.exchange/@radareorg" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>radareorg</span></a></span>) decai/Claude and ghidra!<br>This is marvelous. So much clear and concise + Claude immediately thought this was malicious (I didn't hint anything).</p><p>NB. I will talk about this at <span class="h-card" translate="no"><a href="https://infosec.exchange/@1ns0mn1h4ck" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>1ns0mn1h4ck</span></a></span> </p><p><a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> <a href="https://mastodon.social/tags/radare2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>radare2</span></a> <a href="https://mastodon.social/tags/decai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>decai</span></a> <a href="https://mastodon.social/tags/ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ghidra</span></a></p>
buherator<p>If you use <a class="hashtag" href="https://infosec.place/tag/vim" rel="nofollow noopener noreferrer" target="_blank">#vim</a> to edit <a class="hashtag" href="https://infosec.place/tag/ghidra" rel="nofollow noopener noreferrer" target="_blank">#Ghidra</a> sources, beware that some build scripts try to handle all files in a directory, so .swp’s can cause build errors. </p><p><a class="hashtag" href="https://infosec.place/tag/protip" rel="nofollow noopener noreferrer" target="_blank">#ProTIp</a></p><p>(Neovim stores swap files under your config directory by default, so the situation is better there)</p>
卡拉今天看了什麼<p>Under the microscope: Ecco the Dolphin — Defender of the Future</p><blockquote><a href="https://readhacker.news/s/6hBnW" rel="nofollow noopener noreferrer" target="_blank">Link</a></blockquote>📌<span> Summary: 本文探討《海豚艾可:未來的捍衛者》中隱藏的作弊功能,這些功能通過特定的存檔名稱激活。使用Ghidra和Python進行逆向工程後,作者發現了多個特殊名稱及其對應的效果,如「不死模式」和顯示FPS。文中詳細介紹了作弊的激活方式及其背後的編碼機制,並指出雖然部分名稱可以解鎖相同的功能,但仍有一個名稱(POPELY)不明其用途。最後,作者提到有其他文章深入探索未知的作弊代碼。<br><br></span>🎯<span> Key Points: <br>- 《海豚艾可:未來的捍衛者》含有多種激活作弊功能的名稱。<br>- 使用Ghidra分析後,發現了特殊名稱與相應效果的關聯。<br>- 每個特殊名稱可以解鎖不同的功能,例如:不死模式、顯示FPS、以及搶球遊戲。<br>- 透過暴力破解和Python程式確定其他特殊名稱的效果。<br>- 名稱POPELY的具體效果尚未確認,可能為「無效」。<br><br></span>🔖 Keywords: <a href="https://social.mikala.one/tags/海豚艾可" rel="nofollow noopener noreferrer" target="_blank">#海豚艾可</a> <a href="https://social.mikala.one/tags/作弊代碼" rel="nofollow noopener noreferrer" target="_blank">#作弊代碼</a> <a href="https://social.mikala.one/tags/逆向工程" rel="nofollow noopener noreferrer" target="_blank">#逆向工程</a> <a href="https://social.mikala.one/tags/Ghidra" rel="nofollow noopener noreferrer" target="_blank">#Ghidra</a> <a href="https://social.mikala.one/tags/暴力破解" rel="nofollow noopener noreferrer" target="_blank">#暴力破解</a><p></p>
IT News<p>MOTU Audio Interface Resurrected After Some Reverse Engineering - These days, when something electronic breaks, most folks just throw it away and ge... - <a href="https://hackaday.com/2024/10/18/motu-audio-interface-resurrected-after-some-reverse-engineering/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">hackaday.com/2024/10/18/motu-a</span><span class="invisible">udio-interface-resurrected-after-some-reverse-engineering/</span></a> <a href="https://schleuss.online/tags/reverseengineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reverseengineering</span></a> <a href="https://schleuss.online/tags/audiointerface" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>audiointerface</span></a> <a href="https://schleuss.online/tags/repairhacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>repairhacks</span></a> <a href="https://schleuss.online/tags/linuxhacks" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>linuxhacks</span></a> <a href="https://schleuss.online/tags/firmware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>firmware</span></a> <a href="https://schleuss.online/tags/ghidra" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ghidra</span></a> <a href="https://schleuss.online/tags/hack" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hack</span></a> <a href="https://schleuss.online/tags/motu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>motu</span></a></p>