text stringlengths 0 2.35k |
|---|
[2311.08 --> 2312.38] move back stuff |
[2312.38 --> 2313.92] from the return values |
[2313.92 --> 2314.72] back on the stack, |
[2314.84 --> 2315.02] et cetera, |
[2315.12 --> 2316.44] just already there. |
[2316.98 --> 2317.58] And I think that |
[2317.58 --> 2318.44] on that level, |
[2318.88 --> 2320.06] they're going to |
[2320.06 --> 2321.24] be pretty efficient |
[2321.24 --> 2322.40] and to go pretty fast. |
[2323.34 --> 2323.56] Nice. |
[2324.10 --> 2324.64] Good to know. |
[2324.80 --> 2325.68] It's always encouraging. |
[2325.68 --> 2329.74] So Go is kind of built |
[2329.74 --> 2330.66] in a way that you don't |
[2330.66 --> 2332.26] debug this line by line |
[2332.26 --> 2333.26] with breakpoints |
[2333.26 --> 2333.78] and so on |
[2333.78 --> 2334.38] as you do in many |
[2334.38 --> 2334.96] other languages, |
[2334.96 --> 2336.16] but you do something |
[2336.16 --> 2337.24] and you check for errors |
[2337.24 --> 2337.90] all the time. |
[2338.46 --> 2339.30] I will not ask you |
[2339.30 --> 2340.32] whether malware |
[2340.32 --> 2341.46] is generally written |
[2341.46 --> 2342.42] like this or not |
[2342.42 --> 2343.34] or how good are they |
[2343.34 --> 2344.74] with their error catching |
[2344.74 --> 2345.98] unless you know |
[2345.98 --> 2346.96] and then please do share. |
[2347.40 --> 2348.40] I do know actually |
[2348.40 --> 2349.90] because I end up |
[2349.90 --> 2350.54] reading the code, |
[2350.74 --> 2350.94] right? |
[2350.94 --> 2353.42] So what I learned |
[2353.42 --> 2354.56] about Go |
[2354.56 --> 2355.76] by reading assembly code |
[2355.76 --> 2357.44] and also by trying it myself |
[2357.44 --> 2358.00] and to understand |
[2358.00 --> 2358.68] what was going on |
[2358.68 --> 2359.42] is the fact that |
[2359.42 --> 2361.12] the Go language |
[2361.12 --> 2362.66] will not allow you |
[2362.66 --> 2364.12] to not catch the errors, |
[2364.34 --> 2364.58] right? |
[2364.94 --> 2365.58] If you have a function |
[2365.58 --> 2366.96] that returns to return values |
[2366.96 --> 2368.86] and if you do not catch them, |
[2368.96 --> 2369.36] then you're going |
[2369.36 --> 2369.88] to be in trouble, |
[2370.00 --> 2370.14] right? |
[2370.18 --> 2371.14] The code is not going |
[2371.14 --> 2371.60] to compile. |
[2372.32 --> 2374.24] So I think you can probably |
[2374.24 --> 2375.92] create this underscore variable |
[2375.92 --> 2376.90] that means I don't care. |
[2377.02 --> 2377.30] Yes. |
[2377.50 --> 2377.68] Right? |
[2378.50 --> 2380.00] But as far as I can tell, |
[2380.32 --> 2380.92] malware developers |
[2380.92 --> 2381.72] at least for the programs |
[2381.72 --> 2382.26] that I've seen, |
[2382.46 --> 2384.14] they do catch the errors |
[2384.14 --> 2385.32] and they check for the errors |
[2385.32 --> 2386.72] and they handle them properly, |
[2387.28 --> 2388.60] which I think makes sense, |
[2388.70 --> 2388.90] right? |
[2388.92 --> 2389.96] Because if the language |
[2389.96 --> 2391.22] forces you to do it, |
[2391.62 --> 2392.58] then you're going to do it. |
[2392.64 --> 2393.08] Like, of course, |
[2393.10 --> 2394.30] you can circumvent this |
[2394.30 --> 2395.24] by, you know, |
[2395.28 --> 2396.50] using this special variable |
[2396.50 --> 2397.74] and not actually checking. |
[2397.96 --> 2400.02] But if the mechanism is there |
[2400.02 --> 2400.92] and if the language |
[2400.92 --> 2402.96] creates the framework |
[2402.96 --> 2403.86] where you kind of |
[2403.86 --> 2404.66] have to do it, |
[2404.76 --> 2405.94] then it's kind of feel foolish, |
[2406.02 --> 2406.38] I think, |
[2406.46 --> 2406.96] to not do it, |
[2407.00 --> 2407.50] even though you can. |
[2407.58 --> 2408.48] Because if you don't want |
[2408.48 --> 2409.18] to do those things |
[2409.18 --> 2410.34] and just go back to C |
[2410.34 --> 2411.64] and play without |
[2411.64 --> 2413.10] any safety belts |
[2413.10 --> 2413.64] and, you know, |
[2413.64 --> 2416.62] just play by your own rules. |
[2416.70 --> 2417.12] But if you're going |
[2417.12 --> 2418.00] to use the Go language, |
[2418.10 --> 2419.18] I think it makes sense |
[2419.18 --> 2421.00] to use the language |
[2421.00 --> 2421.88] as it was intended. |
[2422.06 --> 2422.74] And this is, in fact, |
[2422.78 --> 2423.32] what I'm seeing |
[2423.32 --> 2424.74] when I look at malware code. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.