Bang on Iain! As much as the example in the blog post works, getting c2 over any form of filesystem, is the real gem here.
Even locally for privesc, get a system shell without worrying about proxies for example.
Looking forward to see what folk come up with use case wise.
This is such a cool C2 channel technique. Use network file share, RDP mapped drives and anywhere else more than one host sees the same filesystem as a C2 channel which really doesn't get logged. Simple but effective!
Was recently tinkering with DPAPI and CREDHIST and managed to find a way to extract hashes for old passwords and recover them in a new module written for hashcat. Blog -> https://t.co/iX9mn4DdUd
@rvrsh3ll@T3chFalcon This has "Anything is a sex toy if you try hard enough" vibes.
DLP isn't going to stop you if you intend to exfil. It will prevent accidental derps, it will hamper illegitimate efforts, but it won't prevent a determined individual from achieving it.
@0xTib3rius@WifiRumHam May I offer you a name suggestion for your merger? The Cyber Reconnaissance and Autonomous Penetration Suite for Heuristic Offensive Operations and Testing #CRAPSHOOT
@TNHillbillyHack@domchell Which ethically brings it back to assume breach. Humans will fold under the right pressure, if you want to simulate the coercion of someone. You read them in and use them as your foothold. I don't need to bribe a call center employee, they just have to follow my instruction.
@Officialwhyte22 D. As you asked - most likely. The chance my mate's wifi is being targeted is low and ET will generally affect other devices and is usually accompanied by deauths. So they're targeting my device only, but at my mates? Nah.
It's D or E. My mates being a dick and fucking with me.
@UK_Daniel_Card I don't get the need for rage. Surely it's...
From ffmpeg: "you're welcome to submit a pull request".
From sec researcher it's: "I've given <project> all the time I'm willing to. Time for a CVE."
From user it's: "ffmpeg has a vulnerability we do not like, we'll switch to xyz"
@hakluke Might be too in the weeds but the fact that for some reason it appears the world has happily renamed DLL Hijacking to DLL sideloading despite its specific meaning, and this grinds my gears.
@BaffledJimmy Very similar to one of my favourite presenters on leadership and team dynamics: Nickolas Means https://t.co/5xBAtInoC8
He's done a few (3 mile island, fukashima, etc), might be worth a look :) would definitely watch you presenting similar at a con aimed at cyber.
@downpressor@IceSolst Wrong perpetrator and the wrong law.
Try thanking the commercial entities who deliberately employ hostile UX and the amendments to the ePrivacy directive in 2009 which is when cookie notices became a requirement.
None of the privacy laws force providers to use hostile UX.
@_CRUXNET @arpeyton@nickvangilder No not at all, i'm saying an entry level penetration tester is not an entry level IT position.
Hence why i'm already expecting them to have experience in IT and apply security concepts to their domain experience.
@_CRUXNET @arpeyton@nickvangilder That's not really an answer to what I stated.
Yes, compliance will be part of a junior's job (in as much as its part of a senior's too) but it isn't (or shouldn't be) all a junior is expected to do.
If I needed that, i'd employ a Vuln. Analyst as part of a Vuln Mgmt team.
@nickvangilder For me, an entry level in penetration testing is not an entry level position in IT.
They should have experience across the domain already, that they can apply to identify security issues.
I think that's the issue here, lots of people thinking junior = "just nessus" when its not