hacking-and-coffee / defcon-for-n00bs Goto Github PK

I originally gave my handle in recommendations for some items, to clarify it was opinion of the author rather than the best solution. These should be split up to a separate area as workable solutions, with additional solutions added.
In the writing it comes off as authoritative which isn't appropriate for a guide like this.

Issue opened since I am away from dev machine. Anyone may take.

Part of the original data set that was compiled for this called for mentioning DC is the kind of place a hypervisor 0day might drop. In reality that seems like a borked threat model.
The various scenarios need to be double checked. Right now they lie on the conservative side, but FUD isn't something that should be in this repo.

Opened this issue to keep track of things I can't get to away from my dev machine.

Time of year to review this, and I'm spotting typos I somehow missed before.
Opening an issue as a reminder that I need to fix them, or let someone contribute. I'm away from my dev machine currently on travel so opening an issue to prevent losing track

I would recommend adding:

Do: carry cash
Don't: pay by, carry, or demonstrate possession of credit cards or "pay by phone" wallets.

Introduction

A topic up for consideration is the future format. It is better to have this plan @now than to do it later when there is more content.

Current Proposed Options

• GitHub pages using Jekyll/Markdown
• Read The Docs (RTD)

Requirements

• Git version control and collaboration using a public repo (such as this Github)
• must generate static content
• Content must be usable when pulled offline, without using any form of tools (note, this precludes link based pages unless a full archive that is always updated is readily available)

Timeline

Ideally this decision should be made by June, so contributions for the upcoming DC can be made.