Re: Welcome to DEF CON 21! How would you make DEF CON 22 even better?
I went to the Pentesters Toolkit and the Intro to Web Application Hacking. Honestly I didn't have high hopes for the Web App one as I figured that it was going to be really intro. I was kind of excited about the Pentesters Toolkit, but after around 20 minutes when he started to talk about the benefits of a water bottle and staying hydrated I had to leave.
Once again I wasn't sure whether I should say anything or not. I knew that they were 101 talks, and I shouldn't have attended them. I've been going to Defcon off and on for almost 15 years, although I do remember a DC101 that was awesome. I think it was DC15 or DC16 where the lawyer gave a presentation of all the reasons we would go to jail at the con. It was hilarious and informative.
I'll probably avoid the DC101 stuff next year. Also I forgot to mention, I think it was awesome that that contest area was open on Thursday. I don't remember that being the case in prior years.
As for the vendors, I understand, and I think that you guys did a great job. Just passing some feedback. As I said it wasn't a huge deal, it just meant that I drank slightly more than what I had planned on.
Yeah, hence my apprehension on making a comment. I kind of disagree with a full 101 track throughout the whole con. To me at least, I think there is a certain level of person that goes to Defcon. I believe Defcon to be a higher class, or a more intelligent audience. I think that you should have some skill / drive before showing up. Seomeone who is going to Defcon that plans on learning something should already have the drive to do the preliminary research before the con. They don't need to be an expert, but know a little bit of the basics. I think people that go to Defcon with the assumption that they are going to absorb ninja hacking skills through osmosis are canon fodder in the industry. To me we are still a community of RTFM and then ask questions. If you haven't first put forth the effort to try and do it yourself, then you're a waste of my time. But if you tried something and it didn't work, then I would be more than willing to give guidence and help. Show me the initiative and I will help with the rest.
I apologize, re-reading this post I feel as I come across as a giant ass. But I am too tired / lazy to try and fix it.
@ tecknicaltom
I know what you're saying about the tables in the contest area. Although, last year we had a crap ton of tables in the contest area, and most of the time they were fairly emtpy, or at least when I was there doing Project2. I think we have gone from one extreme to the other.
@TheCotMan
You bring up excellent points. I haven't had enough time to think about them, but I think a general weighting system would be key. Also you may have to arrange the talks into building blocks.
If we take wireless cracking for example:
You would have to ask yourself what your level of knowledge is.
1. Do you know what wireless networking is?
2. Do you know what WEP, WPA, WPA2, EAP/TLS, PEAP are?
3. Do you know airmon, airodump, aircrack, or aireplay?
4. Do you know what WPS is?
5. Do you know what JTR or Hashcat are?
In this example, if you don't know what 1 and 2 are then you would have a beginner talk around wireless technology and the different types of security.
If you know 1 and 2 but you haven't dealt with 3, 4, 5 then you would be an intermediate, and you would learn about different cracking methods.
Advanced would probably be getting better at injecting traffic. Wireless antenna's, tracking, and finding weird frequencies. Maybe even cracking open Wireshark and looking at dumps to pull out information, or plowing through bluetooth, RFID, or NFC.
I think with going with the weighting system those talks would be more based on teaching. I think this is how the Village talks go now. But I also think you would have another classification, and that would be zero day or releasing of code. Those I don't think would be classified the same as a track around teaching something. So you would have at least two main classifications, how to and theory / cracks.
Hackajar gave an awesome talk a few years ago on the ineffectiveness of passwords. While he had hard numbers it wasn't really a how to, and it wasn't really a release of code. It was more theory (proven theory) than anything. Bitweasil the next year gave a talk on Hashcat and how it works and how to use it with EC2 to speed up password cracking. Bitweasil's talk was more of an intermediate talk that gave some how to examples.
I think the first step would be to identify the different types of talks and classify them. If they are going to be more oriented on how to do something, then you could then apply skill levels to help delineate the types of people that will attend them.
One last point, if you are offended because you are a noob then you have some other issues to over come. This year I learned how to hand solder SMD's. I had only done SMD's with a hot plate in the past, but this year I learned how to do it with a soldering iron. I was a complete noob at it and it took me a couple of hours to get the hang of it. But after I figured out how to do it, and I became semi-proficient with the size of components that we were using I was able to start to show others how to do it, and also fix mistakes that people were making. My buddy this year is a skilled developer, but he had never picked a lock before. I don't think he would be offended by being called a noob at lock picking, but he probably would be offended if I called him a noob at programming. We all start somewhere and that somewhere is noob. If you don't want to be called a noob then hone your skills and develop the knowledge to elevate yourself, rather than bitching about it.
I went to the Pentesters Toolkit and the Intro to Web Application Hacking. Honestly I didn't have high hopes for the Web App one as I figured that it was going to be really intro. I was kind of excited about the Pentesters Toolkit, but after around 20 minutes when he started to talk about the benefits of a water bottle and staying hydrated I had to leave.
Once again I wasn't sure whether I should say anything or not. I knew that they were 101 talks, and I shouldn't have attended them. I've been going to Defcon off and on for almost 15 years, although I do remember a DC101 that was awesome. I think it was DC15 or DC16 where the lawyer gave a presentation of all the reasons we would go to jail at the con. It was hilarious and informative.
I'll probably avoid the DC101 stuff next year. Also I forgot to mention, I think it was awesome that that contest area was open on Thursday. I don't remember that being the case in prior years.
As for the vendors, I understand, and I think that you guys did a great job. Just passing some feedback. As I said it wasn't a huge deal, it just meant that I drank slightly more than what I had planned on.
Originally posted by HighWiz
I apologize, re-reading this post I feel as I come across as a giant ass. But I am too tired / lazy to try and fix it.
@ tecknicaltom
I know what you're saying about the tables in the contest area. Although, last year we had a crap ton of tables in the contest area, and most of the time they were fairly emtpy, or at least when I was there doing Project2. I think we have gone from one extreme to the other.
@TheCotMan
You bring up excellent points. I haven't had enough time to think about them, but I think a general weighting system would be key. Also you may have to arrange the talks into building blocks.
If we take wireless cracking for example:
You would have to ask yourself what your level of knowledge is.
1. Do you know what wireless networking is?
2. Do you know what WEP, WPA, WPA2, EAP/TLS, PEAP are?
3. Do you know airmon, airodump, aircrack, or aireplay?
4. Do you know what WPS is?
5. Do you know what JTR or Hashcat are?
In this example, if you don't know what 1 and 2 are then you would have a beginner talk around wireless technology and the different types of security.
If you know 1 and 2 but you haven't dealt with 3, 4, 5 then you would be an intermediate, and you would learn about different cracking methods.
Advanced would probably be getting better at injecting traffic. Wireless antenna's, tracking, and finding weird frequencies. Maybe even cracking open Wireshark and looking at dumps to pull out information, or plowing through bluetooth, RFID, or NFC.
I think with going with the weighting system those talks would be more based on teaching. I think this is how the Village talks go now. But I also think you would have another classification, and that would be zero day or releasing of code. Those I don't think would be classified the same as a track around teaching something. So you would have at least two main classifications, how to and theory / cracks.
Hackajar gave an awesome talk a few years ago on the ineffectiveness of passwords. While he had hard numbers it wasn't really a how to, and it wasn't really a release of code. It was more theory (proven theory) than anything. Bitweasil the next year gave a talk on Hashcat and how it works and how to use it with EC2 to speed up password cracking. Bitweasil's talk was more of an intermediate talk that gave some how to examples.
I think the first step would be to identify the different types of talks and classify them. If they are going to be more oriented on how to do something, then you could then apply skill levels to help delineate the types of people that will attend them.
One last point, if you are offended because you are a noob then you have some other issues to over come. This year I learned how to hand solder SMD's. I had only done SMD's with a hot plate in the past, but this year I learned how to do it with a soldering iron. I was a complete noob at it and it took me a couple of hours to get the hang of it. But after I figured out how to do it, and I became semi-proficient with the size of components that we were using I was able to start to show others how to do it, and also fix mistakes that people were making. My buddy this year is a skilled developer, but he had never picked a lock before. I don't think he would be offended by being called a noob at lock picking, but he probably would be offended if I called him a noob at programming. We all start somewhere and that somewhere is noob. If you don't want to be called a noob then hone your skills and develop the knowledge to elevate yourself, rather than bitching about it.
Comment