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

[Kevin_Catlin@xxxxxxxxxxxx]

     Two wrongs don't make a right.  Take 'em to court and get a temporary 
     injunction to require SSA to issue a key that will at least get you 
     through the expected period of litigation.  I think you would have the 
     grounds to do so, but if your user count has gone over the licensed 
     users, you will be on more shaky ground.
     
     Also, anyone who chooses to stay on old technology does so at their 
     own peril.  It's not your legal right to be able to survive on it 
     indefinitely, in particular if you choose to sever ties with the 
     vendor by cancelling/not renewing your support contract.  Sometimes 
     when you roll the dice, it comes up "snake eyes".


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


Well, this one brought me out of the woodwork.
     
> This list is _NOT_ for the purpose of avoiding license
> fees.  Besides, if you haven't figured it out in eight years, you don't 
> _deserve_ to...
     
I don't think the purpose of "breaking" the security code is necessarily a 
question of avoiding license fees -nor- is it necessarily a question of the 
viability of SSA.  Let me set up a hypothetical situation for you:
     
Customer is a long time client of SSA.  Customer has decided to stay on 
405CD due to the hardware requirements and horror stories of those running 
V6.  SSA states it will no longer support 405CD.  Customer drops OGS seeing 
no need for it if the software will no longer be fixed or upgraded. 
Customer moves to a RISC machine from a CISC.  SSA denies a permanent
software key for the new machine without an OGS contract.  Terms of the BPCS 
contract were that the software was licensed for a user count -not- a 
machine processor level.  SSA refuses to budge from its position.
     
Now do you see a reason to break the code?  Now do you see a reason why 
after 8 years it hasn't really been contemplated as to how to break it?
     
No, I'm not the original poster of the question, but it is one that I've 
thought about asking for a while now.
     
Bill
     
     
__________________________________________________ 
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger. 
http://im.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 0033114C; Wed, 11 Oct 2000 11:02:00 -0400
Received: from mail-ewr-3.pilot.net (localhost [127.0.0.1]) by
unknown-27-151.cytec.com. with ESMTP id KAA10233; Wed, 11 Oct 2000 10:58:56
-0400 (EDT)
Received: from uucphost.mcs.net (Kitten2.mcs.com [192.160.127.90]) by
mail-ewr-3.pilot.net with ESMTP id KAA17312; Wed, 11 Oct 2000 10:58:55 -0400
(EDT)
Received: (from 66@localhost)
        by uucphost.mcs.net (8.9.3/8.9.3) with UUCP id JAA10028;
        Wed, 11 Oct 2000 09:56:35 -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 JAA30370
        for bpcs-l-outgoing; Wed, 11 Oct 2000 09:00:06 -0500
Received: (from uucp@localhost)
        by linux.midrange.com (8.9.3/8.8.7) with UUCP id JAA30365
        for bpcs-l@midrange.com; Wed, 11 Oct 2000 09:00:04 -0500
Received: from smtp2.mail.yahoo.com (smtp2.mail.yahoo.com [128.11.68.32])
        by uucphost.mcs.net (8.9.3/8.9.3) with SMTP id IAA02032
        for <bpcs-l@midrange.com>; Wed, 11 Oct 2000 08:55:20 -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 13:55:14 -0000
X-Apparently-From: <brobins3d@yahoo.com>
Message-ID: <006201c0338a$c1e94e90$c60064c8@arlon.com>
From: "Bill" <brobins3d@yahoo.com>
To: <BPCS-L@midrange.com>
References: <47.1e756fa.271582dc@aol.com>
Subject: Re: Is it possible to crack the BPCS Key logic?  
Date: Wed, 11 Oct 2000 06:54:21 -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)