![]() ![]() Just in time though I skidded to a halt and realized that I had nothing better to offer. I was right away heading over to the stable, saddling my moral high horse, to launch into a lecture why this is not a good idea, a security hole in fact and that the “open” verb was intentionally left un-associated in order to avoid scripts just being run by anyone from wherever. As one user put it: “We not only write scripts, we write them to run them”. To make a long story short, it seems users associate the “open” verb with PowerShell.exe, so that they can simply double click any script and run it. Just kidding, I wasn’t really all that puzzled. So I was a little puzzled when I heard that some people don’t agree with me. For us, opening a script in PowerShell Studio when you double click on it in File Explorer, is what we found to be most convenient. Since the “open” verb is by default not associated with anything, for a good reason, I usually asked why that was an issue. ![]() Every now and then we get a forum post or an email from a customer bemoaning that PowerShell Studio associates the ‘open’ verb for Windows PowerShell script (.ps1) with itself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |