Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
Notice: | Welcome to the Digital UNIX Conference |
Moderator: | SMURF::DENHAM |
Created: | Thu Mar 16 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 10068 |
Total number of notes: | 35879 |
Hi, I have a DUNIX 32G System with C2-Secutiry activated on it. 1.) I�ve set Triviality check to be "ON" in XIsso and in XSysAdmin 2.) in /etc/auth/system/default there is an entry: u_restrict (NOT u_restrict@) 3.) in /tcb/files/auth/x/xxx (xxx= <username> ) there is an entry: u_restrict (NOT u_restrict@) But triviality check is not working, WHY ? Thanks, Farah Salem [Posted by WWW Notes gateway]
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
9603.1 | Reported in QAR 47977 and note 4130 | NNTPD::"[email protected]" | Ann Majeske | Fri Apr 25 1997 13:23 | 6 |
It appears that this is a known problem, reported as part of QAR 47977 and in note 4130. To verify, is the problem you are having that some (but not all) of the triviality checks appear to not be implemented? [Posted by WWW Notes gateway] | |||||
9603.2 | which QAR status ? | NNTPD::"[email protected]" | Farah Salem | Mon Apr 28 1997 06:58 | 16 |
> It appears that this is a known problem, reported as part of QAR 47977 > and in note 4130. Which status does this QAR has? Is this Problem solved in DUNIX 4.0, Will it be solved in DUNIX 3.2X ? > To verify, is the problem you are having that some (but not all) of the > triviality checks appear to not be implemented? Yes, Very simple things like user name and English words are checked. Regards, Farah Salem [Posted by WWW Notes gateway] | |||||
9603.3 | QAR web page | NNTPD::"[email protected]" | Ann Majeske | Mon Apr 28 1997 11:51 | 9 |
You can check the status of the QAR from the QAR web page: http://webster.zk3.dec.com/webqar The XSysAdmin and XIsso interfaces were replaced by the dxaccounts interface in Digital UNIX V4.0 so it is possible that this problem is fixed in V4.0. But looking at the QAR, I can't tell if V4.0 has been tested for this specific problem. If it wasn't fixed in V4.0, it will be fixed in a future release. [Posted by WWW Notes gateway] |