On Wed, 26 Sep 2001, Beech Rintoul wrote:
> On Wednesday 26 September 2001 08:52 am, Beech Rintoul wrote:
> > I'm having problems with several applications not finding libc.so.4 since
> > it was moved to compat. I do have COMPAT4X=yes in the /etc/make config and
> > ldconfig -r does list them as
On Wednesday 26 September 2001 08:52 am, Beech Rintoul wrote:
> I'm having problems with several applications not finding libc.so.4 since
> it was moved to compat. I do have COMPAT4X=yes in the /etc/make config and
> ldconfig -r does list them as being in compat. I have tried running
> ldconfig, b
I'm having problems with several applications not finding libc.so.4 since it
was moved to compat. I do have COMPAT4X=yes in the /etc/make config and
ldconfig -r does list them as being in compat. I have tried running ldconfig,
but still no joy. What do I need to do to get this box to use the ne
On Tue, 4 Apr 2000, Matthew D. Fuller wrote:
> > ** RSA_PKCS1: Unable to find an RSA implemenation shared library.
> (Aren't those filenames reversed? Just a hunch...)
Thanks for catching these - I've just fixed the typos.
Kris
In God we Trust -- all others must submit an X.509 certifica
On Tue, Apr 04, 2000 at 05:28:52PM -0500, Matthew D. Fuller wrote:
> Hi Ben :)
Hello Matthew, always nice to "see" you.
> On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me
> that Ben Rosengart remarked
> > Hello all,
> > I am running a 5.0-CURRENT system cvsup'd this afternoon
Hi Ben :)
On Tue, Apr 04, 2000 at 05:41:05PM -0400, a little birdie told me
that Ben Rosengart remarked
> Hello all,
> I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is
> not working for me. When I try to start it, I get the following:
>
> ** RSA_PKCS1: Unable to find an R
Hello all,
I am running a 5.0-CURRENT system cvsup'd this afternoon, and sshd is
not working for me. When I try to start it, I get the following:
** RSA_PKCS1: Unable to find an RSA implemenation shared library.
** Install either the USA (librsaINTL.so) or International (librsaUSA.so)
** RSA li
Dirk Roehrdanz wrote:
>
> Thanks for the modification.
> I have replaced the "[]" with "{}" . A run of "make buildworld" with
> the patch finished without errors.
Sorry about that. I did it quickly and the font I was using has the characters
looking identical. Time to change fonts :-)
> The
Hi Jim,
On 0, Jim Bloom <[EMAIL PROTECTED]> wrote:
> A similar patch was added for the USA version of RSA for the same basic reason.
> Your patch is almost correct. It should add the line:
>
> LDADD+= -L$[.OBJDIR]/../libcrypto -lcrypto
^ ^
>
> Your version woul
A similar patch was added for the USA version of RSA for the same basic reason.
Your patch is almost correct. It should add the line:
LDADD+= -L$[.OBJDIR]/../libcrypto -lcrypto
Your version would reference the system crypto library and not the one being
built as part of buildworld.
Jim Bloom
[
Hello,
On 0, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > I stuck a dlerror() in there and the problem is
> >
> > usr/lib/librsaINTL.so: Undefined symbol "BN_mod_exp_mont"
>
> This symbol is defined in bn_ext.c and should be compiled into libcrypt
On Thu, 23 Mar 2000, Paul Richards wrote:
> I stuck a dlerror() in there and the problem is
>
> usr/lib/librsaINTL.so: Undefined symbol "BN_mod_exp_mont"
This symbol is defined in bn_ext.c and should be compiled into libcrypto -
can you verify yours has it?
Kris
In God we Trust -- all ot
Kris Kennaway wrote:
>
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > > Because the dlopen() of librsaintl.so fails.
> >
> > Ok, I give up :-) Why would that happen then ?
>
> I don't know :-)
I stuck a dlerror() in there and the problem is
usr/lib/librsaINTL.so: Undefined symbol "BN_mod_e
Kris Kennaway wrote:
>
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > > Because the dlopen() of librsaintl.so fails.
> >
> > Ok, I give up :-) Why would that happen then ?
>
> I don't know :-)
>
> > I'm not the only person seeing this, it's been reported on the ports
> > list by someone els
On Thu, 23 Mar 2000, Paul Richards wrote:
> > Because the dlopen() of librsaintl.so fails.
>
> Ok, I give up :-) Why would that happen then ?
I don't know :-)
> I'm not the only person seeing this, it's been reported on the ports
> list by someone else as well.
Hmm, I think I missed this mail
Kris Kennaway wrote:
>
> On Thu, 23 Mar 2000, Paul Richards wrote:
>
> > I'm picking up my secure code from internat so why is modssl trying to
> > use rsaref rather than the international rsa?
>
> Because the dlopen() of librsaintl.so fails.
Ok, I give up :-) Why would that happen then ?
I c
On Thu, 23 Mar 2000, Paul Richards wrote:
> I'm picking up my secure code from internat so why is modssl trying to
> use rsaref rather than the international rsa?
Because the dlopen() of librsaintl.so fails.
> Is there a document that explains how all this is supposed to work, I've
> lost track
I've posted this to current because it seems to be related to the
OpenSSL code.
Apache-modssl throws out the error below when you try to access a SSL
port. The only place I can find this message is in the
openssl/rsaref/rsaref_stubs.c where it tries to open librsaref.so
I'm picking up my secure
18 matches
Mail list logo