Yup the script works perfectly fine if no GUI is created.
In fact I had no intention of writing a GUI as it served my purpose without
one. But certain "non command prompt friendly" friends of mine would like a
GUI. So I tried my hand at creating one.
Let me try undef'ing all the GUI objects a
Emmanuel E wrote:
Even here the start_SSL fails.
Can you make a script work without using any GUI (either Win32::GUI ot
Tk). If so, then we can investigate further. If not, then it is likely
a problem in Openssl/Net::SSLeay. The Win32::GUI code goes nowhere
near any of the socket stuff,
Yes I do enter the dialogue phase. Then when I attempt to start the socket I
end the dialogue phase by returning -1;
Thread or no thread the error still occurs.
I was trying to spawn off a new thread in the button_Click subroutine but
that new thread used to fail in the start_SSL() funtion.
Hi,
the start_SSL() function fails only if the GUI is initialized with the
error
- "SSL connect attempt failed".
If you haven't entered the dialogue phase there should be no reason why you
would get this error.
From a preliminary search I figured that Net::SSLeay (the underlying to
IO::So
Hi,
I have written a program using Win32::GUI to provide a user-interface to a
network script.
However the SSL portion of the script fails if the GUI is invoked.
Basically the script is like this:
1) Show UI and take parameters.
2) On UI event Create a socket.
3) Attempt to SSLify the socket us
5 matches
Mail list logo
