[dogma1138]

It doesn’t matter if it’s provable or not, most developers won’t risk it especially if they want to keep their jobs or be hireable.

If you review the content and publish say a blog post, even without legal repercussions it can impact your ability to be hired in the future since everything you do from that point can be tainted.

So if you do look you should keep it quite or publish it under a pen name that you can’t ever take credit for.

[ATsch]

My point was that even without anyone taking that risk, the information will spread.

Someone reads the code, mentions it to a friend, who adds it to a blog post, which gets cited in a wiki, which gets read by a developer unaware of the source. If the information is useful, it will end up getting spread.

[johnnyfaehell]

Say we use the Microsoft Windows code that got leaked, was anyone black listed for that?

Also, I would assume other processor companies hire people from other processor companies and everyone all wants the best, most of the basic knowledge would have already made it's way to AMD and other companies.

[dogma1138]

But that isn’t basic knowledge, if you work in firmware development, embedded, SOC design etc. and your employer or future employers might be competing against Intel in some market segment (which given the sheer amount of products Intel has isn’t an unlikely scenario) I would be very careful about admitting not to mention publishing content based on this leak.

If you work in a completely unrelated field then you don’t need to care as much.

[johnnyfaehell]

But if you've worked at Intel those should be part of your job for a majority of people and when they leave that knowledge goes to.

[gsich]

You can always say you reverse engineered it yourself. Hard to disprove.