Re: Hypothesis -- Mr. Jeff Williams is a Teenager.

[Michael Dillon <michael@memra.com>]

On Sun, 29 Dec 1996, Jeff Williams wrote:

> > Well, so far the private eye reports allege that you used to work
> > in sales for a Seattle computer store and this past month you
> > hightailed it to Dallas and are now living in a hotel there.
> 
>   You need to hare a more compatant private eye.  I have never worked
> in sales in my life.  Never worked in Seattle or ever been there. 

Then please explain why you have the URL for this Seattle
computer retailler in your sig in this posting that you made to the
ietf-tls mailing list last month...

There are some further comments after the included message.

------------included message------------------
To: marcvh@aventail.com (Marc VanHeyningen) 
Subject: Re: Closing on shared-key authentication 
>From: Jeff Williams <jwkckid1@ix.netcom.com> 
Date: Fri, 11 Oct 1996 15:40:23 -0500 
Cc: ietf-tls@w3.org 
Message-Id: <1.5.4.16.19961011204023.092702b2@popd.ix.netcom.com> 
X-Mailer: Windows Eudora Light Version 1.5.4 (16) 
X-Sender: jwkckid1@popd.ix.netcom.com 

Mark,

  Please read below your comments.

At 11:39 AM 10/11/96 -0700, you wrote:
>> No, you should certainly do something more than just send the password
>> encrypted.  You should avoid sending the password at all, encrypted or
>> otherwise.  Some sort of challenge/response mechanism would be
>> appropriate, but you are protected from eavesdroppers if you encrypt
>> the data.
>
>True.  I'm clearly misunderstanding you then.  You said previously:
>
>>There is no need to add a mechanism
>>to TLS when all existing protocols already have a password mechanims.
>
>I assumed the password mechanisms that you meant there were
>cleartext ones, not more sophisticated ones based on challenge-response
>or keyed hashes or anything else.  Was I wrong?
>
>I believe there is a need to add a mechanism to TLS because, while all
>existing protocols have password mechanisms, they're lousy ones.

  Here here!  I agree. The current password mechanism is definatly flawed
or is te easely accessed.  And chalange/response mechanism might also be 
included as well as an option or feature.

Reguards,
 
>
>- Marc
>
>
>
>
Jeffrey A. Williams
SR.Internet Network Eng. 
CEO., IEG., INC.,  Representing PDS .Ltd.
Web: http://www.pds-link.com 
Phone: 214-793-7445 (Direct Line)
Director of Network Eng. and Development IEG. INC.
-----end of included message-------


>   Keep looking.  We have development centers in three states, and 
> two countries.  We have ongoing relationships/partnerships with
> over 17 other software development companies.  Our main line of
> buisness is in network information managment.  We have been published
> in most major nwespapers in the us and several in europe.  Money mag
> did two articles on us in the past 3 years.  We are the 5th largest
> Employee owned, privatly held company in the world in terms of 
> revinue.

So, you are the CEO of this company and yet you cannot give out anything
other than the vaguest of references. Start by naming the 3 states and
two countries. Then quote the month and year of the Money mag articles.
Name the 17 partner companies and give the name, phone number and email
address of a contact in those companies who can verify that you are who
you say you are.

> > Of course the private eyes could be wrong. In the interests of full
> > public disclosure why don't you just tell us who you are.

>   Well in this case, they are not very accurate, let's put it that way.

You didn't answer the question. Who are you? 


Michael Dillon                   -               Internet & ISP Consulting
Memra Software Inc.              -                  Fax: +1-604-546-3049
http://www.memra.com             -               E-mail: michael@memra.com