Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <392FD763.5127BAE8@vinschen.de> Date: Sat, 27 May 2000 16:10:43 +0200 From: Corinna Vinschen Reply-To: cygwin X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.14 i686) X-Accept-Language: de, en MIME-Version: 1.0 To: Prentis Brooks CC: Cygwin Subject: Re: Further joys in the realm of sshd... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Prentis Brooks wrote: > [...] > Now to accomplish the third requirement, I need to run sshd on a third port > as that user. The problem I am encountering is that sshd dies with the > following error: > > sshd: no RSA support in libssl and libcrypto -- exiting. See ssl(8) > > I can't find the ssl(8) reference. The command I am using to get this is: If one didn't log on via normal workstation login to the machine, his/her user hive isn't loaded to the registry. The current implementation of /dev/random calls the Crypto API so that a user specific key container is used. This fails if the user hive isn't loaded. To get rid of that problem, the Crypto API provides a mechanism to use a so called `machine keyset'. I have just patched the /dev/random implementation to use that machine keyset instead of the user specific keyset. That will be part of the next developer snapshot and of the next net release. Corinna -- Corinna Vinschen Cygwin Developer Cygnus Solutions, a Red Hat company -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com