| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 491.1 | | MARVIN::PALKA | | Tue Jun 09 1987 06:24 | 14 |
|
You can put security alarms on your files, but they can easily be
side stepped by a privileged user.
Any privileged user can change his UIC or grant any identifiers
to himself to allow access to your files no matter what you put
in the ACL. (I think BYPASS privilege will always bypass ACLs anyway).
A privileged user can always pretend to be you, in such a way as
to fool any security system you can put on a file. If you can't trust
privileged users then you have to encrypt your data (and even then
a dedicated hacker might be able to find the encryption key when
you use it to decrypt the file).
Andrew Palka
|
| 491.2 | | ERIS::CALLAS | I have nothing to say, but it's okay | Tue Jun 09 1987 10:26 | 11 |
| Well, yes and no. If someone's masquerading as you, then there's
nothing you can do (except catch them at it -- and it's a firing
offense) to keep them from looking at them, but you *can* put an alarm
on your files that fires on a successful access.
You can also set up auditing to trace use of amplified privileges. You
can track the use of BYPASS, GRPPRV, SYSPRV, and READALL. You can also
get fine-grained enough to (say) read or write access via BYPASS. See
the manual (or help file) for SET AUDIT/ENABLE.
Jon
|
| 491.3 | There are ways... | UTRTSC::GUEDHA | Is infertility hereditary? | Thu Jun 11 1987 09:23 | 22 |
| Giving them false names works as good a way as any. Nobody ever
tries to type a file with an extention .EXE.
On the other hand you can use patch to give them an illegal filename
Like *.*. If you keep a large executable file with who's name and
extention are ASCII codes less than 42 but greater that 31 then
they cannot type it out using TYPE %.%
I have used the latter method (under TOPS-10) for years, it drives
the operators mad.
An other method is to leave a nice interesting looking file which
contains the escape code sequence that kicks of the auto test sequence
on a terminal. As I remember there is one sequence that locks the
terminal in the test loop until it is powered off. There are many
"nice" escape sequences that screw up terminals. I recomend the
handbook of the terminal that is used by the snooper may make very
interesting reading.
Have Fun,
Jamie Anderson.
|
| 491.4 | ^S' them off ! | PILOU::BONGARTZ | Happy Hacker | Fri Jun 19 1987 04:40 | 8 |
|
Another method I use to drive them mad is give a file name like
"privileged_account_passwords.txt" containing a header, then the
messages "* OUTPUT OFF *", "* INPUT OFF *", and a ^S ...it locks
your terminal until you do a "clear comm" (vt2xx) or go into
setup (VT1xx) ...
Marc
|