Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML SSL 3.0 Vulnerability - Poodle and Beast - PVCS Version Manager - How to disable SSLv3 and optionally TLSv1
This is the result of a flaw in the SSL 3.0 protocol, and the specific attack may allow a man-in-the-middle to intercept parts of SSL-encrypted communications. Can be mitigated by forbidding SSL3 protocol for HTTPS connections .
CMS-XML How to setup an Apache Reverse Proxy to access a VM I-Net Web Client server running VM 8.6.1 or newer
Starting with VM 8.6.1, the Agent process running on the end-user's PC uses the WebSocket protocol to connect to the server. A WebSocket connection is established via an HTTP protocol upgrade, and additional configuration is require to pass this through a reverse proxy.
CMS-XML About: VMINET 6.x: - What is Secure Sockets Layer (SSL)
1.The ability to secure (encrypt, authenticate, and provide data integrity for) arbitrary TCP/IP connections using any TCP/IP application-level protocol . Such protocols include HTTP, Gopher, FTP, Telnet, S-HTTP, and many others - including protocols yet to be invented, such as future versions of HTTP itself.
CMS-XML VM on UNIX/Linux cannot use SSH (Secure shell) when GUI is running in setuid mode
error X11 X-11 rejected because of wrong authentication error "Class not found: pvcs.suite.gui.PvcsApp" warning: X11 connection requests different authentication protocol X11 connection rejected because of wrong authentication.
CMS-XML VM GUI on UNIX/Linux cannot run in setuid mode when X-Windows is tunneled through SSH (Secure shell)
error X11 X-11 rejected because of wrong authentication error "Class not found: pvcs.suite.gui.PvcsApp" warning: X11 connection requests different authentication protocol X11 connection rejected because of wrong authentication.
CMS-XML Is Version Manager 8.6.2 affected by CVEs that include Tomcat 8.5.42 as an affected release?
If an HTTP/2 client exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol ), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
MS-WORD Possible Architecture for Using VM in a heterogeneous environment
1. File Sharing such as NFS or SMB (Samba) connection to access UNIX Repository from NT Version Manager or NT VM Inet. ... 4. Use a web browser and web server to connect via the Internet or an Intranet session and transfer files using http protocol .
CMS-XML VM 8.5.2: Patch for Version Manager 8.5
... the IPv6 network protocol (Windows, ... ... the IPv6 network protocol (Windows, ... 1.1.1 Added support for IPv6 [ENH191524] ... , only the connection to the Serena ... ... the IPv6 network protocol (Windows, ... ... the IPv6 network protocol (Windows, ... 1.1.1 Added support for IPv6 [ENH191524] ... , only the connection to the Serena ... 2.3.1 VM I-Net Web Client cannot connect DaemonServer processes under some circumstances [DEF253978] ... "8180" protocol ="HTTP ... ... "8080" protocol ="HTTP ... ... "8180" protocol ="HTTP ... ... "8080" protocol ="HTTP ... ... "8180" protocol ="HTTP ... - 70 | <Connector port="8080" protocol ="HTTP/1.1" ... + 70 | <Connector port="8180" protocol ="HTTP/1.1" - 70 | <Connector port="8080" protocol ="HTTP/1.1"
CMS-XML I-Net: Sorry, access to the port number given has been disabled for security reasons.
To avoid protocol spoofing by rouge/misconfigured URLs, Netscape Proxy Server does not allow clients to connect on certain reserved ports. ... If the client attempts to connect on any of the above ports, the proxy server will deny the connection and return the following error...
MS-WORD How to set up VM Server on two separate servers
The file is then passed to the client via the connection between the web server and the user’s browser. ... The following steps allow you to set up the web server on one machine, and JRun on another, so that the only connection between the two machines is one socket (port) that can be tightly controlled by the administrator. No drives need be mapped, nor DNS set up to allow UNC connections from the web server to the archive server. The only needed protocol between the two is TCP/IP.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs