Most likely this occurs when the ldap port number specified in the connection windows was not a SSL port. If non-secure socket is used to connect to a server's SSL socket, then the application using the non-secure socket will hang. This is a characteristic of the SSL protocol. Open Channel Software runs entirely on Open Source Software. We return value to the Software community in the form of services and original software.

Also, if you see: SSL_Accept failed error:140760EB:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol in your error log, it's for the same reason. See similar questions...

Because you connected with HTTP to the HTTPS port, i.e. you used an URL of the form ''http://'' instead of ''https://''. This also happens the other way round when you connect via HTTPS to a HTTP port, i.e. when you try to use ''https://'' on a server that doesn't support SSL (on this port). Make sure you are connecting to a virtual server that supports SSL, which is probably the IP associated with your hostname, not localhost (127.0.0.1). There can be various reasons. See similar questions...

The very first time a secure connection is established Java must create a secure seed required for the SSL connection. This is a very computationally expensive process and may take up to a few seconds on certain platforms. However, the seed only needs to be computed once per session. See similar questions...

I upgraded to OpenSSH 3.1 and X11 forwarding stopped working. Starting with OpenSSH 3.1, the sshd x11 forwarding server listens on localhost by default; see the sshd X11UseLocalhost option to revert to prior behaviour if your older X11 clients do not function with this configuration. In general, X11 clients using X11 R6 should work with the default setting. Some vendors, including HP, ship X11 clients with R6 and R5 libs, so some clients will work, and others will not work. See similar questions...

You will need to check your browser settings to make sure that it enables SSL. SSL is the protocol for encrypting data over the Internet. You will need to make sure you accept SSL and Cookies. See similar questions...

If you have a very large website, the chances of Frontpage timing out is greater. The more files you have, the longer it will take FrontPage to connect to your website. All of our webservers are set to a time-out rate of 900 seconds, or 15 minutes. According to Microsoft, this time period is more than sufficient to allow heavy operations of FrontPage extensions to complete. The best solution is to simply do your FrontPage updates at night, when Internet traffic is much lower than during the day. See similar questions...

This was a bug in beta versions of the driver. The current release of the driver no longer has this problem. We encourage you to update frequently and to join wireless-beta mailing lists to get notice of enhancements and bug fixes. Unfortunately, three things need to be right before you can use our driver to connect to the internet. First, our driver must recognize your card. Next, your wireless router must be correctly configured correctly to talk to the internet. See similar questions...

There a number of reasons why FrontPage hangs, the biggest reason is related to the amount of data in your public_html directory, both in size and number of files and directories. The more files/directories and size of data, the longer it will take FrontPage to log in. Large amounts of data (> 50MB) and/or a large number of files or directories ( > 500) can cause FrontPage to hang and perhaps even timeout. See similar questions...

The Browser is closely integrated with the JSSE library from Sun. It is a free pure Java SSL library. copying the jnet.jar, jsse.jar, jcert.jar files from the lib/ directory of the JSSE package to the lib/ directory of the Browser. And that's all. To connect using SSL just make sure to select the SSL box in the connect window and specify the right port number. See similar questions...

Most browsers are capable of supporting the SSL protocol and will automatically detect the presence of this protocol and convert to secure mode, which is indicated by the presence of either an unbroken, yellow key, or a closed, yellow lock on the bottom left-hand corner of the browser's status bar. See similar questions...

SSL stands for Secure Sockets Layer (yawn!!!). A secure connection or SSL, is an encryption technology that scrambles up your information and then sends it over the Internet. Without an SSL, data going over the Internet is viewable to anyone who intercepts it. A SSL does not need to be applied to an entire website, only personal and sensitive information. Westerly.com uses Paypal to process credit cards and they are the leader in fighting online credit card fraud. See similar questions...

To enable debug mode for secure connections use -Djavax.net.debug=all option on the command line to the Java interpreter. For example: java -Djavax.net.debug=all -classpath ..... lbe.ui.BrowserApp For details on how to modify the 'lbe' scripts to enable this property see the question about this. See similar questions...

The Insight Browser will take about 1 minute to completely load with a modem at 28K, faster for a modem at 45K. The Java Client will take about the same time. When you zoom into images, be patient. But once you have accessed with a modem, when you access the next time, it will be about twice as fast since Insight stores some of the data in your Browser cache. The best way to get the benefit of the high resolution images we offer is to get some kind of broadband Internet access - cable or dsl. See similar questions...

What is SSL? The SSL security protocol provides data encryption, server authentication, message integrity, and optional client authentication for a TCP/IP connection. Because SSL is built into all major browsers and web servers, simply installing a digital certificate turns on their SSL capabilities. See similar questions...

SSL (Secure Socket Layer) support was added as an optional, additional cost feature in Telnet Magic release 2.2. Telnet Magic supports SSL version 2, SSL version 3 and TLS version 1. See similar questions...

Most 5.1 binaries have support for SSL connections between the client and server. We can't currently build with the new YaSSL library everywhere, as it's still quite new and does not compile on all platforms yet. See Section 5.9.7, "Using Secure Connections". You can also tunnel a connection via SSH, if (for instance) if the client application doesn't support SSL connections. For an example, see Section 5.9.7.5, "Connecting to MySQL Remotely from Windows with SSH". See similar questions...