Problem registering or updating behind an active SSL proxy service

This document (3527193) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Desktop 10
SUSE
Linux Enterprise Server 10

A proxy server is required or used to have access to the Internet.

Situation

Attempts to register the product or to use its online update feature fail.

The recommendations from the following TIDs have been followed but have not helped to resolve the issue:

Resolution

If use of the proxy service is not mandatory, disable use of the proxy service.
 
If the proxy service cannot be bypassed, change the configuration of the proxy service software so that it does not alter traffic between the SUSE Linux Enterprise 10 system and the registration service (secure-www.novell.com) and the online update service (nu.novell.com and possibly the older update.novell.com).

If the proxy configuration cannot be changed, follow TID 3963765 - Manually importing a certificate into a Linux system.

Additional Information

The registration and update mechanisms in SUSE Linux Enterprise 10 use HTTPS (HTTP over Secure Sockets Layer (SSL) or Transport Layer Security (TLS)) traffic (TCP port 443) to protect against tampering. In most network environments proxy software does not alter such traffic in any way, but merely passes it along between client and server.

In some network environments however, proxy software is used which actively scans (and, possibly, filters) the content of this type of connection; for example the
Microdasys SCIP Encrypted Content Security software. As the TLS/SSL protocols have been designed to protect against eavesdropping, the only way in which such software can operate is by working with two traffic sessions: one between the client software and the proxy and one between the proxy and the server; the proxy software then decrypts and reencrypts traffic in both directions. The certificate used by the "server" end of the session between client and proxy service is then not the server's certificate but rather the proxy's. As the proxy's certificate is not signed by a Certificate Authority which is trusted by the client software in SLE10, the client software, assuming an attempted man-in-the-middle attack, will refuse to use this connection.

Background information

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:3527193
  • Creation Date: 15-Oct-2007
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Desktop
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback@suse.com

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center