In message <[EMAIL PROTECTED]> Jesper Skriver writes:
: On Mon, May 07, 2001 at 12:11:16AM -0600, Warner Losh wrote:
: > In message <[EMAIL PROTECTED]> Kris Kennaway writes:
: > : Check the archives, this is a FAQ with probably the usual answer.
: >
: > Hint: the answer is in UPDATING.
:
: Perha
Peter Jeremy wrote:
>
> Having built and installed -current from last Friday, I find that ssh*
> is now reporting "no RSA support in libssl and libcrypto. See ssl(8)"
> and will only talk SSH2. I couldn't find anything relevant in ssl(8).
>
> I haven'
On Mon, May 07, 2001 at 12:11:16AM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Kris Kennaway writes:
> : Check the archives, this is a FAQ with probably the usual answer.
>
> Hint: the answer is in UPDATING.
Perhaps we could add "Make sure you have loaded random.ko" to the output
In message <[EMAIL PROTECTED]> Kris Kennaway writes:
: Check the archives, this is a FAQ with probably the usual answer.
Hint: the answer is in UPDATING.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Mon, May 07, 2001 at 09:16:31AM +1000, Peter Jeremy wrote:
> Having built and installed -current from last Friday, I find that ssh*
> is now reporting "no RSA support in libssl and libcrypto. See ssl(8)"
> and will only talk SSH2. I couldn't find anything relevant i
Having built and installed -current from last Friday, I find that ssh*
is now reporting "no RSA support in libssl and libcrypto. See ssl(8)"
and will only talk SSH2. I couldn't find anything relevant in ssl(8).
I haven't specified "WITH_RSA=NO" anywhere and c
On Sat, 31 Mar 2001, Thomas Moestl wrote:
> Do you have
> device random
> in your kernel configuration? Absence of a working random device
> triggers this bug. The need for this is also documented in UPDATING.
Also, /dev/urandom is now a symlink to /dev/random. A quick "cd /dev; rm
urandom; ln -
d completing ...
>
> ssh: no RSA support in libssl and libcrypto. See ssl(8).
> Disabling protocol version 1
> DH_generate_key
Do you have
device random
in your kernel configuration? Absence of a working random device
triggers this bug. The need for this is also documented in UPDATING.
how does one fix this? *puzzled look* there is no ssl(8) that I can seem
to find to See, and nothing apparent in the UPGRADING file ... system
uptodate as of last night, and mergemaster just finished completing ...
ssh: no RSA support in libssl and libcrypto. See ssl(8).
Disabling protocol
Tue, Mar 27, 2001 at 11:33:11, mark (Mark Murray) wrote about "Re: random woes ("no
RSA support in libssl and libcrypto")":
> > Well, but it says about `options RANDOMDEV'. Later, `device random' was
> > invented instead of it. A few days ago I instal
d legacy since 3.1-RELEASE) and /usr/sbin/sshd began to refuse
> supporting protocol 1 with identical message
> (`no RSA support in libssl and libcrypto. See ssl(8)'). Also,
> kernel was build with `device random', and
>
> netch@iv:/usr/HEAD/src/sys/i386/conf>egrep '(
On Tue, 27 Mar 2001, Valentin Nechayev wrote:
> And, my questions are
> 1) What can happen to refuse RSA support in libcrypto, with environment
> described above?
I suspect you need to remake /dev/urandom. Copy /usr/src/etc/MAKEDEV from
-current into /etc and remake the device. /dev/u
Mon, Mar 19, 2001 at 16:02:08, mark (Mark Murray) wrote about "Re: random woes ("no
RSA support in libssl and libcrypto")":
> > ssh: no RSA support in libssl and libcrypto. See ssl(8)
[...]
> > It seems the compatibility with the previous minor of urandom
> It seems the compatibility with the previous minor of urandom has
> been silently removed (I assume this happened with the last
> update/cleanup of the random device). It took me two hours to figure
> it out.
See src/UPDATING 2624
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Uns
Just in case some else gets caught (which is sure to happen), in
case you get the following obscure message from ssh after updating
your -current:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
This just means you need to remake your /dev/urandom (ln -f random
urandom).
It seems the
In message <[EMAIL PROTECTED]> Julian Elischer writes:
: Unfortunatly /etc/updateing doesn't warn you of this..
: I hit this as well.
: What is in /etc/updating is so vague and nondescript that
: it doesn't help wit this problem. (at least as it was when I hit it)
There is no /etc/updating. UPDA
>
> > I have been trying to get ssh working in current, but with no luck.
> > Since I updated recently, all I get is:
> >
> > ssh: no RSA support in libssl and libcrypto. See ssl(8).
> >
> > I have been off the lists for a bit, so I apologize if I missed
>
On Thu, Jun 29, 2000 at 11:29:40PM +0200, Mark Murray wrote:
> Hi
>
> Either you have no RANDOMDEV in the kernel, or you have not loaded the
> module.
that's right, no RANDOMDEV
and no module...
Id Refs AddressSize Name
14 0xc010 2729e4 kernel
21 0xc0dc7000 4d000nfs
Hi
Either you have no RANDOMDEV in the kernel, or you have not loaded the
module.
M
> On Thu, Jun 29, 2000 at 02:25:50AM -0500, Chris Csanady wrote:
> > I have been trying to get ssh working in current, but with no luck.
> > Since I updated recently, all I get is:
> >
&g
On Thu, 29 Jun 2000, Andreas Klemm wrote:
> On Thu, Jun 29, 2000 at 02:25:50AM -0500, Chris Csanady wrote:
> > I have been trying to get ssh working in current, but with no luck.
> > Since I updated recently, all I get is:
> >
> > ssh: no RSA support in libss
On Thu, Jun 29, 2000 at 02:25:50AM -0500, Chris Csanady wrote:
> I have been trying to get ssh working in current, but with no luck.
> Since I updated recently, all I get is:
>
> ssh: no RSA support in libssl and libcrypto. See ssl(8).
Same for me ... Wanted to make a ssh session
Hi
Please check /usr/src/UPDATING
M
> I have been trying to get ssh working in current, but with no luck.
> Since I updated recently, all I get is:
>
> ssh: no RSA support in libssl and libcrypto. See ssl(8).
>
> I have been off the lists for a bit, so I apologize if I
On Thu, 29 Jun 2000 05:37:35 CDT, Chris Csanady wrote:
> Hmm, I read through UPDATING, but didn't find much about this..
Hmm, you're right; it doesn't explicitly say you need option RANDOMDEV
in your kernel config. It just warns you about the state of the entropy
harvesting.
The exact "HowTo
>
>
>On Thu, 29 Jun 2000 02:25:50 CDT, Chris Csanady wrote:
>
>> I have been trying to get ssh working in current, but with no luck.
>> Since I updated recently, all I get is:
>>
>> ssh: no RSA support in libssl and libcrypto. See ssl(8).
>
>Thi
On Thu, 29 Jun 2000 02:25:50 CDT, Chris Csanady wrote:
> I have been trying to get ssh working in current, but with no luck.
> Since I updated recently, all I get is:
>
> ssh: no RSA support in libssl and libcrypto. See ssl(8).
This is the system's way of punishing you fo
I have been trying to get ssh working in current, but with no luck.
Since I updated recently, all I get is:
ssh: no RSA support in libssl and libcrypto. See ssl(8).
I have been off the lists for a bit, so I apologize if I missed
something, but this has always been confusing. It used to just
26 matches
Mail list logo
