wh0crypt

👾 CTF Player
🎓 Computer Engineering
💻 Low-level, Malware & Hardware
📡 Aviation, Drones, Navigation & RF

[wh0crypt @wh0crypt]

I just earned the Active Directory Red Team Specialist certificate from @cyberwarfarelab!

I started taking it when I was attending a conference and got impressed by the knowledge I could acquire. Recommended. Next cert: CRT-ID?

[wh0crypt @wh0crypt]

@allthingsida sounds quite fun!

[allthingsida @allthingsida]

72 slides done. Who’s ready?

[wh0crypt @wh0crypt]

@renegandola @_LonelyS0ul_ más que frontend y backend diría que lo primordial es aprender a programar a secas, la lógica, sin paradigmas

[Creed @creedlogic0]

@wh0crypt @TrisH0x2A @Hassan_Abedi I agree with Linus, but I still wonder why browsers are written in C++. Even a new one like Ladybird started with C++, and now it's moving toward Rust

[wh0crypt @wh0crypt]

@Iberia aprecio la iniciativa y tal, pero no me sirve que los vuelos alternativos que me déis sean para un día antes del vuelo previsto, tendría que pagar por el cambio de billete de tren :S pensé que por lo menos me daríais una opción el mismo día, muy mal, haciendo overbooking

[wh0crypt @wh0crypt]

@Hassan_Abedi @TrisH0x2A cause git is Linus's project

[wh0crypt @wh0crypt]

@TrisH0x2A @Hassan_Abedi here's why

[wh0crypt @wh0crypt]

@toukorina

[wh0crypt @wh0crypt]

@ChaoticEclipse0 definitely!

[Nightmare Eclipse @ChaoticEclipse0]

I'm back (maybe), new drip (blog), got some interesting stuff that might be worth reading,
https://t.co/1tTNdd147c

[wh0crypt @wh0crypt]

@atomicnumber88 @zuhaitz_dev is that u

[ゆのれい @Yunolay]

OffSec in the train #OffSec #OSCE3 #OSEE

[wh0crypt @wh0crypt]

@TheEduardoRFS reminds me of prolog 😭

[wh0crypt @wh0crypt]

@vxunderground send link

[wh0crypt @wh0crypt]

@devabram @zuhaitz_dev nah companies are boring i wanna press buttons and get paid

[wh0crypt @wh0crypt]

@zuhaitz_dev @devabram we should a start a team and get paid too

[wh0crypt @wh0crypt]

@stanziirl gg! keep going!

[Strace @straceX]

the cost of a virtual call was never the vtable lookup. that's just a pointer load, and modern CPUs are very good at loads.

what actually matters is the indirect branch that comes after it. the CPU wants to know where execution goes next so it can keep speculating ahead. When the branch predictor gets that target right, a virtual call is often surprisingly cheap.

the trouble starts when the same call site sees many different targets. prediction becomes harder, mispredictions increase, and the CPU has to throw away speculative work and start again.

that's why a monomorphic virtual call site can be almost free while a megamorphic one can become expensive.

virtual calls are slow was always an incomplete explanation.

the real question is how predictable the call target is.