 Rank: Administration Medals:  Joined: 5/30/2012(UTC)
Posts: 501
Location: Raleigh, NC
Thanks: 56 times
Was thanked: 82 time(s) in 68 post(s)
|
 This tool adds a Toolbox option to the right-click menu of the host page. Preset configurable commands can be sent to remote machines. Directions: 1. After installing the extension, click on the options to configure your settings. 2. Add in the commands you'd like to store and save settings. 3. Navigate to the host page, select a session(s), and right click. 4. Select the Command Toolbox and select the command to pass. 5. Your results will post to the commands tab for each session selected. This extension is now available in the Online Extensions Library. Note: Currently this extension has only been tested with ScreenConnect 5.4 or higher. Revisions are pending to address some requests. Disclaimer: This extension was written by our support team (and in some cases in conjunction with our forum community) in response to customer requests. Extensions are meant to be quick workarounds or immediate solutions to problems. Extensions are not supported under our normal terms of service, as these extensions are outside typical Q/A or development guidelines. Questions for extensions should be addressed in its respective forum post. Suggestions for improvements (enhancements or defects) should also be queued in the post for consideration. |
ScreenConnect Team |
 6 users thanked Mike for this useful post.
|
|
|
|
 Rank: Advanced Member Medals:   Joined: 5/15/2014(UTC) Posts: 68  Thanks: 8 times
