Publishing Exploit Code Ruled Illegal In France
Dexter writes "A French Court has condemned the security researcher Guillame Tena for publishing a security vulnerability in the Viguard anti-virus software of Tegam. This ruling makes the publication of security vulnerabilities and their proof of concept through reverse engneering illegal in France."
What good is it to publish software vulnerability, especially on closed source products?
If one really wants to help, isn't it better to inform the software maker? If the latter couldn't care less, maybe one shouldn't care more?
However, as the friendly article pointed out, the fine was for a copyright infringement charge, so it looks like you can still publish a vulnerability as long as it is subtle enough.
Rock that crushes, Paper & Scissors that don't matter.
You may notice the article has no details.
I did a Google News Search and found this one which is much better.
Also, the guys own website.
Hope this helps.
- Jax
There are top notch security experts in France, specifically the folks at K-Otik http://www.k-otik.com/
I'm a security consultant and I look to these folks as a source of reputable information. I spent a LOT of time on their site when Microsoft was trying to deal with the fallout of the MSO3-026 vulnerability which begat the MSBlaster worm. I even got the source code for blaster from the K-Otik crew.
This is going to have huge ramifications if it is interpreted as described here.
Good security is based upon reality and common sense. Common sense is a function of having common knowledge.