hey,
I want to be able to automatically log into a website and interact with the
logged in, secure website. Unfortunately, it is 'protected' with one of those
automatic login/password 'authorization' type boxes. How do you get around
them? And how do you get around the timeouts (ie: when someon
Ed Peschko <[EMAIL PROTECTED]> writes:
> PS: has anyone successfully used openSSL on solaris? With SSLeay, I was getting
> core dumps consistently. Also, is there a FAQ on Net::SSLeay.pm?
Not to my knowledge. What question do you propose?
--Sampo
_
Howdy,
I seem to have come across a bug in OpenSSL. In general, it performs
flawlessly. My problem is a segmentation fault by the client when I
arbitrarly kill the server (serious testing going on here). I recompiled
OpenSSL with the -g parameter, and ran my client under gdb. Here is the
session
hey,
When I built OpenSSL for Solaris 2.6, I noticed that the socket libraries are
not provided by default. if you add:
EX_LIBS=-lsocket
to the makefile generated by ssldir.pl, it works fine.
Ed
(
PS: has anyone successfully used openSSL on solaris? With SSLeay, I was getting
core dumps con
Hello,
Can someone explain to me if, and how much, SSL protects normal
username/password authentication for accessing web pages. I think the
password is sent encrypted over the wire, but are there any weaknesses I
might not be aware off.
P.S. We will have a token-based authentication scheme very
