h openssl 0.9.4.
Openssl version:
OpenSSL 0.9.5beta2 27 Feb 2000
built on: Wed Mar 1 01:12:08 CET 2000
platform: linux-mips
options: bn(64,32) md2(int) rc4(ptr,int) des(idx,cisc,4,long) idea(int)
blowfish(idx)
compiler: gcc -fPIC -DL_ENDIAN -DTERMIO -O3 -fomit-frame-pointer -Wall
--
Niels Poppe
re about it in a few sentences
> I can try to give you an answer.
I have no details, but TACACS is one authentication protocol that Cisco
routers can use for authentication. Much like LDAP I think.
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
___
when you do, that would make the test depend on
the correct packaging and configuration of compile-time options,
which was done by packagers (like me) and not by the authors.
When you want reliable results you should indeed compile things
yourself,
using the same
ou to execute rpm --rebuild on
the later apache-mod_ssl source packages will work.
That would give you the latest released stable openssl library
and the newest apache-mod_ssl in most cases.
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
___
install a
> mod_ssl-2.2.8-x.i386.rpm? (Does such a thing exist?) I tried installing them
> and building a DSO of mod_ssl, but the Apache installation from the RPM
> files listed above was not EAPI, so it didn't work.
>
This will not work exactly for this reason. It sure w
/usr/bin/c_hash
/usr/bin/c_info
/usr/bin/c_issuer
/usr/bin/c_name
/usr/bin/c_rehash
/usr/include/ssl
/usr/include/ssl/asn1.h
...
/usr/include/ssl/x509v3.h
/usr/lib/libcrypto.a
/usr/lib/libcrypto.so
/usr/lib/libssl.a
/usr/lib/libssl.so
--
Niels Poppe - org.net bv &l
Magnus Stenman wrote:
>
> Uploaded to the usual place,
> http://www.engelschall.com/sw/mod_ssl/contrib/
>
> /magnus
rebuilt unchanged, for linux-alpha
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
_
ly reproduce it.
> >
> I still got bad data, when I tried it today, 29 mar.
> So this is still a problem with the NS 4.5 mac version.
> International 40-bit version.
>
My Mac (MacOS bluebox 8.1 on top of Rhapsody DR 2 on PPC) Netscape 4.5
US 128-bit passes...
--
Niels Popp
ges with a higher release number and built
from the 'official' frozen 0.9.2 sources.
Because of that, the 'release number' is 0_0328 to reflect the
CVS snapshot it is made from. 'rpm -q --changelog openssl' will
show the top of the cvs CHANGES log.
--
ared
libraries.
The 2.2.5 alpha version is now built shared. Therefore it
currently depends on openssl-0.9.2-0_1999_03_14.alpha.rpm
which can be found at the same location.
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
___
from
cron...
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
__
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automa
VS CHANGES file, while 'rpm -q --changelog
-p ' shows the entire file.
The apache-mod_ssl package is a straight rebuild for the alpha
of Magnus' i386 package which is numbered equal.
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
S/MIME Cryptographic Signature
0 and has the CVS modification date appended.
For the mips binaries I did not yet bundle it to rpms because
that would interfere with the vendor software that is needed
to configure the box itself. It is running fine but just
installed from the sources somewhere into /usr/local.
In case
be changed, hence the new release number.
As you are uploading rpm packages yourself, why do you ask?
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
__
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod
or openssl,
which will make rpm require just libssl.so.0 and libcrypto.so.0
This way these can be provided by any package.
We dont say Requires: glibc to every package, do we? We depend
on major version numbers for the shared libraries.
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
_
ll encryption stuff than to build
backdoors or weaknesses that specific governments may require.
I think you'll need to build custom clients as well to actually
use any 40-bits encrypted https. Do these exist at all?
--
Niels Poppe - org.net bv <[EMAIL PROTECTED]>
___
Marc Slemko wrote:
>
> On Tue, 5 Jan 1999, John wrote:
>
> > I think this would be a very useful option to have built into the main
> > distribution (or at least available via option "most"), just like the
> > other useful limitations we can make for timeouts, etc.
>
> It probably will be at so
John wrote:
>
> "Ralf S. Engelschall" wrote:
>
> > AFAIK we've no mechanism which limits the connections on a per IP basis. But
> > you can write a patch which implements this within a few hundrets of lines of
> > code, I think.
>
> I think this would be a very useful option to have built into
Xiaping Lin wrote:
>
> Hi,all
>
> I installed apache1.3.3 with mod_ssl_2.1.1 on my SUN sparc 10 machine. I created my
>own CA and signed own server cert.
> To create client certicficate, I downloaded PKCS12 from Dr. Henson's FAQ page,
>patched CA certificate (with ca-fix) and compiled PKCS12.e
OK, I've read through the sw-mod-ssl mail archive.
So, I am the only one having this problem (?)
I must be doing something wrong...
Configuration:
linux/intel RedHat (5.1 there)
apache-mod_ssl-1.3.3-2.0.13-1 (from ftp.replay.com)
SSLeay=0.9.0b-3 (same site)
pcks12-prog-052 (latest c-sourcefile Au
d_ssl/
> Official Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
Niels Poppe, org.net bv, <[EMAIL PROTECTED]>
S/MIME Cryptographic Signature
21 matches
Mail list logo
