Re: Microsoft Explorer security hole (fwd) MSoft's reply...

Actually I think its thier lack of foreseeing how a produbt can and will be
used.  Problems throughout thier line of products show this off.
Most of thier products are a creation of Microsoft anyway, they've stolen,
borrowed, purchased or purchased the company to obtain their products, then
added features upon features so they can market the hell out of it
to become #1 in market share. Many cases they've taken a reliable product
and made it less than reliable.
  I don't understand why people continue to support Microsoft they way 
they do!
  
   Ponder the thought of Microsoft buying up every web server/broswer
  company in the first year or two of the WEB?  Would it have made it where
  it is today?  
  Ponder the thought of Micorosft having ultimate control over the
  IETF

>In my experience, one of Microsoft's main problems when it comes to security
>has been its developers and program/product managers don't think like "bad
>guys" when it comes to design and subsequent exploits and holes.
>Unfortunately, the user is the ultimate loser.
>
>Joel
>
>BTW - The paranoid side of me wouldn't be surprised to see PC
>"espionage-enabled" viruses and trojans within the next few years.  Their
>main purpose would be to either disable or patch various security features
>for later attacks, or directly snatch information off of hard drives and
>send it out over the Net.  I know of a few lab projects of a similar nature,
>that were very easy to implement.
>



BTW: When is this list/listserver going to convert the reply-to fields to 
     point to cypherpunks@toad.com?



--
------------------------------------------
There are no facts, only interpretations.

I always wanted to be somebody,

At 2:57 AM -0000 8/28/96, SCN User wrote:
> BTW: When is this list/listserver going to convert the reply-to fields to 
>      point to cypherpunks@toad.com?

Never.

We don't do it because of reply-to loops.

Only idiots, or charitably, those with very low traffic, run their mail lists any other way.

Accidentally sending private e-mail to the list is bad enough without bringing the listserver to its knees...

Cheers,
Bob Hettinga
([probationary] former idiot)

-----------------
Robert Hettinga (rah@shipwright.com)
e$, 44 Farquhar Street, Boston, MA 02131 USA
"'Bart Bucks' are not legal tender."
                -- Punishment, 100 times on a chalkboard,
                       for Bart Simpson
The e$ Home Page: http://www.vmeng.com/rah/

Date: Tue, 27 Aug 1996 19:57:53 -0700 (PDT)
    From: SCN User <bf578@scn.org>
    
    BTW: When is this list/listserver going to convert the reply-to fields to 
         point to cypherpunks@toad.com?

Hopefully never.  It's the wrong way for a distribution list to work.

If you personally want replies to just go to the list, then you can
add a reply-to field in your message.  I prefer when people do a
standard `reply all' to reply to me and CC the recipients of my
message.  In that way, I can file messages to a list in a folder while
treating those that are explicitly specially -- I might want to see
them sooner so as to reply sooner.

The distribution list should just distribute messages.  The sender
should determine the addressing.

			Rick