I would have said that something must have updated either the LIBEAY32. Dll or another dll that depends on it. You may find some helpful information using the depends tool .
If you use this to open up the perl. Exe then it should highlight the dependency path that produces the problem. You can compare this with other machines on which perl runs.
Have discovered that this only occurs when the script is run on a different drive to the one where the EXE is located. As a work around for this I have simply moved the scripts execution.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.