how are you guys finding these bugs any courses. I just want the knowledge.

[kobbycyber]

[ACD421]

Windows is a dumpster fire in code just do one full RE run. Then start the traces you will find lots of stupid coded crap.

[s1lentf00thold]

just understand how ad will work and with complete windows grip in security simple is that🫡

[zkxjzmswkwl]

Windows is a dumpster fire in code just do one full RE run. Then start the traces you will find lots of stupid coded crap.

"Just do one full RE run"

[johnzhou721]

Windows is a dumpster fire in code just do one full RE run. Then start the traces you will find lots of stupid coded crap.

"Just do one full RE run"

I mean if you already have the knowledge neccessary it's quite trivial to find bugs that way... but I don't. So it's more like this

(not that i can draw)

[zkxjzmswkwl]

Windows is a dumpster fire in code just do one full RE run. Then start the traces you will find lots of stupid coded crap.

"Just do one full RE run"

I mean if you already have the knowledge neccessary it's quite trivial to find bugs that way... but I don't. So it's more like this

(not that i can draw)

The knowledge necessary to reverse engineer native binaries requires a considerable amount of time. Hence the "Draw the rest of the fucking owl" image.

That is what I'm saying.

[johnzhou721]

The knowledge necessary to reverse engineer native binaries requires a considerable amount of time. Hence the "Draw the rest of the fucking owl" image.

That is what I'm saying.

Yes, but what I was talking about is that the advice assumes you know how to reverse engineer native libraries, which is already most of the owl; it's on top of this knowledge where they give you a specific component to look for.

With the draw the circles it'd be like "run winRE, then learn reverse engineering."

Sorry for the confusion.

---

I think WinRE is standing for Windows invitation of Reverse Engineers now due to how many bugs it have.

[Salah-Code-Lab]

The knowledge necessary to reverse engineer native binaries requires a considerable amount of time. Hence the "Draw the rest of the fucking owl" image.
That is what I'm saying.

Yes, but what I was talking about is that the advice assumes you know how to reverse engineer native libraries, which is already most of the owl; it's on top of this knowledge where they give you a specific component to look for.

With the draw the circles it'd be like "run winRE, then learn reverse engineering."

Sorry for the confusion.

I think WinRE is standing for Windows invitation of Reverse Engineers now due to how many bugs it have.

well no WinRE is a Recovery Environment that requires physical access
a Recovery Environment is for restoring machines or data basically
so of course you will automatically have the highest privileges without UAC, etc, etc
because it is Physical interaction and since you accessed a locked tool (say CMD locked with a password)
You are one of two things
a Stealer (a Physical one) or the Owner
at the end of the day
Even if WinRE was full of bugs which it may have
a attacker from Russia cannot manipulate it which means it isn't a Vulnerability or a exploit

oh also that guy that says "Run a Trace" and we would find a lot of bugs
if that is so why didn't you find us new zero days and vulnerabilities if it was so easy
then show us educate us or are we just wearing Underwears on our heads ?

[Salah-Code-Lab]

Windows is a dumpster fire in code just do one full RE run. Then start the traces you will find lots of stupid coded crap.

if it was so easy then why didn't you run a "trace" yourself and find a shit tonne of vulnerabilities and post them to microsoft for thousands of dollars ?
where is your proof
where are your vulnerabilities if it is so easy to find ?
let me tell you there are some people who don't wear underwears on their heads

[didotb]

I just want the knowledge.

Learning any programming language, and not just the academia way, will naturally make you learn of all the quirks of that language and how people have tried to hack their way around it, and so you'll learn how to look for these quirks yourself.

If you're interested in systems, however, you'd want to learn C, C++ and assembly. Most of them are still written in these languages. Lately, more and more are turning their head to Rust as well.

Grab a literal ton of coffee, and enjoy the multiple learning curves for each language.