bugtraq - Re: [VulnWatch] Details of Sybase ASE bugs withheld

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20050322153851.2edfef14.infamous41md@hotpop.com>
Date: Tue, 22 Mar 2005 15:38:51 -0500
From: sean <infamous41md@...pop.com>
To: bugtraq@...urityfocus.com
Subject: Re: [VulnWatch] Details of Sybase ASE bugs withheld


Another question, how can one prove that it was found by disassembling the code?
What if it were found by brute force testing?  I can't imagine that a company
would prohibit the user from testing the functionality of a product they sell? A
friend of mine told me this sort of legal piracy was commonplace - have there
ever been any actual legal proceedings in a similar situation?  I'm not finding
anything good on google.


On Tue, 22 Mar 2005 12:12:19 -0500
"Marchand, Tom" <Tom.Marchand@...sfl.com> wrote:

> If the bug was found by disassembling Sybase's code then Sybase probably does
> have a legal position to do this.  I haven't read Sybase's EULA but most have
> a provision prohibiting reverse engineering of code.
> 
> 
> -----Original Message-----
> From:	sean [mailto:infamous41md@...pop.com]
> Sent:	Mon 3/21/2005 5:54 PM
> To:	bugtraq@...urityfocus.com
> Cc:	
> Subject:	Re: [VulnWatch] Details of Sybase ASE bugs withheld
> 
> On Mon, 21 Mar 2005 21:50:22 -0000
> "David Litchfield" <davidl@...software.com> wrote:
> 
> 
> Pardon my ignorance, but on what legal grounds can they do anything if you
> tell them f' off and release anyway?  This is absolute insanity.  Who do they
> think they are?  They don't own your intellectual property.  I'd call their
> bluff if I were you, but then again I'm not ;)
> 
> -- 
> [ sean ]
> 
> 
> 
> 
> 
> 
> 
> Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate
> companies are not responsible for errors or omissions in this e-mail message.
> Any personal comments made in this e-mail do not reflect the views of Blue
> Cross Blue Shield of Florida, Inc.  The information contained in this document
> may be confidential and intended solely for the use of the individual or
> entity to whom it is addressed.  This document may contain material that is
> privileged or protected from disclosure under applicable law.  If you are not
> the intended recipient or the individual responsible for delivering to the
> intended recipient, please (1) be advised that any use, dissemination,
> forwarding, or copying of this document IS STRICTLY PROHIBITED; and (2) notify
> sender immediately by telephone and destroy the document. THANK YOU.
> 
> 


-- 
[ sean ]