************************************************************* Razor 5.1.03 Release Notes ************************************************************* Table of Contents 1. General Installation/Upgrade Considerations 2. Razor Users Upgrading from 4.3c/4.3c.01: - Changes to Razor Password File 3. Important Notes: - Windows 2003 SP1 Posix subsystem issue - HW Data Execution Prevention and Razor - Access_list file - Server Resources 4. Platforms Supported 5. General Release changes for 5.1.03 6. General Release Changes for 5.1 7. General Release Changes for 5.0 8. Release Notes for Razor 4.3e 9. Release Notes for Razor 4.3d 10. Upgrading from Razor 4.3a.05 and prior 11. Note for Razor SCC Users 12. Release Notes for Razor 4.3c thru 4.3b 13. Razor Security Issue in v4.1 *********************************************************** 1. General Installation/Upgrade Considerations WARNING: Customized/Modified scripts should be stored in the $RAZOR_UNIVERSE_DIR/Scripts directory, NOT the $RAZOR_HOME/scripts directory. During the upgrade/installation, any customized/modified scripts stored in $RAZOR_HOME/scripts will be overwritten! Before proceeding, move all customized scripts to $RAZOR_UNIVERSE_DIR/Scripts. 2. Razor Users Upgrading From 4.3c/4.3c.01 - User's upgrading from 4.3c/4.3c.01, and using the Razor password file must first upgrade to Razor v5.0 before upgrading to v5.1 or v5.1.03 - Changes to the Razor Password File A correction has been made to the password functions in Razor. Due to an indeterminate private key in the password algorithm, the 4.3c/4.3c.01 razor_password_file is incompatible with this and future versions of Razor. If you are currently using Razor 4.3c or 4.3c.01 and also using the Password feature, your Razor password file will be incompatible with this and all future releases. To avoid having to recreate the user IDs, you will be asked to execute a script that will save this information prior to upgrading Razor. The filename of the script is create_passwd_list. This script is provided in the "examples" directory of this release. For PC users, the script will be placed in the Razor_lm directory during the upgrade process. The create_passwd_list script will produce a temporary data file with all user IDs. This data file is used once by the license manager at startup to re-create your password file. The passwords for each user will be set to their user ID. Users will also be asked to re-set their passwords when they first login to the new 5.1 Razor release. Steps to follow in saving your user information and running the create_passwd_list script: UNIX/Linux Users ---------------- - Untar/unpack the Razor 5.1 tar file - From an sh, ksh, or bash command prompt, set your Razor environment variables by sourcing your rz_prep.sh file (ie. . /rz_prep.sh) - Verify that the Razor 4.3c/4.3c.01 License Manager is running (ie. use the "razor info" command) - Go to the Razor_5.1/examples directory and execute the following statements chmod 755 create_passwd_list ./create_passwd_list - Bring down the license manager and proceed with the installation Windows Users ------------- - Unpack/unzip the Razor 5.1 software and follow the prompts until you see the message concerning the Razor password file. The script will be copied to your Razor_lm directory at this point. Exit the installation process. - Start the license manager for Razor 4.3c/4.3c.01 using the Razor Admin GUI. - Open a Razor ksh window (Start->Programs->Razor->Razor ksh) - In the ksh window, execute the following commands: . /rz_prep.sh cd $RAZOR_LICENSE_DIR chmod 755 create_passwd_list ./create_passwd_list Proceed with the Razor 5.1 upgrade (remember to take down all databases and the License Manager before proceeding). NOTE 1: You must have permissions to read/write to the Razor_lm directory before running the create_passwd_list script. NOTE 2: After the upgrade, when you first start the 5.1 version of the license manager, the new Razor password file (named rz_pwd_file) will be created. When the user accounts are added, the username password will be the same. Also, the users will be required to change their password the next time they log in. NOTE 3: If your facility is using more than one License Manager and you are also using the Razor password file, the above steps must be completed for each License Manager. NOTE 4: If you have any questions/concerns please contact the Razor product support team at razor_support@visiblesystemscorp.com 3. Important Notes: - Windows 2003 SP1 Posix subsystem issue A bug exists in the Microsoft Windows 2003 SP1 Posix environment that impacts nearly all korn shell scripts. Consequently, the user will experience a core dump when executing many of the Razor commands. This problem is resolved by installing Microsoft hotfix #899522. Information on this situation and instructions on downloading the patch for this hotfix may be found at the following web site: http://support.microsoft.com/kb/899522/en-us All users of Razor on Windows 2003 SP1 must install this hotfix. - HW Data Execution Prevention and Razor Some computer vendors have begun shipping desktop and laptop PCs with hardware based data execution prevention (DEP) turned on. This change impacts Windows XP SP2 and Windows 2003 server machines. In some cases, DEP has the unintended consequence of preventing legitimate software from operating properly. Razor will not operate in a HW based DEP environment. Users must turn off the HW DEP (i.e. optout) in their boot.ini file in order to allow the Razor service to run. User's may find their DEP setting by checking the System Properties dialog under the Performace option of the Advanced tab. The message at the bottom of the Data Execution Prevention tab found in the Performace option will indicate the status of the hardware based DEP. The absense of a DEP tab indicates that you do not have any DEP based (sw or hw) support present on your PC. - Access_list file Users upgrading their installation of Razor may want to add the following entries to the Access_list file to control user access to the new file attachments feature in Issues. The entries to be added are as follows: ISSUE_ADD_FILE_ATTACH ISSUE_REMOVE_FILE_ATTACH ISSUE_VIEW_FILE_ATTACH ISSUE_EXPORT_FILE_ATTACH ISSUE_VIEW_FILE_ATTACH_HISTORY By default, all users are authorized to perform these operations if the corresponding entry is absent from the Access_list file. - Server Resources Some users who upgrade may require increased server resources. This is due to a greater number of Razor processes being spawned. We suggest testing Razor upgrades within a test environment before going 'live' on your production system. Please keep in mind that as your number of Razor databases, files, users, etc., grows, you may also find the need to upgrade server resources. For example, if you plan on using the new file attachments feature in Issues, please verify your system has enough disk space to accomodate this feature. Binary files such as PDF, Powerpoint, Excel, etc normally take up much more space than text files. 4. Platforms Supported Razor 5.1.03 supports the following platforms: Solaris 2.5 (Sparc) Solaris 2.6, Solaris 7, 8, 9, and 10 (Sparc & Intel), HPUX (10.x), IRIX (5.x & 6.x), IRIX 6.5 (64-bit), AIX (3.x & 4.x), Linux (2.2.x, 2.4.x, 2.6.x kernels), Windows 2000/XP-SP1-SP2/2003 (client) and Windows 2000/XP-SP1-SP2/2003 (server and client). NOTE: Windows NT v4 is no longer supported. 5. General Release Changes for version 5.1.03 - (I2-852) Thread updates will no longer 'revert' a version of a file without the user's explicit permission. New entries have been added to the Options file to indicate the new settings. - (I2-896) Additional logic has been added to the server to honor RAZOR_TMP variable. The RAZOR_TMP environment variable must be defined in the rz_prep and rz_prep.sh files for each database which intends to use this value. - (I2-897) Corrected temporary files being left behind by the new Guiffy diff/merge sessions. - (I2-898) Modified the default setting for the Issue Activity window to so that entries are sorted by 'date'. - (I2-904) Added a new option to the Introduce window of ASCII (text) which allows the user to explicitly force a file to be stored as ASCII text. - (I2-905) Enhanced the Razor Versions tool to permit the diff/merge of files with embedded spaces in the name. - (I2-906) Corrected the situation where future updates of a thread do not include files from a renamed folder. - (I2-907) Fixed some general problems with the 'Razor csh' window; modified the Roles file so that RAZOR_ADMIN is set to '*'; updated the PC login windows so that :\ resolves to /dev/fs/; corrected the password update problems on the Razor Admin tool; Fixed certain XP SP2 hangs on LM start when username contains spaces - (I2-908) Updated the 'rz_new_database' script to also copy the Xdefault and Wdefaults file to the RAZOR_UNIVERSE area. - (I2-911) Corrected the condition where a thread import wipes out existing thread entries. The thread import feature will now 'add' entries to the existing thread definition. - (I2-914) Updated the Razor PC server and client to contain the new Guiffy v7.3 utility. This upgrade will help solve the situation where a demo license is loaded on systems with a non-standard desktop location. - (I2-916) Enhanced the Razor Versions tool to allow the user to always 'clear' the Title and Issue box prior to every checkin. The Xdefaults/Wdefaults files contain the new settings. - (I2-917) Corrected the situation where certain usernames cannot be added to the Razor password file. - (I2-918) Modified the rz_toolbox script so that the function razor_versions allows the use of CHECK-IN in the comments. - Added a new SCC integration to the Rhapsody software development envirnonemt by Ilogix (www.ilogix.com) - (I2-921) Corrected the problem in which remote clients (Windows+UNIX) are unable to use the Razor login GUI to update their *Razor* password. A notice/pop-up has been added to inform the user when the Razor password has been successfully changed. - (I2-923) Corrected failure of Razor Admin when razor password file non-existant. - (I2-924) Update reports to show "N/A" for a date attribute that is not set. - (I2-925) In Threads, fixed folder rename for file version rollback. - (I2-927) For Windows platforms, modify Installer to set execute permissions on the scripts, directory. - (I2-928) For Rhapsody users, correct problem that did not allow 'Include Decendants' when checking out a project containing recursive packages. - (I2-929) Upgrade installs leave 2 shortcuts to same thing just with different case in the names to put better worded shortcuts in the Start Menu. - (I2-930) Change RazorAdmin to show full version level in the status bar. - (I2-931) For remote Versions clients running under UNIX, the Guiffy tool was not finding the Guiffy OEM license in the user's HOME directory. This has been fixed. 6. General Release Changes for version 5.1 - (I2-529) A 'Print' button has been added to print out the Release Notes for Windows installs. - (I2-788) Razor has been updated to work with Posix 3.5 on Windows. POSIX 3.5 is bundled with Razor5.1 Server and will be automatically installed if POSIX 3.5 is not present on the Windows machine. The user may elect to install POSIX 3.5 prior to installing Razor5.1 Server by downloading it from the Microsoft website: (www.microsoft.com/windowsserversystem/sfu/downloads/default.mspx) POSIX 3.5 is a freely distributed product available from Microsoft. POSIX 3.5 requires that /dev/fs be added to the start of the pathname in order to reference directories and files within the Razor environment. NOTE: The windows version of IssueWeaver will now run under Microsoft's Internet Information Services (IIS) Web server in addition v2.x of the Apache Web Server. For additional information contact Razor Support. NOTE: During the upgrade process, databases found in the db_aliases file will be modified to work with the new POSIX 3.5 environment. NOTE: Previous versions of Razor will not run with POSIX 3.5. NOTE: At the conclusion of the install on Windows XP the process may fail to release the hourglass and automatically reboot. Should this happen, all you need to do is manually reboot the PC (i.e. CNTRL-ALT-DEL, restart) - (I2-809) Fixed Parent/Child dialog cancel button error discovered in version 5.0 of Razor. - (I2-835) Fixed the fault that occurred when canceling a thread extract from a Project. - (I2-842) Updated Razor to use version 3.0 of Easy Charts which supports generation of pie and bar charts. - (I2-854) Added 8 new scripts to the examples directory: export_issues - exports issue and attachments to local file. Should be attached to issues Commands pulldown. import_issues - prepares staging area with issue file created by "export_issues" into current issue group. Should be attached to issues Commands pulldown. issue_modify.before - calls process_child_issue.before and parent_issue_report - provides a report of currently open parent and child issues. Should be attached to the Commands pulldown. process_child_issue.before - Updates parent issue with child data (including state information) process_parent_issue.before - Insures parent cannot be closed while child issues are open. process_staging_area - imports all staged issues into current database. Run as a cronjob. view_log - shows import/export details. Should be attached as an Issues Commands pulldown. - (I2-860) Incorporated the third-party Guiffy tool for performing file differences and merges as well as folder comparisons. The Guiffy tool is fully integrated within the Versions client. Razor comes with an OEM license that gives the user permission to run Guiffy within the Razor product suite. Users may purchase a seperate license which allows them to run Guiffy outside of Razor. Windows: The Guiffy tool is bundled with the Windows Razor5.1 Server and the Windows RazorPC Client.The Guiffy tool is a Java-based application. The installer will install both the Guiffy tool as well as the applicable Java Runtime Environment (JRE). UNIX/Linux: The Guiffy tool is not bundled with Razor on non-Windows platforms. This product and the appropriate Java runtime engine (JRE) needs to be installed by the user. The product installer and the Java runtime engine may be downloaded from the Guiffy web site located at: http://www.guiffy.com The Guiffy product may be installed in the $HOME directory of the Razor admin account or alternatively in the Razor area under the $RAZOR_HOME/ThirdParty/Guiffy directory. The JRE is installed under the Guiffy tool installation so that it doesn't conflict an an existing JRE installation. The environment variable GUIFFY_HOME must be defined by the user prior to using the product. This is best accomplished by placing the environment variable in the rz_prep files. For more information on the Guiffy/Razor interface see Razor's FAQ on the Visible Web site (www.visiblesystemscorp.com) NOTE: Integration w/Razor requires Guiffy 7.0 build #165 or later. NOTE: Remote users of Razor on UNIX/Linux platforms will need to install a copy of the Guiffy tool for every client and set the value of GUIFFY_HOME to the installation directory. It may be installed in the user's $HOME directory. 7. General Release Changes for version 5.0 - (I2-242) Added functionality for "Live Links" between versions and issues. Live Links is an improvement to the integration between versions and issues. In previous releases of Razor, the Activity window was static. The addition of Live Links allows a constant connection between issues and the files that were changed for each issue. - (I2-430) When a laptop is not connected to a network the power saving features of the operating system typically shutdown the network interface card (NIC). This can cause the 'razor id' utility to obtain an (invalid) Razor licensing ID consisting of all zeros. This issue provides a workaround. - (I2-409) Corrected password message inconsistencies with Razor and IW. - (I2-451) Corrected bug in system_setup script for XP. - (I2-602) Corrected bug in shortcuts to versions and threads for XP. - (I2-648) In Issues, file attachments, corrected problem viewing an attachment with spaces in the file name. - (I2-663, I2-126) Threads, corrected bug with renamed files being dropped from a thread and/or not found by a thread script. - (I2-775) Newer Linux distributions lack 'compress' and 'uncompress' utilities. When manipulating binary files the Razor server will substitute 'gzip' for 'compress' and 'gunzip -c' for 'zcat'. Users may use scripts $RAZOR_UNIVERSE_DIR/Scripts/compress and $RAZOR_UNIVERSE_DIR/Scripts/zcat to override this behavior. Added definitions for '_COMPRESS_' and '_ZCAT_' to $RAZOR_HOME/scripts/system_setup for each OS. Scripts in $RAZOR_HOME/scripts and $RAZOR_HOME/examples now reference '$_COMPRESS_' and '$_ZCAT_'. - (I2-774) Added License Utility scripts, rz_start_license_debug and rz_gen_license_stats scripts to the $RAZOR_HOME/examples directory. a) rz_start_license_debug is a Bourne shell script used to start the Razor license manager in "debug" mode. The output from the log statements are captured in a log file. The log file is saved in the $RAZOR_LICENSE_DIR/Logs directory. b) rz_gen_license_stats script is a Perl script used to analyze the log file and generate statistics. The output is displayed to the screen. This script depends on the Time::Local Perl module. The script also accepts several command line parameters including the log file name. The script expects Perl to be loaded at /usr/bin/perl Additional information on the statistics tool can be accessed by running the script with the "help" option. rz_gen_license_stats -help 8. General Release Changes for version 4.3e/4.3e.x ******** Changes for 4.3e.03 *********** - (I2-722, S.20-994) For versions, corrected a bug with merging a trunk and a branch. Previously, when doing a merge with a trunk and a branch and there was a difference in the first line of the branch, the versions client would crash. ******** Changes for 4.3e.02 *********** - (I2-710, S.20-547) For reports, repaired buffer overflows when saving new report formats and report filters. ******** Changes for 4.3e.01 *********** - (I2-696, S.20-804) Correct Issues clients from crashing when switching from database to database and then switching groups. User preferences were not being refreshed properly when user was switching between databases in issues via the use of the Databases file. ******** Changes for 4.3e ************** - (I2-363. S.18-500, S.19-278, S.19-279, S.19-309, S.19-667) Adding support for the 2.4.x kernel of Linux. - (I2-548, S.19-789) For Issues, added new functions to the client-side and server-side to alleviate permissions problems discovered in 4.3d relating to issue attachments. Previous method sometimes restricted users from modifying issues and adding attachments when their umask was very restrictive. - (I2-393, S.18-654) For IW, corrected a memory management problem in the report function. 9. General Release Changes for version 4.3d - (I2-249, S.18-080, S.18-552) For Issues, the main issue form now has a new 'Attachment' button. The Attachment button can be used to view or manage any file attachments associated with the issue. The new file attachment panel allows users to add, remove, view, and export file attachments. The Razor access list may be used to tailor each of the file attachment related operations for a given user. The new access list template includes these new operations. A user may modify (i.e. add/ remove) attachments only when the issue is locked for modifications. The default behavior allows all users to add, remove, view, and export file attachments. Customers with existing databases should edit their access list to tailor use of these operations. Users can also view the file attachment history from this panel. The file attachment history denotes the file attachment Add, Remove operations performed. For an Add operation the history includes the local directory from which the attachment was introduced. For a remove operation the history entry includes the (optional) backup file created from the 'removed' file attachment. The Razor Options file (at the DB or group level) dictates whether Razor will create a hidden backup file when the file attachment is removed. The viewer panel allows the user to view a file attachment with the application/viewer that Razor thinks is associated with files with the same file extension as the file attachment. The panel also allows the user to browse (Windows) or specify (UNIX) an alternate viewer. The viewer panel has slightly different implementations for UNIX, Windows. When a Razor user goes to view an issue's file attachment the Razor client will pull a read-only copy of the attachment to a temporary location on the client computer. Razor is NOT performing versioning of an issue's file attachments. Consequently, if the user edits the read-only attachment (and saves to another filename) the edits will not be retained by Razor. Just providing capability to view the attachment using native viewer/application. I.e. if they attach a Word document and an Excel spreadsheet to the issue they should be able to view (from a PC) using MS Word, Excel (if they have these applications). The user also has the capability to double-click a particular file in the file attachment list and popup the attachment in the associated viewer/application or the viewer config panel. An effort has been made to prevent users from 'viewing' executables on Windows PCs. Executables (e.g. *.exe, *.bat, *.com, ...) can still be added, removed, exported as attachments. Windows thinks that the associated application for an executable is a shell for running the executable. Didn't want the Razor user running an executable as a side-effect of viewing an attachment. If Issues thinks the attachment is an executable it will not associate a viewer application. It will force the user to cancel viewing or specify an alternate viewer (e.g. Notepad, hex editor). If an issue has (or has had) an associated file attachment there will be a $RAZOR_UNIVERSE_DIR/DOMAIN_01// /Attachments/ directory. The contents of the directory will be as follows: - RzAttachManifest - A test file listing all associated file attachments. Includes filename, username associated with introduction, timestamp for introduction. - RzAttachHistory - A text file logging all remove, add operations performed. Each entry includes operation type, file attachment filename, user, timestamp, directory introduced from (ADD only) or name of optional backup file (REMOVE only). - - Issue file attachment(s) added by user. - rz.. - Represents backup file created when a user removed the attachment. NOTE: Currently, file attachment functionality is not supported for IssueWeaver and Master/Slave databases. - (I2-465, S.19-196, S.19-247, S.19-285, S.19-353, S.19-397) Corrected the bug for Razor clients hanging the Razor lm when there is a server/client version mismatch that appeared in Razor 4.3c.01. Due to a change in communication protocol, the client user was not receiving a version mismatch message. This has been corrected and the client user will now receive the Server/Client version mismatch message. - (I2-482) Corrected bug in Razor 4.3c/4.3c.01 Razor Password File and renamed the file to rz_pwd_file. - (I2-455) For Issues, corrected the problem whereby selecting "AVG STATE Transition" would cause the export report to fail. - (I2-072, S.15-829) For Issues, Versions & Threads, the format of the .razorrc. file has been changed to allow a different startup group for each database and a different startup directory for each group within a given database. - (I2-418) Corrected a bug in 4.3c, when running the razor_lm with the full path a segmentation fault would occur. - (I2-415) Threads, corrected the filter display window for SunOS 4.x.x. - (I2-261) Issues, corrected the razor -c modify_issue command from core dumping when returning an error code. - (I2-190, S.16-955) Corrected the sorting function in reports. The command line and IssueWeaver will now honor the sorting options. - (I2-478) For Issues, Versions, and Threads updated the trademark date to 2003. Will see this update when loading the applications. - (I2-445) Added scripts to the examples directory for parent/child relationships. The set_child_issue and validate_parent_child scripts can be found in the $RAZOR_HOME/examples directory. - (I2-484, S.19-386) For Razor SCC, corrected a problem where 2 users could checkout the same file when using Microsoft Visual Studio. 10. Upgrading from Razor 4.3a.05 and prior For users upgrading from Razor releases 4.3a.05 and prior: The LM_Access_list file (in the Razor_lm directory) supersedes the Database Access_list file in RAZOR_UNIVERSE/Tables. Entries in the RAZOR_UNIVERSE/Tables/Access_list file for RAZOR_DOWN, ADD_USER, MODIFY_USER, and REMOVE_USER will need to be copied to the Razor_lm/LM_Access_list file. Additional controls have been added to the LM_Access_list file to control who can set password aging and lockout a user. To add these controls to your LM_Access_list file, add the following entries to the file: SET_PASSWD_AGING LOCKOUT_USER 11. Note for Razor SCC Users: Microsoft Visual Studio has an option that will prompt the user to retrieve new (ie. updated) files from the Razor database when a workspace is opened. This option is set by selecting Tools->Options and checking the "Get files when opening the workspace" box on the "Source Control" tab. Users should NOT set this option. When this option is set, the IDE will pull read-only copies of all files in the user's workspace that are in source code control. The IDE does this without determining if any files in the workspace are currently checked-out. Consequently, the user may lose any edits to files in the workspace that are currently checked-out of Razor. When the user invokes Project->Source Control->Get Latest Version... from within an open project/workspace, the IDE considers the check-out status of each file. Consequently, those files currently checked-out by the user are NOT overwritten with a read-only version of the file from the Razor DB. 12. Previous Release Notes for Razor 4.3c thru 4.3 ----------------------------------------------------------------- ----------------------Razor(R) v4.3c ---------------------------- ----------------------------------------------------------------- Razor 4.3c supports the following platforms: SunOS 4.1.x, Solaris 2.5 (Sparc) Solaris 2.6 and higher (Sparc & Intel), HPUX (10.x), IRIX (5.x & 6.x), IRIX 6.5 (64-bit), AIX (3.x & 4.x), OSF/1 (Digital Unix 4.x), SCO, Linux (2.0.x & 2.2.x), Windows NT/95/98/2000 and Windows NT 4.0 / 2000 (server and client). Notes for RCS Users: =================== 1.) Razor users using RCS are now required to use version 5.7. For Windows server users, RCS v5.7 is automatically provided. For UNIX users, if you are not sure which version of RCS you have installed, input the command: rcs -V RCS v5.7 can be downloaded from: http://www.gnu.org/directory/rcs.html ------------------------------------- 2.) All keyword expansions for Razor groups using RCS will now have local time. The previous script used UMT time. In addition, the History file will now record everything in local time. If this is going to cause any problems for you, please contact Razor Support. *********************************************************** General Release Changes for version 4.3c *********************************************************** - Increased security in Razor by upgrading the Razor password file to a stronger encryption algorithm. - Added support for the ability to lock a user's account. When an account is locked, the user will be unable to login remotely to Razor. - Added support for the ability to set an expiration date for a Razor user's password. If the password expires, the user will be unable to login remotely to Razor. - Added support for the ability to require the user to change his password on the subsequent login. - Updated the LM_Access_list file to control who can lock accounts or set password aging. - Command line support for password aging and account lockout is provided. - Added a script that will set the password age for a group instead of a particular user. - Updated Threads to now have the option to show only the files associated with the thread (as opposed to showing all files, with the files associated with the thread marked). - Updated the Promote function in Versions. A user can now promote a group of selected files by selecting the "Promote All" button. Each file will be promoted to the next highest level of maturity. - The view filters used by a given Razor user are now stored in file ".razor-init." instead of simply ".razor-init". This change allows each Razor user to maintain a separate set of view filters. To preserve existing view filters, users should copy their existing ".razor-init" file into "razor-init.". - The user preferences used by a given Razor user are now stored in file ".razorrc." instead of simply ".razorrc". This change allows each Razor user to maintain a separate set of preferences. To preserve existing preferences, users should copy their existing ".razorrc" file into ".razorrc.". - Corrected problem with Threads in having to hit the exclude button before being allowed to hit the include button on Linux. - In Windows, when closing the Razor Desktop, the user will be presented a window asking "Are you sure...?" before closing all Issues, Versions, and Threads applications. - Razor will now honor hostnames beginning with 0-9. - Updated Razor SCC so the database does not crash when a project is introduced. - Corrected MetricCenter script to run on SunOS. *********************************************************** General Release Changes for version 4.3b *********************************************************** - Razor now works on the Windows XP platform. Please note that on the XP server, mail generated due to state changes within Issues functions correctly using Microsoft Outlook 2000. - Updated Razor/MetricCenter API to now gather metrics for Issues in addition to Versions. - Updated Razor SCC to integrate with the Visual Studio.Net IDE. - Added one central Access_list file (LM_Access_list) at the License Manager level, to control access to the license manager and the addition/modification of Razor users. - Updated Razor to honor more than one IP address. A multihomed Razor LM/DB server will write a comma-separated list of IP addresses into its License_status and Server_status files. Razor clients will now attempt to connect to each IP listed in the status files until a successful connection is made. Previously, the order of the IP addresses in the status files for a multihomed server were dictated by gethostbyname(). This is still the default behavior. However, a new environment variable (RAZOR_ALT_CLIENT_IP_ADDR) will allow a multihomed Razor client to select an alternate IP address. If a client was multihomed properly then a drop-down list of IPs would be presented. The "Local Host" IP address list can also be populated via the RAZOR_ALT_CLIENT_IP_ADDR environment variable outlined above. New environment variables (RAZOR_ALT_LM_SERVER_IP_ADDRS, RAZOR_ALT_DB_SERVER_IP_ADDRS) allow a user to dictate the order of the IP addresses that the Razor client will use in attempting to connect to the Razor servers. - A new environment variable (RAZOR_DEBUG_ALL) has been added to simplify Razor debugging. This environment variable can be used to enable debugging of primary and secondary processes in the Razor LM, DB, and/or client. - Razor servers that were doing many transactions with many users would sometimes experience sporadic failures in establishing new client connections. The default "backlog" parameter used by the server in the listen() command was inadequate. This parameter has been increased. In addition, the parameter may be manipulated directly via new environment variable (RAZOR_SOCK_LISTEN_BACKLOG). - Prevent server process from exiting when unable to append/open error log file. - Use stat() to debug incidents where server is unable to open Mapping, Info, History, or temporary file. - Updated the Razor (UNIX) install script. When upgrading Razor and answering "NO" to "Do you want to use symbolic links?", the current symbolic link will no longer be deleted. - Updated the method in which tmp files are deleted. Razor now requires the user to define the new environment variable 'RAZOR_USE_TMP_CLEANUP_SCRIPT' in order to run the $RAZOR_HOME/scripts/rz_cleanup_tmp script on server shutdown. Windows: ======= - The Windows installation process has been updated. With new installs of Razor the default install directory is Visible and a debug log has been added. Additionally, if services do not install correctly, the user is notified and directed to contact technical support. - Added a feature to prompt the user for a new password for the License Manager service if RAzor detects the service failed to start due to a login problem. Passwords for the Syslog, Inetd, and database services will also need to be updated manually by the user (no prompt is provided). - Corrected the extra "^I" strings in Razor email notification messages generated by the Permissions file. - Improved the validation on the time stamp field. User is now notified of invalid input. Previously, the incorrect time stamps were just erased by the server on the PC clients. - Corrected a problem in which Razor was not handling 'send would block' errors properly when sending large amounts of data. The problem resulted in data being dropped. Razor SCC: ========= - Updated for the Visual Studio.NET IDE. All functions work in the .NET environment similar to the Visual Studio 5.0 and 6.0 environment. - You can now open a Visual Studio project from a Razor database. To perform this, select File->Open Workspace->Source Control. Then log into the Razor database, choose the folder containing the project to open, select a local directory to place the project in, and click "OK". Once back to the Open Workspace dialog box, open the .dsp or .dsw for the project you just selected, Visual Studio will now get the latest version for all files in the project. - Fixed a problem with case sensitive file name compares causing report of files not in the Razor database during check-in, check-out, and uncheck-out. - Fixed problems with Rational Rose. Most notably, problem where RR would pass a different window handle to SCC dll for each call, we would cache the first passed handle and use it from there on. Since the window handle went invalid, we would get dialog boxes that would not display and other general protection faults. - Many other fixes made to help enhance the general stability of the RazorSCC dll. Issues: ====== - The correct title for the database/group will now appear in the GUI when switching between databases and groups. - Updated the rz_rename_attr and rz_remove_attr scripts to update database and user filters, accordingly. - Corrected the rz_add_issues_group script for Linux 7.0. Versions: ======== - Updated Versions so that 'related issues' appear in reports whenever the *last* entry in the Razor history file [which may specify related issue(s)] specifies a related issue. - In Versions, modified the history file so an entry labeled AUDIT will be added to the Razor History file each time a user does a check-in or checkout. Entry is formatted as follows: ##AUDIT - Updated the rz_vcs.rcs script to include the -zLT option to handle local time. For example, the Razor History file and the revision History in the source file will now have the same time when local time is Pacific Standard time. IssueWeaver: =========== - Corrected entries made in Issues History file when an issue is modified via IW so modifications are now logged as ALTERED. Previously, every time an issue was modified via IW the change was logged as STATE CHANGE. Command Line: ============ - When branching a file expand keywords now works via the command line. NOTE: For release notes prior to 4.3b, please see the RELEASE_NOTES.old file. REMINDER: The Support Staff would like to remind users that releases of Razor prior to 4.3 are no longer supported. Please upgrade your site at your earliest convenience. Detailed instructions follow. Remember to follow ALL the separate upgrade steps where appropriate. *********************************************************************** *********************************************************************** ** ** ** MANDATORY PATCHES ** ** ** ----------------------------------------------------------------------- ** ** ** !!!! HPUX 10.x & 11.x USERS !!!! ** ** ================================ ** NOTE=> All users of HPUX 10.x and 11.x need to install one of the following patches to correct a problem with SCCS handling the year 1999. This problem will be evident when attempting to modify files archived in the Razor database (i.e. modify issues, checkin files, edit threads): HPUX PATCH ---- ----- 10.01 PHCO_16250 10.10 PHCO_16251 10.20 PHCO_16252 11.0 PHCO_16253 If you or your system administrator have additional questions, please contact your HP representative. -------------------------------------------------------------------------- ** ** ** !!!! HPUX 10.2 USERS !!!! ** ** ========================= ** NOTE=> All users of HPUX 10.2 need to install an HP supplied patch (PHCO_13084) to correct a problem related to how 'awk' processes multi-tab entries. -------------------------------------------------------------------------- ** ** ** !!!! IRIX 6.2 and IRIX 6.3 USERS !!!! ** ** ===================================== ** NOTE=> All users of IRIX 6.2 and IRIX 6.3 need to install an SGI supplied patch to the /usr/bin/delta program. The official IRIX 6.2 patch number is SG0001643. For IRIX 6.3 users as well as those IRIX 6.2 users who may not have ready access to the patch, a copy of the 'delta' program is available via anonymous ftp from ftp.razor.visiblesystemscorp.com in the file: IRIX/Patches/delta ** ** ************************************************************************** !!!! Solaris 2.5 OR HIGHER USERS !!!! ====================================== NOTE=> If you are installing on a Solaris 2.5 or higher machine (SunOS 5.5 or higher), "/usr/dt/lib" should be installed. ************************************************************************** ************************************************************************** ** ** ** For details of prior releases, refer to the file ** ** Razor_/doc/RELEASE_NOTES.old. ** ** ** ************************************************************************** ************************************************************************** 13. Razor Security Issue in v4.1 A security vulnerability in version 4.1 of Razor was discovered as identified on the web page referenced at http://nvd.nist.gov/nvd.cfm?cvename=CVE-2000-0572I. Subsequent releases of Razor address this issue. If you are under maintenance, you have the option of upgrading to a more recent release of the Razor at no cost. If you are not under maitenance and want to upgrade then you will need to contact Jennifer Stone at jstone@visiblesystemscorp.com. And, if you are unable to upgrade, then those of you are assuming the risk short of doing your own authentication and work around. Here is some background on Razor release history to help you in deciding how to plan for your upgrade. 1) Razor 4.1 used a very simplistic means of encrypting the Razor password file. Passwords were simply rotated. Some of the LMCO users were able to decrypt the password file. As of version 4.3c, we implemented a much more secure password encryption scheme using a very solid algorithm. 2) Use of the Razor password file is optional. The Razor license manager can be configured to not utilize Razor passwords. Authentication of remote users is done using the native/host password authentication. 3) The upcoming Razor release has an enhancement that allows remote UNIX clients to utilize SSH to authenticate the remote user. This is more secure than the Razor password file or the current means (rexec) of authenticating remote users. Some additional notes ... - Customers may switch and use their own local OS authentication instead of Razor's - OS permissions and protections still apply to the files and issues stored in the database - The security notice applies to local users that have already logged into the server and the supporting system. Razor is based on the presumption that a local user or employee has gained access to the system. The following general information about Razor releases is presented in two-parts. The first part (below) represents an outline of the issues being address in the release we are currently working on which is version 5.2. The second part represents all of the issues addressed in previous releases starting with version 5.1.03. Here is the potential release content for Razor Version 5.2 ... (UNIX) File Chooser GUI rendering problem. Chooser's current directory text field is partially obstructed by the pair of radio buttons above it. Add a checkbox to the GUI logins so that it remembers the user's password (possibly saved in $HOME as a binary) when requested. Add the MAC OS version of Razor including the use of SSH for encryption of username and password. Add the option to terminate a branch from the "razor" command line. Fix bug when terminating a branch that has another branch. Fix problem that occurs when promoting several sources at once to something other than the next state. Fix the text field Xwidget warnings when starting clients on Linux and Solaris. Fix the rz_create_remote_distribution to include needed components for Guiffy problem using the timestamp sort in the Issues Activity window. This is a Windows-only problem. Support addded for Guiffy when used with remote UNIX/Linux clients. Remote Razor Command Line. Add "remote" capabilities to the 'razor command line'. User may need to login to server and "razor command line" may need to store this info in $HOME (similar to CVS). Initially will be UNIX-ONLY, i.e. no Windows support. Update Razor servers for Versions Weaver specific messages/protocol update revision files for 5.2. Update the handling of ONE_OF_MANY_LIST to display the selected item when issue is opened. Update the license scheme to close up the different user same license hole. Update the Razor Desktop so that it starts as a small box at the top right corner of the user's desktop. It may be moved and resized by the user and will remember the user's setting. Update to use ssh for improved security of remote client authentication. Add Guiffy 7.4 to windows Razor installer. Fix bug in razor -c modify_issue, which adds 2 extra lines to 1st text pane after each update. Line should only be added if pane is updated. Multiple updates leave a large set of blanks in text pane. Fix Razor's update password or create user feature so a user's password cannot be blank, i.e. prevent zero-length password. Fix the Razor date wizard in issues, i.e., when user changes to a 30 or 28 day month, it stays this way for all other months. The Razor reports wizard shows empty dates as Dec 31, 1969. Dates should be shown as empty or or something similar. Update the File Attachments feature in Issues so that it remembers the last directory you accessed within the current session. The default directory should be $HOME. Update the File Attachments feature in Issues so that the user can attach more than one file at a time. Update the razor command line to include a "razor lm_start" command. Should be the same as "razor_lm&". Update the Razor up/down and razor_lm start down msgs so that the user is returned to the command prompt. Add ability to delete a database in Windows Razor Admin GUI. Needs to update the registry and then reboot the box. All dbs must be down and lm must be down. On Windows 2003 server, Razor Admin will be able to start a DB that is created on a drive that sits on a different machine.