﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Ayende Rahien commented on Patents, Trademarks and Copyright, Urgh!</title><description>Mark,
  
At the same time, working from x86 assembler is "having the code", no?
  
  
I doesn't work that way. 
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment7</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment7</guid><pubDate>Wed, 10 Oct 2007 17:50:48 GMT</pubDate></item><item><title>Mark B commented on Patents, Trademarks and Copyright, Urgh!</title><description>I have to challenge the contention that using Reflector is reverse engineering. I think it is translation, from IL to (Pick your .NET lang here). You *do* have the actual source code the CLR will compile to byte-code. I don't see the fact that you are using a mnemonic aid to convert from one language construct to another mitigating your knowledge of how the source in question works. 
  
  
On the other hand, if you were to take the published specs, and poke known values at the functions and record the responses to validate the specs / document spec violations &amp; undocumented functions, and then build your own function to reproduce the same effects, then *that* would be reverse engineering. (Gee, sound familiar for the Mono team?)
  
  
Possibly working from the byte code backward as well.
  
  
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment6</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment6</guid><pubDate>Wed, 10 Oct 2007 15:42:30 GMT</pubDate></item><item><title>Adi commented on Patents, Trademarks and Copyright, Urgh!</title><description>The beauty of Microsoft's move is that is doesn't matter if you read the source code or not:
  
http://dotmad.blogspot.com/2007/10/tainted-if-you-do-tainted-if-you-dont.html
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment5</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment5</guid><pubDate>Sat, 06 Oct 2007 23:47:25 GMT</pubDate></item><item><title>Frans Bouma commented on Patents, Trademarks and Copyright, Urgh!</title><description>Jeremy: so, MS is stupid because they force their employees not to look at any OSS code which is GPL-ed ? If it's not such a big deal to look at code, why bother?
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment4</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment4</guid><pubDate>Sat, 06 Oct 2007 09:23:56 GMT</pubDate></item><item><title>Ayende Rahien commented on Patents, Trademarks and Copyright, Urgh!</title><description>&gt; You either violate their copyright by producing a work of enough similarity, or you don't. 
  
  
You seem to be confusing the case of a patent vs. copyright.
  
If you didn't have access to the source (reflector may count as having access to the source, not sure), you are NOT violating copyright even if you produce 1:1 result with what they have, right down to the comments and spacing.
  
  
What you are talking about are patents, where you can be violating that regardless of how you got there.
  
  
&gt; I challenge anyone arguing against viewing the source to also argue against using Reflector,
  
  
Different semantics, one is having access to the code, the second is reverse engineering it.
  
As I said, this is a legal distinction, but an important one.
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment3</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment3</guid><pubDate>Fri, 05 Oct 2007 17:07:43 GMT</pubDate></item><item><title>Tanner Burson commented on Patents, Trademarks and Copyright, Urgh!</title><description>The real problem with looking at the MS source isn't as much the fear of copyright violation (as long as you don't copy/paste) as it's the fear of being tainted by a patented method.  If you've never seen the source, you can at least claim to have independently implemented the same process.  This doesn't entirely patent-proof yourself, but it gives you a leg to stand on.
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment2</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment2</guid><pubDate>Fri, 05 Oct 2007 16:34:04 GMT</pubDate></item><item><title>Jeremy Gray commented on Patents, Trademarks and Copyright, Urgh!</title><description>"Even assuming that you did not copy &amp; paste the code from there, it can still be said that you are in violation of their copyright because you have residual knowledge from looking at the code."
  
  
You have some interesting laws in your country, because that statement certainly doesn'y apply in numerous other places. You can't violate their copyright just by looking at their code. You can only violate their copyright by reproducing the copyrighted work, in whole, in part, or even with just enough similarity, in a manner that is not covered by any type of fair use or appropriate license. You either violate their copyright by producing a work of enough similarity, or you don't. It is as simple as that. How you produced the work doesn't matter. Whether or not you read the source doesn't matter. Whether or not you looked at Reflector doesn't matter.
  
  
I challenge anyone arguing against viewing the source to also argue against using Reflector, as use of either puts you in just as equal a position to be in violation of a copyright. Which, incidentally, is in no better or worse position to be in violation of a copyright than if you _neither_ used Reflector or viewed the source. Get your arguments aligned or be labeled a hypocrite.
</description><link>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment1</link><guid>http://ayende.com/2835/patents-trademarks-and-copyright-urgh#comment1</guid><pubDate>Fri, 05 Oct 2007 15:53:55 GMT</pubDate></item></channel></rss>