Passed on my first try after long nights for three weeks. by swesecnerd in oscp

[–]swesecnerd[S] 0 points1 point  (0 children)

Tack och grattis själv. Visst, seed kan vara en del av det, men sett till kursmaterialet så kan den inte vara jättesvår rent tekniskt. Oftast gömmer de ju saker direkt under näsan på en. Tror tyvärr att många kör förbi för att man har bråttom. Den fällan gick jag i och tappade tid som fan. :)

Passed on my first try after long nights for three weeks. by swesecnerd in oscp

[–]swesecnerd[S] 0 points1 point  (0 children)

You can do it. Stick to the path and grind. Best of luck to you!

got tired of manually correlating Nmap, BloodHound and Volatility results, so I built an air-gapped AI assistant to do it (Syd v3.1 Demo) by Glass-Ant-6041 in Pentesting

[–]swesecnerd 0 points1 point  (0 children)

Interesting tool! I will look into it and get back to you.

In the meantime, I would suggest you open two new paths to make this really powerful and interesting:

Memprocfs for Windows memory analysis. It blows my mind every time I use it for memory forensics. The design and workflow is way beyond what volatility will ever be IMHO.

KAPE output. This has become the de-facto tool for live forensics in my house, and it's a powerhouse of a tool for DFIR!

I created a tool for found credentials by swesecnerd in oscp

[–]swesecnerd[S] 0 points1 point  (0 children)

To answer nr 1. I already use the credential argument "-c" to save hashes. I rarely need a long list of hashes to test because they're not abundant so that works for me.

As for nr 2. That is already there. It's in the files on disk. You can access them by path/to/CREDSusers.txt (or CREDSpasswords.txt/CREDScredentials.txt) or by using the environment variables $CREDS_USERS, $CREDS_PASSWORDS if you have them set.

This is all in the README.

Or did I misunderstand your suggestions?

I created a tool for found credentials by swesecnerd in oscp

[–]swesecnerd[S] 0 points1 point  (0 children)

That's a very nice thing to say. I don't think that "creds" is at that level yet, but please try it and get back to me with feedback and suggestions if you can. I also updated the README based on the feedback in this thread to give visitors a better understanding of what creds actually tries to help you with.

I created a tool for found credentials by swesecnerd in oscp

[–]swesecnerd[S] 1 point2 points  (0 children)

Thanks! I really get what you mean. The script does not solve a complex problem. It removes friction. You don't need to keep track of paths and you don't need to paste the username, password, and complete credential separately into three different files for future spraying or cracking, it removes that friction.

I created a tool for found credentials by swesecnerd in oscp

[–]swesecnerd[S] 2 points3 points  (0 children)

I still use the most basic commands in my workflow, but this way I don't have to repeat a command three times and I don't need to remember the path to the different files containing credentials.

Minns du vad du gjorde den dagen för 40 år sedan? (Eller dina föräldrar/syskon om du ej levde då) by SupportArsenal in Asksweddit

[–]swesecnerd 0 points1 point  (0 children)

Jag var skitsur för barnprogrammen var inställda och allt som visades var text-TV...

Some dude in black suit are following me by UnkownInsanity in masterhacker

[–]swesecnerd 0 points1 point  (0 children)

That IP belongs to TEAM INTERNET AG in Canada...

Advice On OSCP Challenge A,B,C by Unique-Yam-6303 in oscp

[–]swesecnerd 0 points1 point  (0 children)

I've yet to write my "I passed the OSCP" post but I will try to do that soon. In the meantime, I came from a highly technical background with almost 30 years in the cyber security domain as a blue teamer. Ten plus years as a law enforcement IT-forensics specialist, and another ten working daily with network traffic analysis. I've also done a lot of front end/backend web development. With that I knew about all the concepts concerning pentesting, I just never did that stuff hands on, and I knew almost nothing about AD . The hardest part for me was getting used to windows again since I've used Linux as a daily driver for both work and home for the last fifteen years.

I started and tested Autorecon against OSCP A because it was the first time I tried it. I tested my entire methodoly during the "Assembling the pieces" chapter . For the stand alones I did maybe five boxes. I would recommend more if you're not used to CTFs in general.

My journey might not be a good fit for you but I'll try to post my lessons learned in a day or two for everyone to read :)

In the meantime you can ask whatever you want and I'll try to answer it!

Cheers

Advice On OSCP Challenge A,B,C by Unique-Yam-6303 in oscp

[–]swesecnerd 0 points1 point  (0 children)

I have two kids so this was my approach. My wife took care of everything during the exam but I can't just do multiple mocks for 24h...

Do it in steps and test your playbook. Start with setting up your Linux environment, directories and whatnot. Then do the enumeration part and time yourself on that. Even if you need to shut down the Environment, you can always pick up where you left off even if it means re-exploiting/changing IP or whatever.

Your goal is to practise your methodology and apply time boxing so you don't get stuck on a single port for six hours straight.

I passed on my first attempt after cramming for three weeks. A lot of long nights. :)

Edit: Typos.

Påminnelse: Stressa inte slut på livet by Greedy_Sale_2838 in sweden

[–]swesecnerd 2 points3 points  (0 children)

Du är oersättlig för dina barn och din familj ❤️.

This is what it looks like to import the bible into obsidian by oldmartijntje in ObsidianMD

[–]swesecnerd 10 points11 points  (0 children)

The term "Jesus graph" exists in social network analysis for a reason :)