hacking-and-coffee/defcon-for-n00bs

DEF CON for N00bs is an open guide for first time attendees to the convention.

DEF CON for N00bs

Introduction to DEF CON for N00bs

DEF CON for N00bs is an open guide for first time attendees to one of, if not the, best hacker conventions. This repo allows people to submit changes to include, suggested docs, resources, etc. Use of a Git repo allows for a lot more people to contribute items no matter how small, without having to use any propreitary tools or collaboration environments.

This document is meant to Grow

• To all who contribute, I thank you.
• To all who read this, I wish you luck.
• To all who think they know something better, submit a pull request.

Cheers,

-Hon1nbo

Introduction to DEF CON

DEF CON generally needs no introduction. However, we are aware that there will be people not familiar with the security industry and culture attending. Sometimes they are sent by employers, sometimes they are just curious and happen to be in Vegas. For those who are unaware, all we will say here in the introduction is that the networks are some of the most hostile you will ever encounter. The Wall of Sheep is real and easy to get on and this event is the combination of some of the most brilliant minds in industry, some of the most annoying pranksters, and (usually) well-meaning drunks. The history of DEF CON and its background are generally out of scope for this repo, we recommend you UTFSE if you are still reading this and haven't moved on yet to the various sections.

Categories

The repo is broken into a few different sections:

• Essentials
• Tips & Tricks
• Images

Essentials

The Essentials folder has guides for knowledge that, as the name suggests, is essential for the event. It includes topics such as:

• Securing your tech
• Travel
• Do's and Don'ts of the event

If any of the topics presented are unfamiliar to you, read them before heading to Tips and Tricks.

Tips & Tricks

The Tips and Tricks folder is for the submission of items that aren't essential, but make life at the con easier. Anything can go here if it helps out DEF CON attendees.

Images

The Images directory is used for diagrams, references, or anything that does not fit well in the text portions of the repo. All images should go here, and be referenced by their correspeonding text.

defcon-for-n00bs's Issues

Additon to Do and Dont list

I would recommend adding:

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

Split out Original personal recommendations

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.

Proposed Format Changes (Jekyll, Markdown, etc)

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.

Adjust threat modeling

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.

Typos and grammar

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