| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 10020.1 | answers | SMURF::MAJESKE | | Tue Jun 03 1997 12:37 | 24 |
| > 1. Automatic termination of login session upon a predefined period of user
> inactivity (e.g. 20 minutes)
no
> 2. Prohibits multiple login by a single user ID, ie. cannot login if
> you have
> one login session active already.
This should be fairly easy to do with a script, small program, and/or
captive login. Digital UNIX doesn't have this capability built in.
> 3. Revoke user ID that has been inactive for a certain period.
This is available with Enhanced Security enabled. There is more
information available in the Security manual and the prpasswd(4)
manpage.
> 4. Solution on data encryption for information passing through the
> subsystem
> interfaces and network including PCs
I'm not sure what you mean by this. There are layered products you can
use to encrypt data being sent over the network. Pathworks can be used
to communicate with PCs, I don't think it currently has encryption
or secure communications capabilities, but maybe you can use something
in combination with it.
|
| 10020.2 | Re: question 4 | TLAV02::16.158.208.72::SOMNUK | | Tue Jun 03 1997 13:30 | 13 |
| Hi,
Re: question 4. I think the customer want to
encrypt the data before send it to PCs or any
other system on the network and have the destination
decrypt the information or vice versa.
Do we have any product add-on to this?
Thank you for answering
Regards,
Somnuk
|
| 10020.3 | | BIGUN::nessus.cao.dec.com::Mayne | Meanwhile, back on Earth... | Tue Jun 03 1997 18:04 | 3 |
| AltaVista Tunnel?
PJDM
|
| 10020.4 | autologout | NNTPD::"[email protected]" | Brian Haley | Tue Jun 03 1997 19:07 | 20 |
| Hi,
csh does provide an autologout feature, but it might not be what you
want for a security environment because users can override it from
the command line if they know about it. It also has limitations on
what types of sessions can be auto-logged-out.
# set autologout=20
will set a 20 minute logout timer.
# set autologout=0
will disable it.
I believe every users default is 60, changing that would require putting
it in their .cshrc.
-Brian
[Posted by WWW Notes gateway]
|
| 10020.5 | example to stop multi logins | SEPPLT::MARK | Mark Garrett | Wed Jun 04 1997 04:11 | 13 |
| #!/bin/ksh
#
#
typeset -i logins=0
#
logins=$( w | grep "^${USER} " | wc -l )
if [ $logins -eq 1 ]
then
echo "This is your first login for ${USER}"
else
echo "your are now logged in more than once"
echo "I should not let you do this"
fi
|
| 10020.6 | How to integrate with the login process? | TLAV02::16.158.208.51::SOMNUK | | Wed Jun 04 1997 08:59 | 26 |
| Hi,
>#!/bin/ksh
>#
>#
>typeset -i logins=0
>#
>logins=$( w | grep "^${USER} " | wc -l )
>if [ $logins -eq 1 ]
>then
> echo "This is your first login for ${USER}"
>else
> echo "your are now logged in more than once"
> echo "I should not let you do this"
>fi
How do we integrate this script with the login
process? That is, when user get their login name and
password correct, then this shell get execute.
This script should not let the user modify or embeded
in the user profile (.profile, .cshrc, etc.)
Thanks you
Regards,
Somnuk
|