Re[2]: Is it possible to crack the BPCS Key logic?

[Kevin_Catlin@xxxxxxxxxxxx]

     Bill
     
     My assumption is that you are an IT professional and not an 
     intellectual property lawyer.  I think you're talking "out of school" 
     here and suggest you leave such opinions to the legal experts.
     
     Further, if your license explicitly restricts you to operate the 
     software on a particular AS/400, then that defines your rights in no 
     uncertain terms.  If you don't like the terms of your license, then 
     shame on you for signing it.
     
     My opinion on this discussion is that it is frivolous and that we 
     should move on to matters of greater importance.
     
     Kevin


______________________________ Reply Separator _________________________________
Subject: Re: Is it possible to crack the BPCS Key logic?  
Author:  BPCS-L@midrange.com at Internet
Date:    10/11/2000 11:05 AM


Elsberry,
     
> Breaking a software key logic is a 'moral' issue.
     
No it's not, not on it's own.  Breaking the logic in order to get something 
not paid for would be.
     
>  Stealing, no matter what the motive, is still stealing.
     
Agreed.  But we haven't been talking about stealing have we?  We've been 
talking about overriding the security check.
     
>  In the 10 years that I have worked with SSA,
> and 5 for them, I have never seen them be so unreasonable as to deny a
> permanent key to someone just because they won't pay on-going support for 
a
> non-supported older version.
     
Do you still have contacts there?  Call them up and ask them their current 
standing on this issue, and make sure you talk to the holders of the keys. 
If by chance you get the answer that goes against what I have proposed, ask 
them if they ever held that stance this year.  If they reply it has never 
been their policy to withhold the key, then they are lying.  If they reply 
that their current policy is as I have represented it, what is your stance 
then?
     
> If you have to rationalize why you're doing something like this, it is 
> probably to appease your own conscience and not to support some flimzy 
> business reason.
     
Hmm, I would think being unable to operate software that was legally 
licensed would not be a flimzy business reason; maybe your business is 
different.
     
Bill
     
     
_________________________________________________________ 
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
     
+---
| This is the BPCS Users Mailing List!
| To submit a new message, send your mail to BPCS-L@midrange.com. 
| To subscribe to this list send email to BPCS-L-SUB@midrange.com.
| To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. 
| Questions should be directed to the list owner: dasmussen@aol.com
+---
Received: from unknown-27-151.cytec.com. ([204.48.27.204]) by stnt01.cytec.com
with SMTP
  (IMA Internet Exchange 3.14) id 0033197F; Wed, 11 Oct 2000 15:05:46 -0400
Received: from mail02-ewr.pilot.net (localhost [127.0.0.1]) by
unknown-27-151.cytec.com. with ESMTP id PAA19194; Wed, 11 Oct 2000 15:02:41
-0400 (EDT)
Received: from uucphost.mcs.net (Kitten2.mcs.com [192.160.127.90]) by
mail02-ewr.pilot.net with ESMTP id PAA27389; Wed, 11 Oct 2000 15:02:40 -0400
(EDT)
Received: (from 66@localhost)
        by uucphost.mcs.net (8.9.3/8.9.3) with UUCP id OAA46725;
        Wed, 11 Oct 2000 14:01:55 -0500 (CDT)
        (envelope-from bpcs-l-owner)
X-Authentication-Warning: Kitten.mcs.net: 66 set sender to bpcs-l-owner using -f
Received: (from majordom@localhost)
        by linux.midrange.com (8.9.3/8.8.7) id NAA02744
        for bpcs-l-outgoing; Wed, 11 Oct 2000 13:30:07 -0500
Received: (from uucp@localhost)
        by linux.midrange.com (8.9.3/8.8.7) with UUCP id NAA02729
        for bpcs-l@midrange.com; Wed, 11 Oct 2000 13:30:05 -0500
Received: from smtp1.mail.yahoo.com (smtp1.mail.yahoo.com [128.11.69.60])
        by uucphost.mcs.net (8.9.3/8.9.3) with SMTP id NAA42603
        for <bpcs-l@midrange.com>; Wed, 11 Oct 2000 13:28:27 -0500 (CDT)
        (envelope-from brobins3d@yahoo.com)
Received: from unknown (HELO mismanager) (12.127.129.166)
  by smtp.mail.vip.suc.yahoo.com with SMTP; 11 Oct 2000 18:06:18 -0000
X-Apparently-From: <brobins3d@yahoo.com>
Message-ID: <029a01c033ad$d40b8f20$c60064c8@arlon.com>
From: "Bill" <brobins3d@yahoo.com>
To: <BPCS-L@midrange.com>
References: <4a.bfadec9.2715da45@aol.com>
Subject: Re: Is it possible to crack the BPCS Key logic?  
Date: Wed, 11 Oct 2000 11:05:24 -0700
MIME-Version: 1.0
Content-Type: text/plain;
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-bpcs-l@midrange.com
Precedence: bulk
Reply-To: BPCS-L@midrange.com
X-List-Name: BPCS Users Mailing List (BPCS-L@midrange.com)