looks like an airplane banner that got loose.

Explore our detailed Telnet vulnerability research:

📌 Guest Bypass: github.com/hackerhouse-...

📌 Mutual Auth: github.com/hackerhouse-...

📌 Telnet Client MS-TNAP PoC: github.com/hackerhouse-...

#HackerHouse

Not every bug can be a vulnerability and not every vulnerability can be exploited, the MS-TNAP issue I describe exists within the protocol for Telnet authentication using NTLM and partially in the Telnet Server code, but was not fully implemented by Microsoft. PoC's are available for both issues.

have you tried turning it off and on again?

"MSRC didn’t consider a single report as a vulnerability." - is something I agree with, you need the Administrator password to leverage this and whilst Task Scheduler is awesome and tons of fun - you need some kind of boundary violation for this to be an issue. "I have the password" is not one.

It reads to me as a surface-level analysis of the Task Scheduler implementation with the remarkable realization that "Task Scheduler can run Tasks as other users!" 🫢 - I enjoyed the write up but this is a very misleading post.

I was conversing, you unthreaded my comment which is just sad to see.

I often discuss in my talks about how political bias influences and shapes the technology we build and use. The "underground" of computing technology has typically been right of center which is where many interesting protocols have come from. Internet is healing and people are free to speak again.

Political-bias on BlueSky is largely left-leaning, it's a comment that "verification" is just an extension of those political biases on display where those who ascribe to particularly agendas and ideologies leverage institutions and systems as power in the society.

Those who ascribe to extreme-left "woke" ideology.

The woke do love assigning themselves perceived authority over others.