search

maurice-daly / DriverAutomationTool

Home of the Driver Automation Tool
https://www.msendpointmgr.com
BSD 2-Clause "Simplified" License
395 stars 120 forks source link

Security concern #484

Open tintong opened 1 year ago

tintong commented 1 year ago

Hello,

I've been using the Driver Automation Tool for numerous years and love it, however, with security getting more and more tighter the use of the Driver Automation Tool is becoming a big concern.

My work place is currently using Cisco to protect from DNS security issues and as part of this has blocked access to "raw.githubusercontent.com". When this block is in place, it makes the Driver Automation Tool useless as it will not run.

Is there a way to get around this please without having to whitelist that URL?

Thanks

PowershellBacon commented 1 year ago

If you cant manually hit that URL you would have to find a way to get that data locally then and then change the script to get the local file instead of directly from the URL.

ajn142attamu commented 1 year ago

It’s not exactly what you need, but I did something similar by editing the script to look at the OEMLinks.xml file hosted in my forked repo. Rewriting the code to work on a local file is beyond my ken, but it should be possible to maintain your own version of the files on a host on your internal network, and edit an internally maintained copy of the script to look there instead of GitHub

Here’s my fork as an example (again, not looking at an internal host, just another fork hosted on GitHub), I haven’t figured out compiling the .exe or .msi like the repo owner, so you have to run the .ps1 directly from an Admin Powershell window.

https://github.com/ajn142attamu/DriverAutomationTool/blob/master/Current%20Branch/7.2.2/DriverAutomationTool.ps1