On 4/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Matt;
>
> The key to security is tying the user to the Kernel Shell and never
> letting the user get to the GTM prompt. If you get to the MUMPS prompt
> outside the application, you can do just about anything.
>
> In an application environment, any attempt to break out of the application
> should result in the generation of an error trap and the manditory HALT to
> drop them out of MUMPS and hopefully off of the machine.
>
> Best wishes; Chris
>
>
Here is an example of how to tie the login on unix/linux to login on
GT.M. It includes codes to prevent CTRL-C breakout.
Kevin
[EMAIL PROTECTED] vista]# cat .bashrc
# .bashrc
# User specific aliases and functions
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
#set up infinate loop
while [ 1 -eq 1 ]
do
sh runvista ^ZU
done
exit
------------------------------------------------------
[EMAIL PROTECTED] vista]# cat runvista
#!/bin/bash
echo " "
echo "GT.M VistA Startup Script"
. /var/local/OpenVistA_UserData/setup_vista_env
echo "Entering GT.M system now... "
#-----------------------------
stty susp \000
if [ $# -gt 0 ]
then
echo "Automatically launching program: $1"
$gtm_dist/mumps -r $1
else
$gtm_dist/mumps -dir
fi
#$gtm_dist/mumps -dir
echo " "
echo "Leaving GT.M, returning to Linux..."
echo " "
------------------------------------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Hardhats-members mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/hardhats-members
