Re: UnixWare

cklausshadow.net

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Icarus Sparry: "Re: UnixWare"
• Previous message: Karyn Pichnarczyk: "HP"
• In reply to: Gene Spafford: "Re: UnixWare"
• Next in thread: Gene Spafford: "Re: UnixWare"

> 
> I've had several people tell me that HP has gotten better recently.  I
> would have mentioned them as good examples, except:
> 
> 1) I have not seen them make any security patch announcements to any
> of the established security-related newsgroups or mailing lists.

I see their bulletins on comp.security.unix all the time.  Not only
that, they have their own mailing list.  

	For security concerns, questions, or problems, you can contact:
        security-alerthp.com

I will append my FAQ to the end of message for more information.  

> 
> 2) HP does not have a member or liason in FIRST, nor have they had
> any presence at any of the incident response workshops.
> 

I do not see any major advantage of being in FIRST, other than for namesake.
I have e-mailed a couple FIRST contacts on a couple of occasions with dismal
response.  I have gotten more information from CERT about problems than some
FIRST contacts [if that says anything].  CERT does a good job in reporting
vulnerabilities to vendors and such, but I think Brad Powell (of Sun) was
suggesting starting a new organization that dealt with intrusions 
more specifically - along the lines of if any organization thats serious
about going after intruders could join and have a coherent effort to
stop this type of actions.  Maybe Brad could explain his idea more?

Anyways, my point is that just because a corporation is not in FIRST
make it not security conscience with its customers.    

> 3) I have read accounts of HP customers not being able to get security
> patches because they aren't paying for maintenance.
> 
> #3 may no longer be true; in any event, I have no direct experience
> with it so I can't say it was ever more than a misunderstanding.
> 

May no longer be true?  I am not even an HP customer and I can get their
patches.   Read my FAQ for more information.  I post it on the security
newsgroups monthly.

Subject: computer-security/vendor-contacts FAQ
Newsgroups: alt.security,comp.security.misc,comp.security.unix,comp.unix.admin,comp.answers,news.answers,alt.answers
Followup-To: poster
Reply-To: cklausshadow.net
Organization: ISS, Inc.
Distribution: world
Keywords: security contact vendor

Archive-name: computer-security/vendor-contacts 
Posting-frequency: monthly
Last-modified: 1994/04/04
Version: 1.4

"It [Vendor Security Contact FAQ] is the kind of thing that makes you look
good at work when your boss decides he's joe security and wants a patch (for
like rdist - duh!) yesterday..." -- Tim Scanlon, System Analyst



	Vendor Security Contacts: Reporting Vulnerabilities 
	and Obtaining New Patches


	The following FAQ is a list of security contacts to reach at various
vendors for reporting security vulnerabilities and obtaining new security
related patches.  
	With the rising number of people and hosts gaining access to the
Internet, the basic integrity of the Net needs to be maintained.  Many of
security incidents that happen on Internet could have been avoided by
installing security patches that are available by vendors.  It is important
to get the recent patches and ensure that your systems are configured
properly.  With intruders and their underground network having quick access
to security vulnerabilities, it is important that administrators have
security information available and not rely on just One organization.

	Here are the security contacts that information is available for:
A/UX, Cray, Dec, HP, IBM, Next, SCO, SGI, and Sun.  

	When reporting a new security bug, try to be as specific as
possible about how to reproduce it, which OS release (uname -a), and any
other release numbers of software that are involved.




A/UX

Contact information for A/UX as follows:

Send security related information to the following people:
	Erik E. Fair fairapple.com
	and CC: staffapple.com

	antonioaux.support.apple.com (A/UX support person).




Cray

Contact information for Cray as follows:

Cray Research customers should first direct questions and concerns to on-site
support personnel (if provided by their service contract).  Other contacts
should be made through the

  Technical Service Center
  Cray Research, Inc.
  655F Lone Oak Drive
  Eagan MN 55121 
  USA

  tel. +1-612-683-5600
  email. supportcray.com



Dec

Contact information for Dec as follows:

Send security related information to the following people:

