> For the complete documentation index, see [llms.txt](https://shmoo.gitbook.io/2016-shmoocon-proceedings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shmoo.gitbook.io/2016-shmoocon-proceedings/foreword.md).

# Foreword

Here we have the third edition of The ShmooCon Proceedings - our ongoing project to document the knowledge and information put forth by ShmooCon speakers every year.

Putting things in print, rather than relying on videos and PowerPoint presentations, accomplishes two things. First, these proceedings force ShmooCon speakers to wrangle all their thoughts and feelings on a topic and capture them in 1,000 words. This can be no small feat given the complexities of the topics covered at the conference. Second, these proceedings provide you, the reader, with a citable, permanent source of knowledge that you can leverage as you move forward in your cybersecurity endeavors (yes, we said cyber).

We are excited to publish another year of proceedings. Thanks to everyone who contributed to this edition. This starts with the volunteers who show up and generously donate their time, helping us produce ShmooCon each and every year. Thanks to Rob Fuller for his continued role as ShmooCon Proceedings editor. Most especially we thank the speakers, whose hard work is represented in these pages.

Thanks and enjoy!

Heidi Potter


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://shmoo.gitbook.io/2016-shmoocon-proceedings/foreword.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.