# set PS1 with system name, the history
# number (ksh) and last bit of the current
# directory (truncated so it won't be
# too long to fit on the screen. Format
# the whole thing as vbl=value; so that cut
# and paste works export SYSNAME=`uname -n` export PS1='$SYSNAME=!_${PWD#${PWD%/*/*/*}/}; '
# Set PS2 to be cut and paste friendly export PS2=' '
# Set window titles if xterm or dtterm and
# change PS1 to be more streamlined (since
# other info in window title)
case "$TERM" in
xterm|dtterm)
export startHeader="$(print '\033]2; ')" export endHeader="$(print ' \007\c')"
export startIcon="$(print '\033]1;')"
export endIcon="$(print '\007\c')"
PS1='${startHeader}$LOGNAME@$SYSNAME: ${PWD#${PWD%/*/*/*/*}/}${endHeader}${startIcon}$LO GNAME@$SYSNAME${endIcon}^M$SYSNAME =!; '
esac
# set PS1 with system name, the history
# number (ksh) and last bit of the current
# directory (truncated so it won't be
# too long to fit on the screen. Format
# the whole thing as vbl=value; so that cut
# and paste works
export SYSNAME=`uname -n`
export PS1='$SYSNAME=!_${PWD#${PWD%/*/*/*}/}; '
# Set PS2 to be cut and paste friendly
export PS2=' '
# Set window titles if xterm or dtterm and
# change PS1 to be more streamlined (since
# other info in window title)
case "$TERM" in
xterm|dtterm)
export startHeader="$(print '\033]2; ')"
export endHeader="$(print ' \007\c')"
export startIcon="$(print '\033]1;')"
export endIcon="$(print '\007\c')"
PS1='${startHeader}$LOGNAME@$SYSNAME: ${PWD#${PWD%/*/*/*/*}/}${endHeader
}${startIcon}$LOGNAME@$SYSNAME${endIcon}^M$SYSNAME =!; '
esac
Anothe HIPPA issue is that the "responsible party" is liable for a $1,000 fine for each medical record released to the public, up to $250,000. This is not a corporate fine. This is a personal fine. Make sure you're not consider the "responsible person." As far as the strength of passwords, they're pretty good unless they're flying over the net unencrypted (which it sounds like they're not) or if the back-end password database is compromised. The advantage of digital certs is that the backend database only has the 'public key' part, so there's nothing to compromise. I'd still use two-phase though (user name and cert, for example). Another issue is that you can't just allow people to come into the system with their "membership number" and request a passworded account, or some such. You need verification that they're who they say they are before you hand them an online account.
Slashdot Mirror
# set PS1 with system name, the history
# number (ksh) and last bit of the current
# directory (truncated so it won't be
# too long to fit on the screen. Format
# the whole thing as vbl=value; so that cut
# and paste works export SYSNAME=`uname -n` export PS1='$SYSNAME=!_${PWD#${PWD%/*/*/*}/}; '
# Set PS2 to be cut and paste friendly export PS2=' '
# Set window titles if xterm or dtterm andO GNAME@$SYSNAME${endIcon}^M$SYSNAME =!; '
# change PS1 to be more streamlined (since
# other info in window title)
case "$TERM" in
xterm|dtterm)
export startHeader="$(print '\033]2; ')"
export endHeader="$(print ' \007\c')"
export startIcon="$(print '\033]1;')"
export endIcon="$(print '\007\c')"
PS1='${startHeader}$LOGNAME@$SYSNAME: ${PWD#${PWD%/*/*/*/*}/}${endHeader}${startIcon}$L
esac
# set PS1 with system name, the history # number (ksh) and last bit of the current # directory (truncated so it won't be # too long to fit on the screen. Format # the whole thing as vbl=value; so that cut # and paste works export SYSNAME=`uname -n` export PS1='$SYSNAME=!_${PWD#${PWD%/*/*/*}/}; ' # Set PS2 to be cut and paste friendly export PS2=' ' # Set window titles if xterm or dtterm and # change PS1 to be more streamlined (since # other info in window title) case "$TERM" in xterm|dtterm) export startHeader="$(print '\033]2; ')" export endHeader="$(print ' \007\c')" export startIcon="$(print '\033]1;')" export endIcon="$(print '\007\c')" PS1='${startHeader}$LOGNAME@$SYSNAME: ${PWD#${PWD%/*/*/*/*}/}${endHeader }${startIcon}$LOGNAME@$SYSNAME${endIcon}^M$SYSNAME =!; '
esac
Anothe HIPPA issue is that the "responsible party" is liable for a $1,000 fine for each medical record released to the public, up to $250,000. This is not a corporate fine. This is a personal fine. Make sure you're not consider the "responsible person." As far as the strength of passwords, they're pretty good unless they're flying over the net unencrypted (which it sounds like they're not) or if the back-end password database is compromised. The advantage of digital certs is that the backend database only has the 'public key' part, so there's nothing to compromise. I'd still use two-phase though (user name and cert, for example). Another issue is that you can't just allow people to come into the system with their "membership number" and request a passworded account, or some such. You need verification that they're who they say they are before you hand them an online account.