Reid, Brian K.  (BKR)  reidPA.DEC.COM (415) 688-1307
Peck, Joseph R.  (JRP50)  peckPA.DEC.COM (415) 688-1341
Rich Boren rich.borencxo.mts.dec.com (719) 592-4689
        
Security patches are issued by Customer Support Centers.




HP

Contact information for HP as follows:

        
	For security concerns, questions, or problems, you can contact:
        
        security-alerthp.com

	
Obtaining Patches:

The HP SupportLine mail service is available to anyone who can send electronic
mail via the Internet.

If you have access to the Internet or can send electronic mail via an Internet
mail forwarder, you can use the HP SupportLine mail service.


********************************************************************************
*                How do I access the HP SupportLine mail service?              *
********************************************************************************


o  To obtain a copy of the HP SupportLine mail service user's guide, send the
following in the TEXT PORTION OF THE MESSAGE to supportsupport.mayfield.hp.com
(no Subject is required):

   send guide

Note: The HP SupportLine mail service user's guide is formatted using nroff. If
you would like an ASCII version of the user's guide or if you are utilizing a
non-UNIX mail reader, replace "send guide" with "send guide.txt".

o  Once your request is received, the HP SupportLine mail service will send you
a copy of the user's guide.

o  If you encounter any problems using the HP SupportLine mail service, report
them to support-feedbacksupport.mayfield.hp.com

********************************************************************************
*                     What mailing lists are available?                        *
********************************************************************************

The following is a list of all mailing lists available via the HP SupportLine
mail service:

mailing_list_name    Description
-----------------    -----------
hpux_all_patch       weekly digest of all new hp-ux patches
hpux_300_patch       weekly digest of all new hp-ux s300_400 patches
hpux_700_patch       weekly digest of all new hp-ux s700 patches
hpux_800_patch       weekly digest of all new hp-ux s800 patches

dom_all_patch        weekly digest of all new domain patches
dom_m68k_patch       weekly digest of all new domain m68k patches
dom_a88k_patch       weekly digest of all new domain a88k patches

technical_tips       weekly digest of new HP Technical Tips
existing_news        monthly digest of new Existing Product News
general_news         monthly digest of new HP General News
new_products         monthly digest of new HP Product Information
security_info        Latest digest of new HP Security Bulletins
security_info_list   Index of available HP Security Bulletins


o  To subscribe to an  HP SupportLine mail service mailing list, send the
following in the TEXT PORTION OF THE MESSAGE to supportsupport.mayfield.hp.com
(no Subject is required):

   subscribe mailing_list_name  (i.e. subscribe hpux_all_patch)

On a weekly or monthly basis, the HP SupportLine mail service will create and
distribute the requested mailing_list_name digest directly to your mailbox.


********************************************************************************
*                     How do i get a Patch from HP?                            *
********************************************************************************

If you know the name of the patch needed, Email to:

supportsupport.mayfield.hp.com 

with the body of the message stated as:

"send PHKL_9999"

The patch will automatically be mailed back to you with a mail unpacker 
script (patch_maker).

If you just want the README for the patch, Email a message to:

supportsupport.mayfield.hp.com

with the body of the message stated as:

"send doc PHKL_9999"

The patch README will be mailed back to you.

       
	Response Center Customers: 1-800-633-3600
        BasicLine Customers:  1-415-691-3888
        Also try email to bkelleycup.hp.com

        Outside the U.S., contact your local Response Center.




IBM

Contact information for IBM as follows:


  IBM support  1-800 237-5511
  Email to servicesaustin.ibm.com 
       

  Send security related information to Nick Trio (nrtwatson.ibm.com,
a.k.a. postmasteribm.com) Unix person on IBM's Computer Emergency Response
Team) and Alan Fedeli (fedelivnet.ibm.com).

  There are some security patches on anonymous FTP software.watson.ibm.com
in pub/aix3 for AIX.

Security patches are issued through your IBM sales office.

Some of the following patches that are available are:
Patch: ix22628   Fix: Corrects TFTP from allowing people to grab /etc/passwd.



Next

Contact information for Next as follows:

Technical Support at "ask_nextnext.com"   
Phone number: 800.848.6398.

