[THIN] Re: Flex Profiles Kit - License Infringement?

  • From: "Lilley, Brian" <brian.lilley@xxxxxxxx>
  • To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
  • Date: Thu, 24 Nov 2005 11:33:27 -0000

well, I think the argument MS would have is that you must have reverse 
engineered machinecode to understand where one needed to poke the bytes??!  
unless of course, the dudes at Log*in are very very lucky. in which case I am 
going to ask them for some Lotto numbers.

-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
Behalf Of Tom Howarth
Sent: 24 November 2005 11:29
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Flex Profiles Kit - License Infringement?


I'm not a Coder but my veiw s

on reverse engineering is to faithfully imitate a product with the
express desire to replicate all functions and pass it off as your own
work. (not the case here as the file is only modified and all licenses
are references and noted)

Decomplication - surely this means returning the product to raw code. 
(definaltely not the case here)

Disassembly ( I thought that was only done to Johny 5) ;-)

how different is this modifcation by a HEX editor to what you can do
with Spy++ etc


On 24/11/05, Andrew Wood <andrew.wood@xxxxxxxxxxxxxxxx> wrote:
> Well - that'd be my line - and the closest I could see was
>
> 4.      LIMITATIONS ON REVERSE ENGINEERING, DECOMPILATION, AND DISASSEMBLY.
> You may not reverse engineer, decompile, or disassemble the Software, except
> and only to the extent that such activity is expressly permitted by
> applicable law notwithstanding this limitation.
>
> But, I'd argue that the modification with a hex editor in the context of the
> flex tool's use is neither reverse engineering, decompliation or
> disassembly...
>
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
> Of Tom Howarth
> Sent: 24 November 2005 10:50
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Flex Profiles Kit - License Infringement?
>
> My thoughts are that the ORK is a free download and therefore distributable,
> however the issue is whether the editing of the file with the HEX editor
> causes an infringment. But to be honest I have not read the EULA in detail.
>
> On 24/11/05, Andrew Wood <andrew.wood@xxxxxxxxxxxxxxxx> wrote:
> >
> >
> > The flex profile kit utilises code from the Office Resource kit -
> > which is modified using a hex editor - all fine and dandy open and
> > above board and its mentioned in the doco.
> >
> > Theres been an interesting debate today in the office as to whether
> > that makes the deployment of the tool legal - as the kit ultimately
> > relies on a modified binary.
> >
> > Anyone know/have thoughts on this?
> >
> > Tia.
> >
> > ----------------------------------
> > Andrew Wood
> > Sunderland
> > United Kingdom
> >
> >
>
>
> --
> Tom at home
> ************************************************
> For Archives, RSS, to Unsubscribe, Subscribe or set Digest or Vacation mode
> use the below link:
> //www.freelists.org/list/thin
> ************************************************
>
> ************************************************
> For Archives, RSS, to Unsubscribe, Subscribe or
> set Digest or Vacation mode use the below link:
> //www.freelists.org/list/thin
> ************************************************
>


--
Tom at home
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************

==============================================================================
Please access the attached hyperlink for an important electronic communications 
disclaimer: 

http://www.csfb.com/legal_terms/disclaimer_external_email.shtml

==============================================================================

************************************************
For Archives, RSS, to Unsubscribe, Subscribe or 
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************

Other related posts: