asciinema VS OSCP-Exam-Report-Template-Markdown

Incorrect link. Just goes to the list of open requests.

Here is a ticket which mentor the rust rewrite, perhaps this was what was intended: https://github.com/asciinema/asciinema/pull/579

Location: Europe

Remote: Yes

Willing to relocate: No

Technologies: Rust, Elixir, Nix(OS), WASM, AWS

Résumé/CV: Available upon request

Github: https://github.com/ku1ik

Open-source: creator of https://asciinema.org, contributor and maintainer of many other projects (see Github profile)

Email: hnhire /at/ defn /dot/ 33mail /dot/ com

20 years of professional experience. I enjoy anything backend related, e.g APIs, profiling and solving performance problems, building high performance, low-latency network solutions, among many other things.

This might be a good usecase for https://asciinema.org/

I do quite a lot of this kind of stuff for my job. Some context that may be useful.

Often the full IDE is needed. I record a lot of gifs of VSCode, where part of the gif is typing code, part is interacting with the rest of the IDE / terminal - perhaps to run the code and view the output.

For me the killer app would be one which could pre-record keystrokes (and maybe mouse actions) so that I could do them error free. I often attempt a gif 10 times before I'm happy with the outcome.

I don't personally love the transition animation. I would want the option for something that seems like it's being typed.

The closest tools I've found are:

Typewriter VSCode extesion: Allows you to copy text and then "types" it out for you. https://marketplace.visualstudio.com/items?itemName=dansilve...

Ascii Cinema: https://asciinema.org/

but it seems pretty popular for this kind of screen recording.

[1] https://asciinema.org/

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