Address is 900 Chesapeake Drive; Redwood City, CA; 94063.



SCO

Contact information for The Santa Cruz Operation (SCO):

Send security related information to:

  security-alertsco.com

Security patches are issued on an as-needed basis and will be available
at ftp.sco.com and its mirrors.

When submitting information about a security problem, please include
output of the following commands:

  uname -X
  swconfig
  hwconfig -h        (if hardware-related)

and as much detail about the problem as you can muster.



SGI

Contact information for SGI as follows:
 
Send security related information to:

  security-alertsgi.com

If there is no response, try Dave Olson olsonanchor.esd.sgi.com.

	Support line 1-800-800-4SGI and ask what patches are available.
	
	There are some security patches on anonymous FTP sgi.com in
directory sgi/IRIX4.0 (or 5.0 if the system is IRIX5).

Security patches are issued through your SGI sales office.



Sun

Contact information for Sun as follows:

  email: security-alertsun.com
  phone: 415-688-9081
  Fax:   415-688-9101

postal:
  Sun Security Coordinator
  MS MPK2-04
  2550 Garcia Avenue
  Mountain View, CA 94043-1100

Sun produces "Sun Security Bulletin" - ask security coordinator for it.


Other Resources

   The CERT (Computer Emergency Response Team) advisory mailing list.  Send
e-mail to certcert.org, and ask to be placed on their mailing list.  Past
advisories and other information related to computer security are available
for anonymous FTP from cert.org (192.88.209.5).

   The CIAC (Computer Incident Advisory Capability) of DoE.  To report a
vulnerability, call CIAC at (510) 422-8193 or send e-mail to ciacllnl.gov.
Previous CIAC bulletins and other information is available via anonymous
ftp from irbis.llnl.gov (ip address 128.115.19.60).  


Standard Form From CERT

Here is the form CERT provides for reporting new vulnerabilities found
in Unix platforms.

			CERT Coordination Center
		Product Vulnerability Reporting Form


			 Reporter Information

Reporter name			: 
Reporter e-mail			: 
Reporter phone / fax		:
Reporter affiliation and address: 

Reported to vendor: Y/N
	Date of report		: 
	Vendor contact name	: 
	Vendor contact phone	:
	Vendor contact e-mail	: 
	Vendor reference number	: 
		

===============================================================================
			     Policy Info

Reporter Considerations
	Pass name to vendor?	: 
	Use name in advisory?	: 

Special considerations (e.g. restrictions on dissemination): 

===============================================================================
			    Technical Info

Vulnerability number (after assigned by CERT)	: 

Problem Description: 

Impact: 

Currently being exploited?	: Y/N

Exploitation: 

Systems and/or configurations vulnerable
	System		: 
	OS version	: 
	Verified/Guessed: 

Workarounds and/or fixes: 

Problem Analysis: 

Source code, logs, or other supporting technical info: 



Acknowledgements

Thanks Dave Millar for helping provide a portion of the information.


Copyright

This paper is Copyright (c) 1994 by Christopher Klaus

	Permission is hereby granted to give away free copies.  You may 
distribute, transfer, or spread this paper.  You may not to pretend that
you wrote it.  This copyright notice must be maintained in any copy made.  


Disclaimer

	The information within this paper may change without notice. Use of
this information constitutes acceptance for use in an AS IS condition.
There are NO warranties with regard to this information. In no event shall
the author be liable for any damages whatsoever arising out of or in
connection with the use or spread of this information.  Any use of this
information is at the user's own risk.



Address of Author

	Please send suggestions, updates, and comments to:	
 
	Christopher Klaus <cklausshadow.net>





-- 
Christopher William Klaus  Email: cklausshadow.net  Author:Inet Sec. Scanner
2209 Summit Place Drive,Dunwoody, GA 30350-2430. (404)998-5871.

• Next message: Icarus Sparry: "Re: UnixWare"
• Previous message: Karyn Pichnarczyk: "HP"
• In reply to: Gene Spafford: "Re: UnixWare"
• Next in thread: Gene Spafford: "Re: UnixWare"