> Richard add a -WWW option that makes available the files under the
> current directory. It's just a test tool, but still it should not
> allow anyone who can connect to the s_server port to obtain the
> contents of other local files; so we have to reject file names
> referencing directory ".."
Ben Laurie <[EMAIL PROTECTED]>:
> Attempting to make URL to file translations safe is a tricky task. I
> suggest we don't even bother with s_server - why would we want to? It is
> a test/demo tool?
Richard add a -WWW option that makes available the files under the
current directory. It's just a
Tests of OpenSSL 0.9.6a Beta 3, engine version in all cases, in all cases
did make, ran openssl speed test to make sure engine loaded properly, and
ran make test:
HP-UX 11.0 32-bit (hpux-parisc-gcc): Passed if libswift.sl was copied to
apps directory.
AIX 4.3 (aix43-gcc): Passed if libswift.a was
Quoting Andy Polyakov ([EMAIL PROTECTED]):
> > %ifarch sparc sparc64
> > ./Configure %{CONFIG_FLAGS} --openssldir=%{openssldir} linux-sparcv9 shared
> > %endif
>
> Should at least look like following:
>
> %ifarch sparc
> ./Configure %{CONFIG_FLAGS} --openssldir=%{openssldir} linux-sparcv7 shared
Bodo Moeller wrote:
>
> On Fri, Mar 30, 2001 at 04:55:52PM +0200, [EMAIL PROTECTED] wrote:
>
> > Modified:apps s_server.c
> > Log:
> > this time *really* fix the /../ check ...
>
> Well, I guess this one was a little late ...
>
> The original implementation had the problem that i
Shigeyuki Fukushima wrote:
>
> Hello.
>
> I'm a OpenSSL user.
> I found openssl's bug.
> I send a bug-fix patch.
> It is a fix for an infinte length SEQUENCE.
>
> infinite length SEQUENCE: 0x30 0x80 ...Contents... 0x00 0x00
>
> And also, I send a pkcs#7 data: cert.p7.
> Using openssl-0.9.6
I'm trying to use a certificate generated by a Java app (using a certain
Java Crypto library). It knows how to generate PKCS#8 format with DSA
parameters and identifies the algorithm as OID=1.3.14.3.2.12. This is
equivalent to "dsaEncryption-old" in crypto/objects/objects.h.
This Java library *
Has anyone successfuly compiled any version of SSL-MZ-telnet on hp-ux
11.00? I`ve tried to compile versions 0.11.1 and 0.11.2, and always got
this error(s):
cc -c -g -I../lib -I../include -I/usr/local/ssl/include
-DHAVE_CONFIG_H -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK
-DAUTHENTICATION sys_term.
"David E. Weekly" wrote:
>
> Please excuse this somewhat naive question.
>
> Would it make sense to integrate additional cryptography into OpenSSL's
> libcrypto? Would it be useful to have AES and Twofish, a TIGER hash, etc?
More crypto is always welcome. We do already have AES, however.
> Is
> > But this fails to generate the shared library.
>
> No, it doesn't.
I mean "that's correct, it doesn't generate shared libraries." A:-)
__
OpenSSL Project http://www.openssl.org
Development Mai
> %ifarch sparc sparc64
> ./Configure %{CONFIG_FLAGS} --openssldir=%{openssldir} linux-sparcv9 shared
> %endif
Should at least look like following:
%ifarch sparc
./Configure %{CONFIG_FLAGS} --openssldir=%{openssldir} linux-sparcv7 shared
%endif
%ifarch sparc64
./Configure %{CONFIG_FLAGS} --opens
11 matches
Mail list logo