Dear All,
I am a contributor to the WCE port of stunnel, using intensively openssl.
I have recently completed the port of stunnel v434 to WCE platform,
and needed a refreshed version of openssl for that target.
I have recompiled openssl v100a with MS EVC4 sp4 free compiler, MS
WCE420 SDK and
Hello,
I have to install openssl on a Computer with openSUSE where I don't have any
root rights.
Is this possible? How?
Thanks in advance
--
View this message in context:
http://old.nabble.com/Install-openssl-without-root-rights-tp29825759p29825759.html
Sent from the OpenSSL - User mailing
Hello, brothers and sisters help me. See attached for details.
I use Windows 7 64bit OS on ASRock Motherboard, MinGW-5.1.6 + MSYS-1.0.11,
msysDTK-1.0.1, other windows platform requirements for squid,
squid-2.7.STABLE8, and also squid-2.7.STABLE9 it gives stack.o error,
Win64OpenSSL_light-1_0_0a
Hello, brothers and sisters help me. See attached for details.
I use Windows 7 64bit OS on ASRock Motherboard, MinGW-5.1.6 + MSYS-1.0.11,
msysDTK-1.0.1, other windows platform requirements for squid,
squid-2.7.STABLE8, and also squid-2.7.STABLE9 it gives stack.o error,
Win64OpenSSL_light-1_0_0a
On 28-09-2010 06:39, Vivek Madani wrote:
Clipped earlier communication
What OS is this running on? That error can be caused by a DLL being loaded to
an address that is already in use under Windows and relocation would
invalidate the signature.
You can work around that by specifying an
On 28-09-2010 08:57, fabermundi wrote:
Hello,
I have to install openssl on a Computer with openSUSE where I don't have any
root rights.
Is this possible? How?
Thanks in advance
Step 1: Compile it yourself from source.
Step 2: During compilation and install, install to your own home dir,
It depends what you mean by 'install'.
You can certainly install it under your home directory and use it or link
to it. I often do that when testing with a new version.
If you want to install it in a standard place like e.g. /usr/lib, then you
need rights to write that directory, often root
I don't want to discourage you from learning the details yourself, but
you may want to look at some wrapper software that is already worked
out and takes care of these things for you. For example, I usually
find TinyCA adequate to my minuscule certificate-processing needs.
Even if you decide not
On Tue, Sep 28, 2010 at 4:51 PM, Jakob Bohm jb-open...@wisemo.com wrote:
On 28-09-2010 06:39, Vivek Madani wrote:
Clipped earlier communication
What OS is this running on? That error can be caused by a DLL being
loaded to
an address that is already in use under Windows and relocation would
Not discouraged at all (just short on time trying to meet a deadline).
I'll check out TinyCA (and the like) in the meantime, but actually do
hope to delve into the source and figure out those directives when I get
some time. I do appreciate your time and attention!!
On 09/28/2010 09:41 AM,
On Tue, Sep 28, 2010, Vivek Madani wrote:
Clipped earlier communication
What OS is this running on? That error can be caused by a DLL being loaded
to
an address that is already in use under Windows and relocation would
invalidate the signature.
You can work around that by
On 9/27/2010 4:13 PM, Scott Neugroschl wrote:
As David said, yes.
On the other hand, you could re-implement malloc() and free() for your
platform.
There's really no way to make that help very much. It might help a
little, but the fundamental problem is this:
If you want to implement each
First, check to see that you're not able to have root rights via
'sudo'. If you can, you can just install it as a package. If you
can't...
Use './config --prefix=$HOME' (or whatever you want the installation's
root to be), set 'export
LD_LIBRARY_PATH=$HOME/ssl/lib:$HOME/lib:$LD_LIBRARY_PATH' in
13 matches
Mail list logo
