juuso wrote:It`s up to you to use SamyGO or not to use it.
Of course it is. What I am trying to do here is improve this "reverse engineering community", but you will probably disagree that I am.
juuso wrote:I`m not going to explane every security gap what we`re using for this or another exploit. Why?
Because after publishing every detailed how-to, we`re getting it closed with upcoming (forced over otn or not) firmware upgrade.
You should understand why here isn`t so much details about hacks. Samsung is reading us.
That seems like the "security by obscurity" approach to me. For me real reverse engineering is something different (e.g.
http://events.ccc.de/congress/2010/Fahr ... 87.en.html, Slides, page 11+). Also, there is clearly no reason not to properly document vulnerabilities that have been already closed by Samsung. Yet I haven't seen anything like this on the wiki.
juuso wrote:If you need more detailed how to, start to reading forum and not those three topics you showed.
That doesn't make any sense to me. If the information is there, it should be organised so people who want to contribute can contribute easily and have a clear starting point. The reason is simple: if the information is there, Samsung will find it anyway, but a single person who would like to contribute will likely not find it.
juuso wrote:Especially if you just need NFS and Samba shares, look at SamyGO Extensions.
If you`re developer, then you can look at the SamyGO Extensions code and sure, related topics and wiki pages, whose links are referenced.
Of course I could do that, of course I could read code but then again I could probably even reverse engineer it myself (a bit) given enough time. The thing is ... some people would like to contribute to this project but do not have the time to reinvent all the wheels just to be able to contribute.