TCL Prompt (AREV Specific) [Revelation On-Line Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
[[https://www.revelation.com/|Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community]]


==== TCL Prompt (AREV Specific) ====
=== At 04 MAR 2008 11:36:38AM Daniel Rebich wrote: ===
 
{{tag>"AREV Specific"}}
 
<QUOTE>
Looking for a way to disallow users from entering F5 and getting the TCL prompt.   I know you can disable it in the Environment menu, but, that affects everyone, I believe.  We still need the programming staff to be able to get to the TCL prompt.  Any help would be appreciated.



Thanks

Daniel
</QUOTE>
----

=== At 04 MAR 2008 02:25PM Aaron Kaplan wrote:  ===

<QUOTE>Environment settings are per AREV user.  There should be a record in SYSENV called username_ENVIRONMENT.  From SYSPROG, you can edit these in the settings window by hitting SF1.



If, for some reason, you don't have these records, you can easily copy them from an existing environment.

</QUOTE>

----

=== At 04 MAR 2008 05:12PM Victor Engel wrote:  ===

<QUOTE>The TCL prompt is just a window, and you can edit it just as you can any window. You could add security hooks to it to control access.

</QUOTE>

----

=== At 05 MAR 2008 10:26AM Michael Slack wrote:  ===

<QUOTE>We do something like what Victor suggests and that we've added a program to the TCL window that restricts which TCL commands a genereal user can use.  We restrict them from using any of the commands that can do damage to tables and such.  But it still lets them do LIST/SELECT, SAVELIST, GETLIST, DELETELIST and a few other safe commands.  Assuming that they've entered a command on the safe list, then it passes the whole command to the TCL process for execution.  Otherwise it gives them a message saying they can't use that command and sends them pack to the TCL window.



We have our own user account setup.  Our added TCL process looks at the user's account and determines if they can have full access or not.  If they should have full access then they can type in any TCL command.  If not, it restricts them to the safe list of commands.



We also have a couple of applications where TCL is turned off for everyone as a default.  But in the login process, it looks at the user's account and determines if they get TCL turned on or not.  In this case it's all or nothing.



I hope this helps.



Michael Slack

</QUOTE>

----

=== At 05 MAR 2008 11:26AM Dave Harmacek wrote:  ===

<QUOTE>I just copy the TCL window from SYSWINDOWS to WINDOWS COMMANDER.  Then I add security Restriction Level=1 and a Password to COMMANDER.  Then I add a W COMMANDER code and command to the Macro Set of the restricted Users.  Any time I need access while they are logged in with restrictions I just press the Macro key bringing up COMMANDER, enter the password and continue.



Dave

</QUOTE>

----

=== At 06 MAR 2008 08:55AM Daniel Rebich wrote:  ===

<QUOTE>Aaron,



Thank you, we were able to update the individual environment records for all of the users for which we wanted to restrict access to the TCL prompt.



I'd also to thank everyone for their suggestions.



Daniel

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=NONWORKS_READ&SUMMARY=1&KEY=0635F506767D2BB885257402005B3ED0|View this thread on the  forum...]]