Reply to thread

Message

<blockquote data-quote="ncage" data-source="post: 752346" data-attributes="member: 62363">You can really say that about a lot of things: Guns, knives, lawn mowers,&nbsp; cars , motorcycles, circular saws, ect... All you can do is throw up all kind of warnings and let people know if they go further they are doing so at their risk. I bet a lot of researching started out of curiosity. If they couldn&#039;t have access to such samples where do you think they would be now? Do you think only people who work at AV vendors should have access to such samples? I think trying to protect people from themselves is a mistake. Yes there will be those yahoos who mess their system up but then there will be those that add to the security community. A good example is i&#039;m a developer by trade. There are a lot of people out there programming sites with all kinds of vulnerabilities because they don&#039;t know what the heck they are doing: SQL Injection, cross site scripting attacks, don&#039;t correctly hash password in their database, ect... But do i think depriving them of products to make sites is a solution? Absolutely not. I remember shaking my head when the developers of ashley madison correctly bcyrpt passwords but in the end one of the developers thought it was to slow so he stored md5 passwords right beside it.</blockquote>

[QUOTE="ncage, post: 752346, member: 62363"] You can really say that about a lot of things: Guns, knives, lawn mowers, cars , motorcycles, circular saws, ect... All you can do is throw up all kind of warnings and let people know if they go further they are doing so at their risk. I bet a lot of researching started out of curiosity. If they couldn't have access to such samples where do you think they would be now? Do you think only people who work at AV vendors should have access to such samples? I think trying to protect people from themselves is a mistake. Yes there will be those yahoos who mess their system up but then there will be those that add to the security community. A good example is i'm a developer by trade. There are a lot of people out there programming sites with all kinds of vulnerabilities because they don't know what the heck they are doing: SQL Injection, cross site scripting attacks, don't correctly hash password in their database, ect... But do i think depriving them of products to make sites is a solution? Absolutely not. I remember shaking my head when the developers of ashley madison correctly bcyrpt passwords but in the end one of the developers thought it was to slow so he stored md5 passwords right beside it. [/QUOTE]

Verification