HP3000-L Archives

March 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Isaac Blake <[log in to unmask]>
Reply To:
Date:
Mon, 27 Mar 1995 08:26:23 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (23 lines)
Item Subject: Message text
> IMHO Joe was under the impression that Isaac was saying that if SM's
> were told privately by HP, they would discuss it on HP3000-L.  Again
> IMHO, Isaac was saying HP3000-L should not be the notification means.
>
> IMNSHO HP should publicly admit a problem exists, privately disclose
> details of the problem (including proposed solutions) to customers,
> and let the customer choose what (if anything) to do.  And in my
> opinion, the solution should NOT require an MPE upgrade.  If it does,
> HP should pay for non-prime time RC support if the customer's normal
> operations would suffer doing the upgrade in prime time.
 
Interesting points Tony!!!  See my reply regarding the first paragraph...
 
Regarding the second, I'll ask the same question (or close to it) I posted to
Joe.  What will be your response to a site who has their security breeched due
to the disclosure of this information???  Secondly, how would you defend the
actions of HP providing this information, and for us demanding this
information???
 
Regards,
/isaac

ATOM RSS1 RSS2