Was thanked: 2 time(s) in 2 post(s)
|
Love it! Only thing is the box appears really small in Chrome 44:  Edited by user Friday, August 28, 2015 5:14:03 AM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Administration Medals: Joined: 5/30/2012(UTC)
Posts: 501
Location: Raleigh, NC
Thanks: 56 times
Was thanked: 82 time(s) in 68 post(s)
|
Orginally posted by jonmcknight Quote:Installed Screen Connect Version: 5.3.9074.5646Not working for simple reboot command: Error Message Returned: Code:System.ServiceModel.FaultException`1[ScreenConnect.SessionManagerFault]: Session group 'A' does not exist. (Fault Detail is equal to ScreenConnect.SessionManagerFault).
Am I using this incorrectly?  Edited by user Friday, August 28, 2015 3:02:58 PM(UTC)
| Reason: Not specified |
ScreenConnect Team |
|
|
|
|
|
Rank: Administration Medals:  Joined: 3/28/2014(UTC) Posts: 2,862  Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
I've just committed a fix to make this extension work correctly with previous versions of SC. @clickright I haven't been able to replicate that, though. Do you have a really long command by chance? ninja edit: the new version may take a few days to hit the Library. Edited by user Monday, August 31, 2015 2:50:29 PM(UTC)
| Reason: Not specified |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
Confirmed working in Version: 5.3.9074.5646. Thanks for the fix!
|
|
|
|
|
|
Rank: Advanced Member Medals:  Joined: 4/1/2014(UTC) Posts: 234 Location: Raleigh Thanks: 4 times
Was thanked: 16 time(s) in 12 post(s)
|
|
|
|
|
|
|
 Rank: Member Medals: Joined: 11/25/2014(UTC) Posts: 32  Location: Bogota Thanks: 25 times
Was thanked: 7 time(s) in 5 post(s)
|
How can I launch a tool from this command tool and show the gui on the client?
I need to do that because I have a Client with Active Directory and the "Run Tool" not work, becuase he have policies to dont save anything in the local hard drive. I have a network drive with some tools.
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Commands executed from the Host page cannot invoke applications/operations to the GUI. |
ScreenConnect Team |
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
To update this thread, version 1.31 is now available from the Extension Library. The two new features are the ability to Edit commands before you send them and the ability to provide a common name to identify the command.
In the Extension's Settings, you'll notice that there are now two settings per command, CommandNameX can be used to identify a command. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
Looks great! Thanks Scott
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
I'm having trouble getting this to work on version 5.3.9074.5646 I have successfully installed the extension & configured a test command as shown below:  The "Command Toolbox..." option shows up on the righ-click menu on the Host page, but clicking on it does nothing in either Chrome or Firefox... Suggestions?
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 4/1/2014(UTC) Posts: 234 Location: Raleigh Thanks: 4 times
Was thanked: 16 time(s) in 12 post(s)
|
so nothing is in your command tab after running the command toolbox line? this is what i see when i run that command [img]null[/img] 
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Matt Highsmith  so nothing is in your command tab after running the command toolbox line? The problem is that I can not get the Command Toolbox to pop up & therefore I'm unable to run any commands. Like I said: KBrownConsulting wrote:The "Command Toolbox..." option shows up on the righ-click menu on the Host page, but clicking on it does nothing in either Chrome or Firefox...
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
The Command Toolbox works best with ScreenConnect version 5.4+, but it does have code to handle 5.3 and lower. I recommend going to 5.4 if you can, but I'll make a note to take a look at the 5.3 code to see what the issue is. |
ScreenConnect Team |
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
To update, I just uploaded a new revision, 1.34, which contains a fix for version 5.3 not showing the dialog on the Host page. As always, it might be a few days before it hits the Library. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Scott To update, I just uploaded a new revision, 1.34, which contains a fix for version 5.3 not showing the dialog on the Host page. As always, it might be a few days before it hits the Library. Thanks Scott. I just tested 1.34 & can confirm that the Command Toolbox dialog does now pop up on the Host page. Unfortunately there's now a second issue: It appears the extension is only looking at the command name & not the actual command itself in some circumstances. See below. Here's my Command Toolbox settings:  When I initially open the Command Toolbox from the Host page it pops up fine & shows the correct command:  But if I switch to the second command, it show the command name for both the name & the command. (And if I run the command it sends exactly what is shown to the client.)  Further, at this point if I switch back to the first command, that one is now messed up too:  Obviously the easy solution is to just set the command name to the command you want to use & for now that's what I'll do, but I thought you might want to be aware of the issue. (I won't be upgrading until 5.6 is released as stable as I haven't wanted to deal with the delayed auto-start that was introduced in 5.4) Thanks
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Doh! That was purely my mistake, a typo in the < 5.4 version code. I've fixed it and uploaded version 1.4, might take a few days to appear on the Library.
Thanks for pointing that out! |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Scott Doh! That was purely my mistake, a typo in the < 5.4 version code. I've fixed it and uploaded version 1.4, might take a few days to appear on the Library.
Thanks for pointing that out! Hope I'm not being impatient, but how long is "a few days"? I'm still not seeing the update... Also, is it possible to include shabang modifiers (like maxlength & timeout) in a Command Toolbox command? I've tried a bunch of different ways & at least in 5.3 nothing seems to work, which is actually a major limitation for me. (I know I can globally adjust those settings but it would be much nicer if I could define them on a command by command basis.) On a related note, would it be possible to allow the Command Toolbox to support multi-line commands? (This would probably resolve the shabang modifier issue as well as make the Command Toolbox much more flexible.) Thanks for considering it! Edited by user Thursday, March 10, 2016 12:05:57 AM(UTC)
| Reason: Grammar police
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@KBrownConsulting should be live now.
What have you tried with the shebang modifiers that isn't work? Can you post an example?
Also, the current iteration just assumes the textarea's contents are one entire string but I can look into allowing support for multi-line commands. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Scott @KBrownConsulting should be live now. Confirmed & verified it's working, thanks! Originally Posted by: Scott What have you tried with the shebang modifiers that isn't work? Can you post an example? Well really the only seemingly halfway decent idea I could come up with was concatenating the commands: Code:#timeout=60000 & MyAppThatRunsForALongTime.exe
I also tried just stringing the commands together: Code:#timeout=60000 MyAppThatRunsForALongTime.exe
As well as some random delimiters: Code:#timeout=60000, MyAppThatRunsForALongTime.exe
Code:#timeout=60000; MyAppThatRunsForALongTime.exe
Code:#timeout=60000 MyAppThatRunsForALongTime.exe
But they all resulted in the process instantly being killed: Quote:Killed after 0 milliseconds. Please let me know if you have any other suggestions! Originally Posted by: Scott Also, the current iteration just assumes the textarea's contents are one entire string but I can look into allowing support for multi-line commands. It would be amazing if you could figure out a way to allow for multi-line entries in the Command Toolbox configuration! It would definitely make the Command Toolbox more flexible & powerful! Edited by user Tuesday, March 15, 2016 3:41:29 PM(UTC)
| Reason: Spelling
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
It might depend upon what the exe is doing, as I just tested with a console exe with no UI output (it emails) using the following: Code:
#!ps
#timeout=90000
C:\Users\slinak\checkStuff.exe
Also, upon further investigation, you can use Shift+Enter within the textarea to effectively make the command multi-line. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Scott It might depend upon what the exe is doing, as I just tested with a console exe with no UI output (it emails) using the following: Code:
#!ps
#timeout=90000
C:\Users\slinak\checkStuff.exe
Also, upon further investigation, you can use Shift+Enter within the textarea to effectively make the command multi-line. We're still talking about the Command Toolbox extension right? Shift+Enter works great in the text box for the built-in "Commands" window but I'm trying to figure out how to send the #timeout= shabang as part of a Command Toolbox command without having to modify the command before sending it... Are you able to save your example code as a working Command Toolbox command??
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@KBrownConsulting Ahhhhh, I see the difference, my mistake. No, I was not entering the text into the 'Edit Settings' but rather into the text area itself. The Edit Settings menu right now only supports the text box as it exists currently, but I suppose a button within the Command Toolbox modal to Save/Overwrite might do the trick, I'll look into that when I get a chance. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Scott @KBrownConsulting Ahhhhh, I see the difference, my mistake. No, I was not entering the text into the 'Edit Settings' but rather into the text area itself. The Edit Settings menu right now only supports the text box as it exists currently, but I suppose a button within the Command Toolbox modal to Save/Overwrite might do the trick, I'll look into that when I get a chance. That would be really great, thanks.
|
|
|
|
|
|
Rank: Advanced Member Medals:  Joined: 10/28/2015(UTC) Posts: 46 Location: WA Thanks: 11 times
Was thanked: 5 time(s) in 5 post(s)
|
Hello,
Would it be possible to add the ability to do the follow?
-Be able to easily change the order of the commands in the toolbox. Maybe by Alphabetical or grouping or just up and down arrows.
-Provide two text boxes for each command. For example, if I want the command to first stop a service then start a service. I couldn't find a way to create a return so that the command could do each action separately without having two different command drop-downs. For example, net stop "spooler" net start "spooler"
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Cooper -Be able to easily change the order of the commands in the toolbox. Maybe by Alphabetical or grouping or just up and down arrows. I like this idea! At least the up & down arrows would be great! I'd definitely use them! +1 Originally Posted by: Cooper -Provide two text boxes for each command. For example, if I want the command to first stop a service then start a service. I couldn't find a way to create a return so that the command could do each action separately without having two different command drop-downs. For example, net stop "spooler" net start "spooler"
This is exactly what I asked for above. (Not multiple boxes but the ability to enter multiple lines for each command.) Scott said in his most recent message that he'd try to look into this. In the meantime though, you can accomplish your goals of stringing multiple commands together by simply concatenating them with the ampersand (&) character like so: net stop "spooler" & net start "spooler" Cheers Edited by user Friday, April 1, 2016 11:45:07 PM(UTC)
| Reason: Not specified
|
1 user thanked KBrownConsulting for this useful post.
|
|
|
|
Rank: Advanced Member Medals: Joined: 10/28/2015(UTC) Posts: 46 Location: WA Thanks: 11 times
Was thanked: 5 time(s) in 5 post(s)
|
Originally Posted by: KBrownConsulting Originally Posted by: Cooper -Be able to easily change the order of the commands in the toolbox. Maybe by Alphabetical or grouping or just up and down arrows. I like this idea! At least the up & down arrows would be great! I'd definitely use them! +1 Originally Posted by: Cooper -Provide two text boxes for each command. For example, if I want the command to first stop a service then start a service. I couldn't find a way to create a return so that the command could do each action separately without having two different command drop-downs. For example, net stop "spooler" net start "spooler"
This is exactly what I asked for above. (Not multiple boxes but the ability to enter multiple lines for each command.) Scott said in his most recent message that he'd try to look into this. In the meantime though, you can accomplish your goals of stringing multiple commands together by simply concatenating them with the ampersand (&) character like so: net stop "spooler" & net start "spooler" Cheers Thanks! I'll try that out. What I ended up doing is putting the commands into a bat file and that works fine. The Command Toolbox and the Run Tool features are awesome. They can be such a time saver.
|
|
|
|
|
|
Rank: Member Medals: Joined: 6/17/2013(UTC)
Posts: 29
Thanks: 10 times
Was thanked: 2 time(s) in 2 post(s)
|
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
@Scott - In the newly posted Extension: Set Session Properties From System VariablesI noticed the following: " The Extension Settings editor for this extension has been modified to allow Text Area type fields for these command entries to facilitate multi-line commands (script-style)."  Is there any way that functionality could easily be copied to this extension?!
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Thanks for noticing that, I'll make a note to change that to allow similar behavior in the command toolbox. |
ScreenConnect Team |
1 user thanked Scott for this useful post.
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
Hey Scott, any progress on text-area input, (multi-line commands) update?
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Nothing solid yet, it's still on my to-do list. The way it was implemented within that other Extension @KBrownConsulting mentioned is kind of hackish, I'm instead looking at potentially changing the Extension Runtime itself to provide a way for extensions to hook into native modals. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
I was just looking at some new commands I'd like to add to the Command Toolbox that would be simplified if multi-line entries were possible so thanks for continuing to consider this Scott.
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
I'm not super happy with the implementation, but I've added the ability to save multi-line commands to the Extension in version 1.43.21, which should be available for download from the Library already. The reason I'm not super happy with it is that it's far from intuitive, the multi-line commands are saved from within the Command Toolbox modal on the Host page, similar to:  Overloading the already-present Edit Extension Settings modal is only possible through some hackish copy-paste which isn't a very good method. We're still looking for ways to allow Extensions to hook into other modals, though. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
@Scott
I'm running ScreenConnect version 5.4.9675.5750.
I just updated the Command Toolbox extension to the new version 1.43.21. I immediately tested changing one of my commands in the manner you described. While it did save that command as a multi-line command, it also deleted all of my other commands.
Any thoughts?
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@jonmcknight ah, sorry about that but thanks for the report. I have temporarily reverted the version found in the Library to 1.4 so that I can find a fix. I can see what's happening so the fix should be relatively quick. |
ScreenConnect Team |
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Version 1.43.22 of the Command Toolbox has been published with a fix for the issue that @jonmcknight reported. Thanks again for the report. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
@Scott
I just updated the Command Toolbox extension to the new version 1.43.22. I immediately tested changing one of my commands in the manner you described. The bug that was deleting all other other commands is no longer present, however it is no longer saving the command as a multi-line command.
Any thoughts?
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@jonmcknight hmm, strange. It's saving the commands correctly as multiline from both my dev environment and our QA environment. What browser are you using? What version of SC and what OS for the SC server? |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 1/30/2015(UTC) Posts: 47 Was thanked: 7 time(s) in 5 post(s)
|
I'm running SC version 5.4.9675.5750 on Windows Server 2008 R2. I'm accessing SC from Google Chrome on Windows 7. I just got it to work, but I'm not certain how or what the problem was. After yesterday's 1.43.21 issue that deleted all but the edited multi-line command, my commands where as follows: 1~6 as "Default"
#7 as the multi-line command that I just saved.
8~10 as "Default" Later that day I edited command #1 to a normal single line command leaving me with the following commands: #1 as a custom single line command
2~6 as "Default"
#7 as the multi-line command that I just saved.
8~10 as "Default" I'm not sure which of the following two actions I just performed fixed the problem. I reset all commands/names to default, then I setup #1 as a custom single line command and #2 as a soon-to-be multi-line command.
I then saved my changes. After this I returned to the /HOST page, modified #2 to be multi-line saved the change and refreshed, (as I have done every time). When I rechecked command #2, I saw that it was multi-lined and that #1 had not been deleted. So it appears that everything is good now. Edited by user Wednesday, May 11, 2016 4:08:21 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
First, thanks for working on this Scott. It is appreciated!
Unfortunately I think I found another bug.
Basic functionality seems to work in that I can save multi-line commands, reload the page & they are still there, still work & no other commands have been messed up.
BUT if I then go back to the Extension settings to add a new command, as soon as I save the extension settings all the carriage returns seem to get wiped out for the multi-line command & it no longer works.
SC 5.3.9074.5646 running on Windows 2012 R2
Browser: Chrome on Windows
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
@KBrownConsulting what you describe is exactly why I wasn't too happy with how I had to implement this. The ability to save multiline-commands is only possible from the Command Toolbox modal on the Host page because the textarea field. The Edit Extension Settings modal uses an input element of type text which doesn't respect the newlines.
We're still looking for a good, clean way to hook into current modals in order to modify their behavior. But, until then, this is about as good as it gets without having to change a significant amount of stuff around or implement a hackish alternative. |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
That's what I was afraid you'd say. Would it be possible to update not just the command itself but the name of the command from within the Command Toolbox modal on the Host page? If so, we could just enable ALL commands from the Extension settings page initially (with the unused ones having a name/title of "Unused") & from then on configure/update/add new commands from the Host page. It's ugly & hackish but no more so than the current implementation & does (more or less) solve the problem. But this train of thought actually brings up a security related question regarding the recently added functionality... Who is allowed to update the Command Toolbox commands using the new "Overwrite Setting" button? I haven't tested it, but if anyone who has the ability to use the Command Toolbox can update the command for ALL users in the system that presents the following security vulnerability: Scenario & attack: - Malicious Tech X is trying to gain access to a server that they do not have access to.
- Tech X has a legitimate SC account but is prevented from accessing the target server through properly configured SC user roles & session groups.
- Tech X is allowed to use the Command Toolbox.
- Tech X modifies an existing multi-line command that is commonly used by other SC users. Tech X appends/inserts commands that create a new local admin account as well as downloads & installs a remote administration tool of their choosing. If they wanted to try & hide their actions a little they could program in some logic into the commands so they only run against the target server.
- Tech X waits.
- Tech A who does have access to the target server runs the modified command on the target server as part of regular maintenance.
- Tech X now has full admin rights to the target server...
- Tech A would almost undoubtedly be unaware of the malicious changes for two reasons: 1 - The purpose of the Command Toolbox extension is to simplify/automate things & you don't want to have to audit the code before sending it every time. 2 - With the current modal dialog box that pops up on the Host page you can't even see the full text of the commands you are sending without manually expanding the size of the text box.
 Thoughts...?
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
As a follow-up thought... if this is indeed a concern, and one that might cause you to consider reversing the changes; instead of losing the feature altogether, maybe there could be an option added to the main Extension options controlling whether or not the "Overwrite Setting" functionality is enabled with a link to an explanation of the security considerations. (That way people like myself who are essentially a 1-man shop & don't have to worry about this issue can still take advantage of the multi-line capability immediately!)  Edited by user Thursday, May 12, 2016 10:15:40 PM(UTC)
| Reason: Not specified
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Quote:
Would it be possible to update not just the command itself but the name of the command from within the Command Toolbox modal on the Host page? If so, we could just enable ALL commands from the Extension settings page initially (with the unused ones having a name/title of "Unused") & from then on configure/update/add new commands from the Host page. It's ugly & hackish but no more so than the current implementation & does (more or less) solve the problem.
Potentially, I'm not quite sure which is the best route yet. Yesterday we discussed expanding the Extension Setting's definitions to allow authors to define the type of setting (or type of input required). This would mean that I would just say these settings should have a textarea input field and the modal would act accordingly. This route is relatively simple to implement and provides quite a lot of benefit; it could also allow other input elements like SELECT and/or radiobuttons. Also, I can certainly see where the concern is coming from with regards to your second issue. I guess that since you have to have access to the Extension tab in order to set any extension's settings that requiring Administrator permission to modify them from within the modal seems logical. I'll make sure to add that to the next release of this extension. Thanks for the feedback! |
ScreenConnect Team |
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/11/2014(UTC) Posts: 70 Thanks: 13 times
Was thanked: 8 time(s) in 5 post(s)
|
Originally Posted by: Scott Potentially, I'm not quite sure which is the best route yet. Yesterday we discussed expanding the Extension Setting's definitions to allow authors to define the type of setting (or type of input required). This would mean that I would just say these settings should have a textarea input field and the modal would act accordingly. This route is relatively simple to implement and provides quite a lot of benefit; it could also allow other input elements like SELECT and/or radiobuttons. That sounds like a great solution! I'd +1 that! Quote:Also, I can certainly see where the concern is coming from with regards to your second issue. I guess that since you have to have access to the Extension tab in order to set any extension's settings that requiring Administrator permission to modify them from within the modal seems logical. I'll make sure to add that to the next release of this extension. Awesome, thanks Scott!
|
|
|
|
|
|
Rank: Advanced Member Medals: Joined: 3/9/2011(UTC)
Posts: 112
Location: Lancaster, Pennsylvania
Thanks: 7 times
Was thanked: 2 time(s) in 2 post(s)
|
Command Toolbox doesn't seem to work in ScreenConnect 6.0.11299.6071. Choose a command and hit Run Command and nothing happens. The window just sits there until you close it and when you check the Commands on the computer nothing was sent to the computer.
|
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Version 1.45.1 of this extension has been released and works with 6.0 as well as previous versions. |
ScreenConnect Team |
|
|
|
|
|
Rank: Administration Medals: Joined: 3/28/2014(UTC) Posts: 2,862 Thanks: 3 times
Was thanked: 351 time(s) in 303 post(s)
|
Version 1.46 has been published containing a minor fix for overwriting non-sequentially saved commands. |
ScreenConnect Team |
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.
