Originally posted by ericminimumwage
View Post
DEF CON's official policy on attending DEF CON: (subject to change without notice)
https://www.defcon.org/html/links/dc-faq/dc-faq.html
Originally posted by URL
Advice: Check out the redit defcon area, and read content from several twitter accounts:
* https://www.reddit.com/r/Defcon/
* https://twitter.com/thedarktangent
* https://twitter.com/dcib
* https://twitter.com/defcon
* https://twitter.com/DEFCON_NOC
* https://twitter.com/Niki7a
* https://twitter.com/v3rtig0
* https://twitter.com/Grifter801
* https://twitter.com/defcon101
Review the DEF CON FAQ (see link at top of this post.)
See if there is a "DEF CON Group" near you, and if active, attend and get to know people:
https://defcongroups.org/dcpages.html#usa
If no DCG are near you, try 2600 groups, or computer clubs, or User Groups for various OS, or form your own group. Networking with people that have different experiences exposes you to ideas or concepts you have not yet encountered.
On what to learn, you can review past talks, and watch many on YouTube. Watch for understanding any videos for topics that interest you. When something comes up that you do not understand, pause the video, look it up and understand it, then resume the video. Videos and text from old presentations also give you search terms to use with google to "find out more."
Do not discount old-fashioned books as sources for learning. Some may even be suggested by speakers.
After you heave learned "enough" consider buying tools and resources to test what you know. If you do not have enough money to build a lab, maybe you can build a mini-lab with Raspberry Pi, or install some sort of VM system on your computer and run tiny OS that you can test what you have learned. Work to add an OS and services with no security, break that through attack, then improve security, and try to defeat it, repeat this cycle to learn both sides: offense (red-team) and defense (blue team.)
Beyond basic systems and services, you will probably want to learn some programming languages. Initially, scripting languages would be useful, but as you get into exploits, languages like Assembly, C/C++ would be better for understanding source code of many services, and how many attacks actually work.
When you arrive at DEF CON expect there to be Thursday events, and expect there to be lines. Plan for these.
Consider attending "DC101" or "DEF CON 101" which is an attempt at a presentation to introduce you to DEF CON, how things work, and advices on how to get the most out of your con. Some of this is silly, but that is because some of DEF CON is silly. There are party aspects to DEF CON as much as there are learning opportunities with people you meet, or contests/events/parties/villages/speaker-track-talks.
About 2 to 3 months before con, start looking to see which talks, villages, contests, events, or social gatherings are happening, and make notes of those that interest you.
Build a tentative schedule of those things that interest you, so that during any point of your con there are things you want-to, and can do, even if you choose not to do at the time. Be ready to dismiss anything you planned to do if something better comes up.
Assuming you are going to be 17 next year, you may consider yourself "too old" for "DEF CON rootz" aka "Rootz Asylum" aka "DEF CON Kids" but you might want to compare what they have to the rest of con.
HTH,
-Cot
Leave a comment: