MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  August 2002

MSUNAG August 2002

Subject:

NOVL-2002-FAQ - Novell Security Alerts Facts Sheet (fwd)

From:

Joe Budzyn <[log in to unmask]>

Reply-To:

MSU Network Administrators Group <[log in to unmask]>

Date:

Tue, 13 Aug 2002 15:43:22 -0400

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (180 lines)

I thought that this might be of interest.
Joe

---------- Forwarded message ----------
Date: 12 Aug 2002 20:20:57 -0000
From: Ed Reed <[log in to unmask]>
To: [log in to unmask]
Subject: NOVL-2002-FAQ - Novell Security Alerts Facts Sheet



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For Immediate Disclosure

============================== Summary ==============================

 Security Alert: NOVL-2002-FAQ
          Title: Novell Security Alerts Fact Sheet
           Date: 12 Aug 2002
       Revision: Original
   Product Name: Novell Products in general
 OS/Platform(s): Netware, Windows, Linux, UNIX, Solaris,
                 AIX, HP/UX, and others
  Reference URL: http://support.novell.com/security-alerts
    Vendor Name: Novell, Inc.
     Vendor URL: http://www.novell.com
Security Alerts: http://support.novell.com/security-alerts
        Affects: None - informational
    Identifiers: None

============================ Description ============================

In light of increased customer interest in Internet-related security
and the migration of Novell's products to the Internet Protocol,
Novell is taking steps to better inform our customers and partners
about security alerts.  This fact sheet is intended to answer
questions about this new policy and provide pointers to interested
parties who want additional information.

============================== Impact ===============================

Q: What is Novell's policy for releasing information about
product-related vulnerabilities?
A: Generally, Novell will provide information to the public (both
customer and non-customer) about real or potential security
vulnerabilities in our products along with recommended corrective
actions, patches and other guidance, as those corrective actions
become available; accordingly, we won't disclose information about
theoretical or unsolved (nor unsolvable) problems until a workaround
or product "fix" is available.

Q: Are there exception to this general policy?
A: For any given security vulnerability, we reserve the right to
provide information in a time and manner that we determine based on
the surrounding circumstances.

Q: Under what circumstances might Novell delay publishing information
about a problem?
A: We cannot predict every eventuality.  One circumstance may be when
we're aware or a problem but other vendors afflicted with the same
problem have not yet had the opportunity address the issue in their
own products.  Such circumstances will usually arise in conjunction
with our work with CERT (http://www.cert.org) or other multi-vendor
forums.

Q: How will Novell provide information to the public?
A: Novell intends to publish security alerts to CERT
(http://www.cert.org), Bugtraq
(http://online.securityfocus.com/archive/1), our own security-focused
web site (http://support.novell.com/security-alerts) and other
suitable public forums that become well known to our customers and
us.

Q: How is this different from past Novell policy?
A: In the past, customers could find information about fixes to
security-related problems, but we didn't make it particularly easy
for customers (or attackers) to find the information.  That is what
is changed.  Now, customers will be able to go to a single Novell
Support site to find security-related fixes for their Novell
products.

Q: Doesn't it pose a risk to customers to publish information about
vulnerabilities?
A: The risks to customers are the vulnerabilities themselves.  Novell
intends to notify customers about the fixes they should apply to help
protect them from those vulnerabilities.  It's every customer's
responsibility to maintain (and secure) its own systems and to keep
its Novell products up-to-date by applying security-related patches.
Novell cannot commit to keeping products free of security flaws, but
Novell is committed to providing a process to be used when a product
is suspected of having security problems.

Q: Where and how can people report suspected vulnerabilities in
Novell products?
A: The new web site, http://support.novell.com/security-alerts has a
form that can be used to submit information about a suspected
problem.  In addition, reports can be made to [log in to unmask] via
email.

Q: How do people without Novell support contracts report problems?
A: Novell is interested in security-related issues with all our
products, regardless of whether there's a support contract in place.
Use the same web site or email address as above:
http://support.novell.com/security-alerts and [log in to unmask]

Q: Is this a ploy to get customers to buy upgrade protection and
maintenance contracts from Novell?
A:  No.  In today's world and today's Internet, network systems are
facing many more attacks than ever before.  Customers who use our
products (and, for that matter - other vendor's products, too) have
to work harder to secure their systems from attack.  That's just the
way it is.  This new policy is one way to help customers keep on top
of their systems maintenance, and to easily know what patches and
precautions should be taken with our products.  Novell will benefit
if this attention to customer needs results in more sales, but that's
not why we're doing it.

======================== Recommended Actions ========================

Monitor Novell websites (http://support.novell.com/security-alerts)
for Security Alerts and (http://support.novell.com) regularly for
general information relating to the Novell products you have
installed, and follow the recommendations and directions posted
there.  It's every customer's responsibility to maintain (and secure)
their own systems and to keep their Novell products up-to-date by
applying security-related patches.

In addition, Novell recommends users periodically review websites
such as the following for reported vulnerability issues:

             CERT/CC (www.cert.org)
             ICSA (www.icsalabs.com)
             Security Focus (www.securityfocus.com)

============================ DISCLAIMER =============================

The content of this document is believed to be accurate at the time
of publishing based on currently available information. However, the
information is provided "AS IS" without any warranty or
representation. Your use of the document constitutes acceptance of
this disclaimer. Novell disclaims all warranties, express or implied,
regarding this document, including the warranties of merchantability
and fitness for a particular purpose. Novell is not liable for any
direct, indirect, or consequential loss or damage arising from use
of, or reliance on, this document or any security alert, even if
Novell has been advised of the possibility of such damages and even
if such damages are foreseeable.

============================ Appendices =============================

None

================ Contacting Novell Security Alerts ==================

To report suspected security vulnerabilities in Novell products, send
email to
            [log in to unmask]

PGP users may send signed/encrypted information to us using our PGP
key, available from the pgpkeys.mit.edu server, or our website at:

            http://support.novell.com/security-alerts


Security Alerts, Novell, Inc. PGP Key Fingerprint:

F5AE 9265 0A34 F84E 580E  9B87 3AC1 1974 DE05 0FDB

========================= Revision History ==========================
       Original: 12 Aug 2002 - Original Publication

-----BEGIN PGP SIGNATURE-----
Version: PGP Personal Security 7.0.3

iQA/AwUBPVgM/DrBGXTeBQ/bEQJDPQCdFNxb1k/BgRxiN9LcDig5QyezrzcAn0tm
NyaPoi6qpFREhLmoRVW8JbAT
=bAkR
-----END PGP SIGNATURE-----

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager