 |
 |
Articles / TULARC / Security / Vendor Security Contacts / |  |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
   |
|
||
|
11 SCO (Vendor Security Contacts) |
|
||
|
||||
|
|
|
||
|
||||
|
|
Articles / TULARC / Security / Vendor Security Contacts / | |
|
|
||||
|
|
|||
|
|
|||
|
||||
|
|
||||
|
|
|
||
|
11 SCO (Vendor Security Contacts) |
|
||
|
||||
|
|
|
||
|
||||
|
|
|
|
||
|
||
|
|
|
|
||
|
|
||
|
||
|
|
|
|
||
|
||
This article is from the Vendor Security Contacts FAQ, by Christopher Klaus cklaus@iss.net with numerous contributions by others.
Contact information for The Santa Cruz Operation (SCO):
* Send security related information to: security-alert@sco.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.
Continue to:
|
|
|
|
 |
|