[prev in list] [next in list] [prev in thread] [next in thread] 

List:       full-disclosure
Subject:    Re: [Full-Disclosure] The Trillian GPL violation allegations are confirmed false.
From:       Stefan Esser <s.esser () e-matters ! de>
Date:       2004-02-29 1:45:43
Message-ID: 20040229014543.GA11213 () php ! net
[Download RAW message or body]

Sean,

I do not know what code was shown to you. But if you have seen the real
code you are simply a liar.

It would have been okay if you have asked Eric to just double license the
code. He already said that he would give the code to the Trillian people.
But your claim is a fucking joke. The chances that you and Trillian thought
up the same code 1:1 is so minimal....

Everyone on this list who will look into the issue will not believe you.
Just one example: why in hell should someone choose 64 byte for the 
keysize? The keys are decimal numbers. Even on 64 bit machines this are
around 32 chars or so. So why in hell did you both choose coincidently
64 byte... Just one of many examples.

And using atoi() instead of strtol() is still derived code.

Ohh and btw: your parsers are not efficient and it would be trivial to
write a far more efficient one with the use of memchr()

Stefan Esser

-- 

--------------------------------------------------------------------------
 Stefan Esser                                        s.esser@e-matters.de
 e-matters Security                         http://security.e-matters.de/

 GPG-Key                gpg --keyserver pgp.mit.edu --recv-key 0xCF6CAE69 
 Key fingerprint       B418 B290 ACC0 C8E5 8292  8B72 D6B0 7704 CF6C AE69
--------------------------------------------------------------------------
 Did I help you? Consider a gift:            http://wishlist.suspekt.org/
--------------------------------------------------------------------------

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.netsys.com/full-disclosure-charter.html
[prev in list] [next in list] [prev in thread] [next in thread]