OSCP-Exam-Report-Template-Markdown VS flameshot

Thank you! Yes, I used https://github.com/noraj/OSCP-Exam-Report-Template-Markdown and included vulnerability details, as well as how to fix the vulnerability and it got lengthy which I think was unnecessary, but I tried to make it nice and be thorough. I probably should've put more time in trying to fix the other issues I had but oh well.

I am in the process of redacting my report. In fact, I have already documented all 10 machines and all exercises in the lab. However, i have still a question regarding the expected content of it, as the official template as well as some famous templates such as this one mention a whole introduction section containing among all introduction, objectives, requirements, methodologies...

Here a good starting point: https://github.com/noraj/OSCP-Exam-Report-Template-Markdown

Also you can take a look at the OSWE Exam Report Template in Markdown I you prefer to avoid Word.

I wrote my reports in Markdown using the format here. I researched more about pandoc and decided to convert my Markdown documents to docx first, edit them in LibreOffice (Page Breaks, better Table of Contents), and export them to PDF for submission Test your report conversion before the exam. This helped me figure out issues with my report conversion before the exam (issues with special characters in my terminal), and switch to a system that works. Another good report format can be found here, this one provides resources

However things I did do right was to right the whole thing in markdown in obsidian. I used flameshot to get all my screenshots and converted the markdown to a pdf with eisvogel using this GitHub as a template https://github.com/noraj/OSCP-Exam-Report-Template-Markdown

For your screenshots simply use Flameshot: https://flameshot.org

First, conceptually this is what I mean: think about when using a good screen-capture/annotation tool like flameshot: you select a region of the screen, and "magic" you can "edit" it, "in situ". No, what I'm talking about wouldn't share any of the same technical underpinnings with the way flameshot works, it would be the live monitor output, not a raster dump of the screen made to look like it's live. And the annotating would be done on a different screen. But as a user, this is pretty similar.

Flameshot is a free and open-source screenshot tool for Linux that allows users to take screenshots of an area, a window or the full screen. It then provides an editor where users can modify the screenshots by drawing on them, adding text, highlighting areas, blurring parts and more. Users can save the screenshots in common image formats like PNG and JPEG, and upload them directly to image hosting sites like Imgur.

I would recommend Flameshot, available on Linux, Windows and Mac.

This https://github.com/flameshot-org/flameshot/issues/1529 mat or may not be an issue for you with Flameshot, but it may be for others. It's solvable if it is an issue by using mandatory access control such as AppArmor or conditional build. Just FYI.

Flameshot viene con todo eso.

[3] https://github.com/flameshot-org/flameshot/issues/2848