text stringlengths 0 2.35k |
|---|
• The current reverse engineering tools, such as IDAPro, are not innovative and have not been significantly improved in 20 years due to lack of competition. |
• Ghidra, an open-source competitor, has driven some improvements but even then, the industry is relatively stagnant. |
• The compiler currently uses algorithmic means without AI or machine learning applied to its decompilation process. |
• Discussion of company's R&D capabilities |
• Comparison with Ghidra, an open-source decompiler |
• Speculation about AI involvement in the decompiler |
• Lack of awareness of any plans to work on AI-powered decompilers |
• Expertise required for machine learning algorithm tuning |
• Possibility of a secret project working on this technology |
• Market impact and potential disruption to industry |
• Idea to create an AI that translates assembly language to Go |
• Requesting an AI that analyzes malware in the style of a specific developer's code |
• Proposal for a plugin that identifies the style of malware code |
• Mention of existing research projects on similar topics in the intelligence field |
• People were already obtaining code from open source repositories |
• Attempting to extract characteristics of developers from their code |
• Hoping to identify authors of malware in the future |
• Intelligence services would be interested in this capability |
• It's possible that intelligence agencies spent money on similar projects for research purposes |
• The field of extracting developer characteristics is a new avenue of research |
• Discussing existing problems and the lack of progress in solving them |
• Mention of interesting developments and new ideas for tools and projects |
• Discussion of future plans, including expanding knowledge on Go language and conducting actual research |
• Joking about being unpopular but having a personal guarantee that implementing one of the discussed ideas would lead to great success |
• Closing remarks and thanks to the audience |
• The software world is constantly changing and evolving. |
• The changelog website provides news on recent changes in the tech industry. |
• Partners Fastly and Fly.io are thanked for their contributions to Go Time podcast. |
• A mysterious guest, Breakmaster Cylinder, is thanked for participating. |
• The beat supply is credited with keeping things "swole". |
• The community is invited to connect with the hosts at changelog.social. |
• Next episode's topic will be on making Go code more efficient through modern observability practices. |
[0.00 --> 6.52] This week I was working on another APT case and one of the malware implants that we found there was actually written in Pascal. |
[6.84 --> 11.44] And so it was kind of a trip down the memory lane to one figure out what Pascal was again. |
[11.82 --> 16.78] And also trying to understand what kind of assembly was generated by this Pascal compiler. |
[16.94 --> 20.24] It wasn't that bad, actually. Way less bad than having to discover the Go language. |
[20.24 --> 28.30] What's up, friends? This episode is brought to you by Sourcegraph. |
[28.76 --> 34.20] With the release of Sourcegraph 4.0 and the Starship event just a few weeks behind us, |
[34.40 --> 40.62] it's super clear that Sourcegraph is becoming not just CodeSearch, but a full-on code intelligence platform. |
[41.00 --> 44.16] And I'm here with Joel Cortler, Product Manager of Code Insights for Sourcegraph. |
[44.46 --> 49.08] Joel, this move from CodeSearch to code intelligence is a really big deal. |
[49.08 --> 55.46] How would you explain this feature, Code Insights, if you're just talking to folks in the hallway track of your favorite conference? |
[56.06 --> 60.28] I would really start with technical because before I was a product manager, I used to be an engineer as well. |
[60.60 --> 65.42] And it's really cool and exciting just to be able to say, we're going to turn your code base into a database. |
[65.94 --> 70.32] And the structured language that you need to interact is just the ability to write a code search. |
[70.60 --> 72.54] You know, literal search, that's totally fine. |
[72.70 --> 76.34] Regular expression, you know, that'll give you a few more advanced options, even a structural search. |
[76.34 --> 82.88] But the number of long-tail possibilities it unlocks, truly the journey of building this product was just saying, |
[83.02 --> 86.08] well, we've just unlocked, you know, an infinite number of possibilities. |
[86.52 --> 91.16] We got to figure out some immediate use cases so we can start to, you know, invest in this product, build it and sell it. |
[91.36 --> 95.58] But we're only getting started in terms of the number of uses that we're uncovering for it. |
[95.58 --> 103.32] The story I told you about discovering, like, version tracking turned out to be a really important use case that wasn't even on our roadmap six months prior to discovering that, |
[103.38 --> 111.34] as we were already planning to launch this product, until we talked to enough folks, realized this was a problem, and then found, well, oh, that's like a simple regular expression capture group that you can just plug right in. |
[111.42 --> 114.96] Because we really built this system to not limit the power of what we built. |
[114.96 --> 119.06] We don't want to give you, like, three out-of-the-box templates, and you can only change, like, one character or something. |
[119.16 --> 122.06] It's truly, like, the templates are there to hold your hand and get you started. |
[122.20 --> 126.34] But if you can come up with anything you want to track in your code base, you can do that with Code Insights. |
[126.64 --> 127.74] I love it. Thank you, Joel. |
[127.86 --> 132.48] So right now, there is a treasure trove of insights just waiting for you. |
[132.76 --> 138.26] Living inside your code base, your code base is now a querible database thanks to Sourcegraph. |
[138.26 --> 142.80] This opens up a world of possibilities for your code and the intelligence you can gain from it. |
[143.06 --> 148.32] A good next step is to go to about.sourcegraph.com slash code dash insights. |
[148.64 --> 149.88] The link will be in the show notes. |
[150.24 --> 152.74] See how the teams are using this awesome feature. |
[152.98 --> 157.82] Again, about.sourcegraph.com slash code dash insights. |
[158.16 --> 160.44] Again, this link is in the show notes. |
[168.26 --> 176.44] Let's do it. |
[177.02 --> 178.06] It's Go Time. |
[178.56 --> 179.96] Welcome to Go Time. |
[180.96 --> 184.82] Your source for diverse discussions from all around the Go community. |
[185.74 --> 187.72] Changelog has joined the Fediverse. |
[188.56 --> 191.62] Find our Mastodon instance at changelog.social |
[191.62 --> 195.06] and connect with us at gotime at changelog.social. |
[195.06 --> 200.80] Thanks to our partners at Fastly for delivering Go Time super fast all around the world. |
[201.00 --> 202.90] Check them out at fastly.com. |
[203.22 --> 205.18] And to our friends at fly.io. |
[205.50 --> 207.34] Deploy your app servers close to your users. |
[207.72 --> 208.82] No ops required. |
[209.16 --> 211.20] Learn more at fly.io. |
[211.56 --> 213.34] Okay, here we go. |
[216.34 --> 223.58] Today, Ivan Kwiatkowski, you are joining us again to talk more about hacking with Go |
[223.58 --> 227.52] and cover all the things we did not manage to cover in our last episode. |
[228.42 --> 229.90] Yes, very happy to be back here. |
[230.78 --> 234.02] So for those who did not tune in to the previous episode, |
[234.30 --> 235.88] could you shortly introduce yourself? |
[236.72 --> 237.46] Yes, of course. |
[237.66 --> 239.86] So my name is Ivan Kwiatkowski. |
[240.12 --> 241.98] I am a French cybersecurity researcher. |
[242.48 --> 244.14] And I work for Kaspersky. |
[244.38 --> 247.04] Specifically, I work in a threat intelligence team. |
[247.04 --> 252.18] And my role in this team, apart from writing reports and that kind of stuff, |
[252.34 --> 258.22] is really to proceed with the reverse engineering of the malware that is provided to me by my coworkers. |
[258.58 --> 260.04] So basically, they do the threat hunting. |
[260.40 --> 263.18] They find some interesting stuff to look at. |
[263.38 --> 266.90] They identify implants used by the attackers and they give them to me. |
[266.90 --> 272.66] And then my job from there is using the fantastic tools of the reverse engineer, |
[272.92 --> 274.24] which are Ida Pro, basically. |
[274.68 --> 279.16] I do read the assembly code of those programs and try to figure out what they do as best as I can. |
[279.64 --> 280.56] And that's my life. |
[281.22 --> 288.30] And in the previous episode, we talked a little bit about how Ida is yes or no supporting Go, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.