Patch Name: PHSS_3580 Patch Description: s700 9.09 HP VUE 3.0 patch This patch corrects the following new problems. Vuelogin: - vuelogin is started at syshi. The user can specify a session sensitivity level at login, and the user's session will run at that single level, subject to restrictions implied by their clearance. vuelogin also sets the user's base privileges properly. Vuelock: - the lock on the front panel now runs the vuelock utility to lock the screen Vuefile: - objects dragged from the root "/" directory can now be thrown in the trash can Notes: A user must have the execsuid priv to start a terminal emulator, as these are setuid root. Users do not need other privileges to log into a VUE session. This patch DOES NOT fix the defect where root cannot telnet back to the same system. This defect will be fixed by a kernel patch, and is beyond the scope of this X windows patch. ***** You should run setfiles after loading this patch. Even though setfiles is run twice (2 times) in this patch's customize script, it doesn't seem to take. The patch changes the privileges of several of the X11 binaries. Path Name: /hp-ux_patches/s700/9.X/PHSS_3580 Effective Date: 94/01/07 OS Release: 9.09 Automatic Reboot?: No Critical: Yes PHSS_3580: ABORT CORRUPTION Patch Files: /usr/vue/bin/vuelogin (separate binary from vuge files below) /usr/vue/bin/vuelock (separate binary from vuge files below) /usr/bin/X11/xload /usr/lib/X11/sys.x11start /usr/bin/X11/X (the X server) /usr/lib/grmd (the graphics resource manager) /etc/newconfig/auth/system/FCDB/X11-RUN/files Note: the following files are actually multiple names for a single executable file containing all the VUE components. This patch will install the single binary (vuge_all) and thereby update all the listed files. /usr/vue/bin/helpview /usr/vue/bin/hpterm /usr/vue/bin/vueaction /usr/vue/bin/vueannotator /usr/vue/bin/vuecolor /usr/vue/bin/vuedialog /usr/vue/bin/vuefile /usr/vue/bin/vuegreet /usr/vue/bin/vuehello /usr/vue/bin/vueicon /usr/vue/bin/vuelock /usr/vue/bin/vuelogin /usr/vue/bin/vuepad /usr/vue/bin/vuesession /usr/vue/bin/vuestyle /usr/vue/bin/vuetypes /usr/vue/bin/vuewm /usr/vue/bin/xload SR#: None "what" string/timestamp: copyright: customize: $Revision: 1.8 $ files: grmd: (build date: Thu Jan 13 20:33:42 PST 1994) X Window System, Version 11 HP-UX 9.09 SRC_909 R5+ $Revision: 8.16 $ sys.x11start: vuelock: (build date: Fri Jan 7 12:48:31 PST 1994) X Window System, Version 11 HP-UX 9.09 SRC_909 R4+ HP Visual User Environment Version 3.0 A.03.05 vuelock: $Revision: 1.8 $ vuelogin: (build date: Thu Jan 13 20:40:14 PST 1994) X Window System, Version 11 HP-UX 9.09 SRC_909 R4+ HP Visual User Environment Version 3.0 A.03.05 vuelogin: $Revision: 3.14 $ HP BLS Authentication vuge_all: REV: 931129.092518, 9000/720 HP-UX A.09.01 masonbld@hpfcbite (build date: Mon Jan 17 10:12:55 PST 1994) X Window System, Version 11 HP-UX 9.09 SRC_909 R4+ HP Visual User Environment Version 3.0 A.03.05 vueaction: $Revision: 1.7 $ vuepad: $Revision: 2.1 $ vuestyle: $Revision: 2.9 $ vueicon: $Revision: 1.17 $ vuedialog: $Revision: 1.5 $ vuelock: $Revision: 1.8 $ vuefile: $Revision: 1.50 $ vuesession: $Revision: 2.30 $ vuewm: $Revision: 3.46 $ vuelogin: $Revision: 3.14 $ HP BLS Authentication vuegreet: $Revision: 3.12 $ HP BLS Authentication hpterm: $Revision: 2.103 $ helpview: $Revision: 1.3 $ vuehello: $Revision: 2.15 $ xload: $Revision: 1.6 $ vueannotator: $Revision: 1.10 $ vuetypes: $Revision: 1.4 $ HP libAt v 0.1 Tue Aug 11 12:30:28 EDT 1992 HP libAlib v 0.1 Fri Aug 21 09:13:26 EDT 1992 xload: (build date: Fri Jan 7 13:11:19 PST 1994) X Window System, Version 11 HP-UX 9.09 SRC_909 R5+ xload: $Revision: 1.6 $ "sum" output: 40645 6440 X 49996 6 files 24550 504 grmd 17378 6 sys.x11start 32250 112 vuelock 11396 1168 vuelogin 48440 11040 vuge_all 34923 264 xload Dependencies: If installed with PHSS_4425, PHSS_3580 must be installed first. Supersedes: None Patch Package Size: 9810 Kbytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. Note: Please back up your system before you patch. --------------------------------------------------------------------------- I. After getting the patch onto your machine, unshar the patch (sh PHSS_3580 where yyyy is the number of the patch). *** NOTE *** If you are patching a component of HP VUE, your system, and any cluster nodes, must NOT be running VUE at the time of the update. If you are not patching VUE skip to Section III. *** **** *** II. If you need to shut down VUE complete section II. If you are not patching VUE skip to Section III. On the cluster server and each of the nodes do the following: 1) At the HP VUE login screen, choose the [No Windows] option. You should see a console login prompt. Press [Return] if you don't. 2) Login as root. 3) Type: /etc/telinit 2 4) Logout. You should see a console login prompt again. III. To install this patch do the following: 1) Run /etc/update (Note: you must be logged in as root to update a system). 2) Once in the update "Main Menu" move the highlighted line to "Change Source or Destination ->" and press "Return" or "Select Item". 3) Make sure the highlighted item in the "Change Source or Destination" window is "From Tape Device to Local System ...", then press "Return" or "Select Item". 4) You should now be in the "From Tape Device to Local System" window. Change the "Source: /dev/rmt/0m" to "Source: /tmp/PHSS_3580.updt" (this assumes that you are in the /tmp directory where PHSS_3580.updt has been placed). Note: You must enter the complete path name. 5) Press "Done". 6) From here on follow the standard directions for update. IV. If you need to restart VUE after patching one of its components complete this section. Again, on the cluster server and each of the nodes do the following: 1) At the console login prompt, login as root. 2) Type: /etc/telinit 4 3) Logout. After a few moments the VUE login screen will reappear. The customized script that update runs will move the original software to /system/PHSS_3580/orig. HP recommends keeping this software there in order to recover from any potential problems. It is also recommended that you move the PHSS_3580.text file to /system/PHSS_3580 to be retained for future reference. If you wish to put this patch on a magnetic tape and update from the tape drive, dd a copy of the patch to the tape drive. As an example the following will create a copy of the patch that update can read: dd if=PHSS_3580.updt of=/dev/rmt/0m bs=2048 ============================================================================ ============================================================================ ============================================================================ This patch contains the following post 9.0 fixes: PHSS_3111 93/09/14 Vuelogin: - X-terminal accounting that was introduced in the August Periodic Patch (PHSS_2903) caused a problem with the "finger" program. This problem has been corrected plus a resource was added to disable X-terminal accounting if desired. To do so, set... Vuelogin*networkDevice: None in /usr/vue/bin/Xconfig. (SR #5003149302) PHSS_2903 93/08/01 Vuefile: - After putting a directory on the Desktop, the OpenNewView action doesn't always work. - Vuefile could abort when restoring a session with a view of the root directory. (SR #1653054312) - Vuefile doesn't pass the correct file name to Vuepad if the language locale uses 16-bit characters. (SR #5000693168) Vueicon: - Polyline/Polygon operations will sometimes leave a bogus rubber-band line scrag. - The File Selection dialog file list was not always current when the dialog became mapped. Vuelock: - Vuelock can be unlocked via an external client. (SR #5003123794) Vuelogin: - *** NEW FUNCTIONALITY *** Vuelogin now updates the accounting files, /etc/utmp and /etc/wtmp for X-terminals. (SR #5003074138 SR #5003122651 SR #5003094086 SR #5003037911 SR #5003119198) - *** NEW FUNCTIONALITY *** The default font path for X-servers started by Vuelogin can be augmented via Vuelogin resources or environment variables in /etc/src.sh. - *** NEW FUNCTIONALITY *** The display name can now be included in the login screen greeting message. (SR #5003123489) - The login matte could not be repositioned by specifying x,y coordinates. (SR #1653057844) - If a user's home directory is across a down NFS hard link, the login screen will freeze until the link returns. (SR #1653048835) - Vuelogin fails when the user has a restricted shell. (SR #1653042176) - Setting the LC_ALL variable the same as LANG prevents overrides of individual settings of LC-* variables. Vuesession: - If a user's session resource file happens to contain a cpp(1) reserved word, the file is processed incorrectly. (SR #5003114991) - VUE locks up if the user's $HOME/.vue directory is removed in the middle of a session. Vuepad: - Vuepad will silently corrupt a file if it runs out of disk space. (SR #5003120790 SR #5003116269) Vuewm: - When one of the "tar" actions (pack, unpack, list) prompts for input, the user's response is not echoed to the terminal window. (SR #1653053629) - Action dialogs generated from the front panel are unreadable on monochrome systems. (SR #4701139840) - A subpanel that is too tall to slide up gets out of sync and refuses to post after a while. (SR #1653054965) - Menu bar menus from a maximized, moved window do not post in the correct location. (SR #5003135715) PHSS_2616 93/06/01 Hpterm: - Focus can be lost after posting a Motif menu. (SR# 5003113043) - User cannot set the SWTCH char. using the ttyModes resource or -tm command line option. (SR# 1653041160) - Replies to a selection request may contain invalid information, potentially causing loss of data or core dump. - Can abort when a PS2/DIN keyboard is used. Vuefile: - Aborts if user's $HOME directory is /nfs//$HOME, an action is dragged to the desktop, and then the action is executed. - Unable to display more than 1000 files in a single view. (SR# 5003121178) - User can get access to parent directory in restricted mode. (SR# 1653051243) Vuelogin: - *** NEW FUNCTIONALITY ***. X-terminals can bypass the login screen and log directly into a user's session at power-up, except for the root user. To enable this functionality, add a line to /usr/vue/config/Xaccess: BYPASS_LOGIN - Did not reliably determine if an X-terminal is powered off. Vueicon: - May abort when grabbing an image on a display with more than 256 colors. - Aborts on a s700 with the "-f" option and a file name without a "/" - Aborts on an X-terminal when the screen capture width or height is zero. Vuesession: - *** FUNCTIONALITY CHANGE ***. Vuesession no longer restores the user's saved font path at session startup. This allows the system administrator greater flexibility in managing font paths and font servers for multiple users. The previous behavior can be restored by setting the resource, "Vuesession*saveFontPath: True" - *** NEW FUNCTIONALITY ***. The script "$HOME/.vue/sessions/sessionexit" can be invoked at logout similar to "sessionetc" at login. Vuestyle - Memory problem causes random, but infrequent, aborts. Vuewm: - Freezes if a user's mail file is across a hard NFS link and the link goes down. (SR# 5003113647) - Doesn't install the correct number of colormaps with respect to WM_COLORMAP_WINDOWS PHSS_2235 93/04/01 Helpgen: - Titles for non-IsoLatin help volumes are displayed with an IsoLatin font. - Helpgen always displays the message for Vuehelp 2.01 in english. Hpterm: - Problems with backspace in Japanese language. - Problems with Katakana characters in title of mwm window - Security hole associated with logging. - Hpterm does not automatically lock the keyboard when a data transfer handshake is pending. This can cause problems for certain user-written blockmode applications. - 16bit characters that fall in a certain position of the input stream will (when logging is used) have the first byte logged twice. - If hpterm is killed with many misc signals, it will not cleanup the /etc/utmp entry. Vueannotator: - The algorithm used to determine playhead pixel color is indeterminate. - Annotator help windows don't have the correct decoration. - Zoom-in on waveform can cause XtWarning messages to appear in a terminal window. - If an audio connection is broken, the 'Stop' button won't unpost the audio preview dialog. - Saving a file with an existing, non-writable name causes 2 error dialogs to be posted. - No error dialog is presented if a bad host name is given during a file save. Vuedialog: - The "default" button highlight should be disabled when the focus is in a text field which maps the Return key to focus traversal. - If -signal is not specified, the default should be SIGUSR1, not NULL. - Help dialogs do not have a window manager menu. Vuefile: - Using "*XmList.items" or "*XmList.itemCount" can cause vuefile to abort. - If $HOME=/nfs/, views sometimes are initialized to an erroneous current directory line. - Renaming a file in one view does not update the same file in another view. - Unmapped views are automatically updated even though they are not visible. This degrades performance. - Workspace names with a quote (') confuses desktop management. - If Vuewm is not ready, all desktop objects are restored to workspace #1. - If a user tries to put an object on the desktop while in directory graph mode, and the object comes from a directory above what the view feels is its current view, the object won't stick. - If a user puts a root directory on the Desktop then does a save and restore, the root directories won't restore to the Desktop. - Freeing up cached icons can cause vuefile to abort in extreme cases. - If the user has a save settings file that they had saved previously, and brings up a new view based on this save settings file, the help volume name read in can be corrupted. - If a user changes the files filter by using the Modify Filter list dialog, those changes aren't propagated to a new view based off of this file manager view. - If the "openDir:" resource is set to NEW, doubleclicking on the current directory line can bring up more than one view. - If the -title option is used and the root directory is displayed, the root title is used rather than the -title value. - Vuefile does not honor "*openDir: NEW" in a saved home session. - Creating the "Change To" dialog can cause vuefile to abort. - When using "openDir: NEW", "desktopIcon: small", and a different icon to represent an open directory, icons on the desktop are messed up. - Multiple selected items don't always get removed from the desktop at once. - Setting umask doesn't change permissions on a "New File" creation. - The File Manager will not allow a link to be created to / (root). - If the "restrictMode" resource is True, the user could get in a state where the ..(go up) directory is shown in the restricted directory and the user is allowed to go there. - If the "showFilesystem" resource is False, and the user goes to directory graph mode, then back to single directory mode, the current directory text widget is still posted. - When the "openDir" resource is True, or "showFilesystem" is False, or "restrictMode" is True, vuefile may abort. - If there is an icon on the desktop which came from a toolbox and "Open File's Folder" is selected, the new toolbox view doesn't get the correct geometry. - If the number of workspaces changes between sessions, desktop objects without a workspace are restored to workspace one, then disappear. - Detecting whether the "." or ".." directories are annotated does not work. - If the user click on an icon in the File Manager and then fairly quickly clicks on another icon anywhere else in the File Manager view, the original icon's colors aren't set back to their normal colors. - If the user renames something on the desktop then doubleclicks it, the default action will happen twice. - If the "restrictMode" resource is True and the grid is off, the ..(go up) icon is present when viewing the top most directory of the restricted directory. - If a user invokes an action to run a session with a session file, the current desktop objects are cleared first. With the fix, any desktop object which is being restored is additive. - Checking the links of desktop objects puts a heavy load on CPU. - When the user dragged a file from the desktop or from a file manager view to the trash, the same message was output. The code now puts out different messages depending on where the file was dragged from. - After a session save/restore, the toolbox icon was wrong. - When a user is super user and throws a symbolic linked file in the trash can, the .~ file created for the trash is created as a hard link rather than a soft link. This can lead to having extra files laying around. This also happens when renaming a file. - When a user brings up a File Manager view and then the Find dialog, the directory searched is the directory view shown in the File Manager view. If that directory is a symbolic link and the user wishes to search for something in that directory, it won't find it unless the Follow Links: option is turned on. - In the 'Find' dialog, the 'File Contents' text field has filename completion enabled; this prevents the user from searching for a string containing any spaces (i.e. "From: test"). Vueicon: - Dialogs are more consistent. - Getting "Help" on "Using Help" doesn't work correctly. - The "Exit" menu item under the File menu did not display the "x" mnemonic. - File name dialogs disappear if a bad file name is entered. - If vueicon is started with a file in iconic state, the icon title does not have a file name. This could happen if vueicon is restored from a session or when started iconified with the -f option. Vuelogin: - The prompt for aged passwords is unreadable if the current language is a multi-byte language. - If [No Windows] mode is selected from the [Options] menu, the ITE sometimes doesn't reset and show the normal "login:" prompt. - Vuelogin may not restart if the system clock is moved backwards. - Vuelogin does not correctly parse languages with locales selected from the [Languages] menu when setting up the fonts to use for the login screen. - Names longer than 20 characters cannot be entered into the login field. Vuepad: - If a large amount of text is pasted into the text widget with word wrap on, vuepad will abort. - Lines wider than the window which contain tabs beyond the right edge of the window do not display correctly. - If vuepad is started with a path-relative filename as a command line argument, then its "Print" action will fail. The action (i.e. vuecommand) will post an error dialog saying that it cannot find the file. Vuesession: - Vuefile does not get workspace information if Vuewm takes a long time to come up. - App-defaults file used was /usr/lib/X11/app-defaults/Vuesession rather then /usr/vue/app-defaults/Vuesession. Vuestyle: - If you select the "Color" item, then select "Add...", and then press "OK", without ever entering a name into the prompt dialog, an error dialog is posted containing nothing but an icon and an OK button; no error text is displayed. - If the window manager is restarted, the colors of "Backdrops" dialog no longer change when you move from workspace to workspace. Vuewm: - The "positionIsFrame" resource is ignored for programmatic moves. - Mwm f.raise_lower on Btn1 with xload/xclock doesn't work correctly. - Caps Lock does not have an effect when f.action invokes an action. - If you have a subpanel with embedded clients that never gets managed, then you will get an extra client in your session when you save the session. (Two copies of one of these embedded clients gets saved.) - Vuewm aborts performing a certain sequence of icon and workspace manipulations. - Entering a very, very long workspace name (>= ~1000 char) aborts Vuewm. - FP Control - may core dump if icon not found. - FP Busy - not allowed in primary box. - FP Subpanel - literal strings modified (ESlit core dump) - FP Box - secondary with busy requires another larger box. - FP Date - date in second row way too big if no "%n" in format - FP Date - old date not cleared when date changes (secondary box) - FP Date - extra width for some dates (VGA only) - Deep pixmaps don't work as icon images. - FP Mail - push_recall duplicate is mismatched after click. - FP Busy - Controls lost if secondary row is on top. - FP Date - second line is clipped in subpanel. - FP Client - client geometry off by 2 (secondary, subpanel). - FP Control - help precedence is inconsistent. - FP Panel - default colors are disallowed if no color server. - Posting a subpanel too tall to fit between front panel and screen edge, unposting it, then iconifying and uniconifying the front panel several times can cause strange subpanel behavior.