[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

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

8763.0. "Cannot get into system after Pause Screen, v3.2D-1" by RULLE::BRINGH () Sun Feb 09 1997 11:44


Hi


A customer has an interesting problem. If he pause Xwindows and type the
wrong password then he cannot get in, no matter what he types. They are
running DigitalUNIX v3.2D-1 on three ASRV1000 systems and they are running
C2-security. The tests we tried was, pause screen and type correct password
and we get in. Type wrong password, backspace and type the correct password
and we are in again. But type the wrong password and send it with <Enter>,
get the error Incorrect password, try again error message and after that it
doesn't matter what we type. Try this logged in as root and we don't have
the problem. I don't think the problem is related to C2 since we can log in.
The problem does not seems to be related to caps lock since we can log in.
And I don't think it is related to backspace producing funny characters since
we can type the wrong password and erase it and type the right one and get in
as long as we dont hit enter. I believe this is a permission/owner problem.
Any suggestion to where? The customers work around has been to kill whatever
X-related processes owned by the user that he has found. What I have not done
yet is a fverify on installed Xwindows kit. The customer can reproduce the
problem on all three systems while we cannot reproduce it here.

Any suggestions?

Regards,

Mikael Bringh
Unix-gruppen, TSC, Sweden

T.RTitleUserPersonal
Name
DateLines
8763.1solved, problems with dxpause and C2 enhanced securityRULLE::BRINGHTue Feb 11 1997 08:1417

As I looked into this a little bit more and realized that when I pause the
screen I actually start an application, dxpause. Then it wasn't so hard to
find notes about problems with dxpause and C2 enhanced security, note 5040.0
in this conference for example.

I only had to turn on C2-security and I had the same problem on my system.
The patched dxpause and DXpause.uid that can be found at anonymous ftp,
alpha.zk3.dec.com, pub/ootb/1367_pause/3.2C (can also be used for v3.2D-1)
solved the problem on my system.



Mikael Bringh
Unix-gruppen, TSC, Sweden