Https not supported in wol-trigger

system · November 19, 2009, 12:22am

(imported topic written by wcwelch91)

Hello All,

I am attempting to user the Bigfix-WoL-Trigger-0.5.0.0 executable and encountering the following error.

501 Protocal scheme ‘https’ is not supported <Crypt::SSLeay not installed> at Bigfix-WoL-Trigger-v0.5.0.pl line 49

We currently have our web reports host set for SSL (https) while the BES server host is not (http).

Does this scenario have the same cross-domain issues as the wake on web?

Thanks to all,

Bill

BenKus · November 19, 2009, 5:35am

(imported comment written by BenKus)

Hey Bill,

The WoL trigger doesn’t run in a browser so it doesn’t have a cross-side scripting issue… but it does have the problem that it doesn’t support HTTPS natively… I think this is my fault because I built the script (sorry)…

I will try to dig up the source code and recompile it for you (or maybe I can get Zak to do it)…

Ben

BenKus · November 19, 2009, 5:41am

(imported comment written by BenKus)

Maybe this was easier than I thought… Can you help me test this version and see if it works with HTTPS?

http://software.bigfix.com/download/bes/util/BigFix-WoL-Trigger-0.6.0.0.exe

Ben

system · November 19, 2009, 4:29pm

(imported comment written by wcwelch91)

Hi Ben,

That worked perfectly. Thank you.

If you need any further testing I’m happy to help.

-Bill

system · November 19, 2009, 4:49pm

(imported comment written by MattBoyd)

We also needed this. Thanks Ben!

system · December 22, 2009, 6:36pm

(imported comment written by raveldc91)

Ben,

Would you be able to provide the source code for this, or an abstracted example? We need this to work on Linux and Macintosh as well.

BenKus · December 8, 2011, 9:10pm

(imported comment written by BenKus)

Sure… see attached…

Ben

system · December 23, 2009, 4:05pm

(imported comment written by raveldc91)

Thanks Ben. For some reason I never see the attachments in the forums. Is there a setting to change/tweak?

P.

BenKus · December 24, 2009, 11:40am

(imported comment written by BenKus)

I think older forum members sometimes have some permissions problems… I updated you to a “member”… See if that helps…

Ben

system · January 14, 2010, 5:39pm

(imported comment written by raveldc91)

Thanks Ben!

One other thing, the perl script you provided is great, but portability across all OS X platforms is an issue. Would you be able to compile the perl script with your tool using OS X as a target?

BenKus · January 15, 2010, 9:45am

(imported comment written by BenKus)

You want to compile it to run on OSX? I don’t have a perl compiler for that…

Ben

system · January 18, 2010, 9:35pm

(imported comment written by raveldc91)

Are you using the ActiveState compiler?

Noah · January 18, 2010, 10:21pm

(imported comment written by NoahSalzman)

If you are on a Mac, and you want to turn this script into a standalone “executable”, you can always use PAR::Packer. The steps I used were:

get SOAP::lite using this command --> cpan SOAP::Lite
get PAR::Packer using this command–> cpan PAR::Packer
create the package using this command --> pp -o BigFix-WoL-Trigger-v0.5.0 BigFix-WoL-Trigger-v0.5.0.pl
make the package executable --> chmod 744 BigFix-WoL-Trigger-v0.5.0

system · January 20, 2010, 12:03am

(imported comment written by raveldc91)

I tried that. Doesn’t work on 10.4, it doesn’t include all of the relevant modules. Biggest problem is that the versions of perl are so different. When I compile with Macports, you end up with a “Bad CPU type” error message.

P.