|
DASDEC
Software Updates
DASDEC
upgrade software is made available to customers by email notification.
Notification of new software is sent to registered customers. You
can request the latest DASDEC
software by sending an email request to support@digitalalertsystems.com.
Latest official release software is
version
1.8-1 (Available Aug
14, 2008)
This is an
important update release
of DASDEC/OneNet 1.8 level software. This release supports many useful
enhancements to the 1.8-0 feature set. There are also a few very
important bug fixes.
DAS
recommends installation on ALL DASDECs in the field.
This release
contains all of the features and bug fixes from earlier software
releases. It can be used to upgrade any level of DASDEC software.
Latest
official pre-release software is
version
1.8-1d (Available Dec
8, 2008)
This update release
of DASDEC/OneNet 1.8 level software is in advance of the coming 1.8-2
release. It supports useful
enhancements to the 1.8-1 feature set. There are also a few significant
bug fixes that apply to specific configurations. All new DASDEC
units will be shipped with this software as of Dec 8,2008.
2007
& 2008
Daylight Savings Time Note
Changed
DST rules for the United States went into effect at 2AM March 11,2007.
DST will end at 2AM on Nov 4, 2007. The rules remain in effect for
2008. DASDEC software from 1.6-0 and up
supports the new rules. It
is still important to upgrade
to the latest software even if you missed the transition to the new DST
rules. You may need to set the time after the
upgrade. DASDEC software
versions earlier than 1.6-0 transitioned to DST starting 2AM Sunday
April 1,2007 and will transition too early at the end of October 2007.
Request
download info from support@digitalalertsystems.com
|
Previous
four software
versions were 1.8-0 Jan 18,2008 & 1.7-0.a04
- Nov 6,2007 & 1.7-0 - Sept 16,2007 & 1.6-0 -
Feb 16,2007
Legacy version Important Note!
|
If your
DASDEC software
is version 1.1-7 up through 1.2-2, it is important to install the the
following repair patch before upgrading to newer software or installing
any other packages shown on this page. Versions 1.2-3 or later do not
need to be repaired.
Download the RPM
database repair package: dasdec-repair_rpm_db-1.0-0.i386.rpm
to your hard disk and then install using the normal DASDEC server
upgrade (under Setup->Server). This package runs a database repair
operation on the RPM package system. The repair starts one full minute
after
installation. Be patient after the install and do not log back
in or operate the DASDEC until the repair has completed. The DASDEC
server software
will stop during the repair and the front panel LCD will flash the
in-progress repair status
until the operation is finished. At that time the DASDEC server
software will restart. After that, upgrades can be safely
performed. |
Download Latest DASDEC Security
Patches
|
These
RPM files are the latest
security patches for OpenSSH, OpenSSL, Apache Web Server, and GNU
GLIBC. They
can be installed on the DASDEC, as of release 1.2-3, using the Software
Upgrade feature of the DASDEC Web Interface.
To install click on the link for the desired file. Your Web browser
must be configured to save an RPM file to disk. Save to your local hard
disk. Login to the DASDEC using the Web browser interface. Go to the
DASDEC Setup->Server
page. At the bottom of the page
use the Browse button for the provided Software Upgrade
interface and find the RPM file you saved in the previous step. Select
the file and then use the Upgrade button to install on the DASDEC. Each
patch group must be installed together. The DASDEC Software Upgrade Web
interface tracks uploads of these patches and will only run the final
upgrade install when
all the files of a group have been uploaded.
What
is fixed by these patches? These upgrades fix recently discovered
security holes. The same files and full explainations of what is fixed
can be found at http://www.fedoralegacy.org/updates/RH9/
Should
you install? If
your DASDEC is installed on a
company wide or facility wide network, and you have rather open access
in this network, then you should install these patches. If your DASDEC
has very restricted network access then it probably does not matter.
OpenSSH
patches:
For DASDEC Software Version
1.3-2c and up
OpenSSH
main RPM
(openssh-3.5p1-11.4.legacy.i386.rpm - 182 KB)
OpenSSH
Server RPM
(openssh-server-3.5p1-11.4.legacy.i386.rpm - 182 KB)
OpenSSH
password RPM
(openssh-askpass-3.5p1-11.4.legacy.i386.rpm - 43 KB)
OpenSSH
clients RPM
(openssh-clients-3.5p1-11.4.legacy.i386.rpm - 307 KB)
For
DASDEC
Software Version
1.2-3 to 1.3-2b
OpenSSH
main RPM
(openssh-3.5p1-11.2.legacy.i386.rpm - 182 KB)
OpenSSH
Server RPM
(openssh-server-3.5p1-11.2.legacy.i386.rpm - 182 KB)
OpenSSH
password RPM
(openssh-askpass-3.5p1-11.2.legacy.i386.rpm - 43 KB)
OpenSSH
clients RPM
(openssh-clients-3.5p1-11.2.legacy.i386.rpm - 307 KB)
OpenSSL patches:
For
DASDEC Software Version 1.3-2c and up
OpenSSL
main RPM
(openssl-0.9.7a-20.6.legacy.i386.rpm - 1.1 MB)
OpenSSL
devel RPM
(openssl-devel-0.9.7a-20.6.legacy.i386.rpm - 1.6 MB)
For
DASDEC
Software Version
1.2-3 to 1.3-2b
OpenSSL
main RPM
(openssl-0.9.7a-20.4.legacy.i386.rpm - 1.1 MB)
OpenSSL
devel RPM
(openssl-devel-0.9.7a-20.4.legacy.i386.rpm - 1.6 MB)
Apache
Web Server patches:
For
DASDEC Software Version 1.3-2c and up
Main
Apache Server RPM
(httpd-2.0.40-21.21.legacy.i386.rpm - 1 MB)
Apache
Users Manual RPM
(httpd-manual-2.0.40-21.21.legacy.i386.rpm - 835 KB)
Apache
SSL Module RPM
(mod_ssl-2.0.40-21.21.legacy.i386.rpm - 80 KB)
For DASDEC Software Version 1.2-3 to 1.3-2b
Main
Apache Server RPM
(httpd-2.0.40-21.20.legacy.i386.rpm - 1 MB)
Apache
Users Manual RPM
(httpd-manual-2.0.40-21.20.legacy.i386.rpm - 830 KB)
Apache
SSL Module RPM
(mod_ssl-2.0.40-21.20.legacy.i386.rpm - 80 KB)
GNU GLIBC patches:
For DASDEC
Software Versions 1.6-0
and up
(Manual
(command line)
install of the glibc 2.3.2-27.9.7.4.legacy series can be performed on
any DASDEC Software Version, but is only required for installation on
1.5-1 and less. See below.)
These three rpm packages also
support the correct transition from
standard time to daylight savings time starting March 11,2007.
Installing these packages is not
required for obtaining the DST changes if DASDEC
version 1.6-0 or higher is installed. But, these
packages will become the latest GLIBC libraries for the DASDEC
with the release of 1.6-0 or higher.
Main
GLIBC RPM
(glibc-2.3.2-27.9.7.4.legacy.i386.rpm - 3.3 MB)
GLIBC
Common RPM
(glibc-common-2.3.2-27.9.7.4.legacy.i386.rpm - 12.6 MB)
GLIBC
Devel RPM
(glibc-devel-2.3.2-27.9.7.4.legacy.i386.rpm - 2.3 MB)
For
DASDEC Software Version 1.2-3 - 1.5-1
Main
GLIBC RPM
(glibc-2.3.2-27.9.7.2.legacy.i386.rpm - 3.3 MB)
GLIBC
Common RPM
(glibc-common-2.3.2-27.9.7.2.legacy.i386.rpm - 12.6 MB)
GLIBC
Devel RPM
(glibc-devel-2.3.2-27.9.7.2.legacy.i386.rpm - 2.3 MB)
Standard
Web Interface RPM Installation
Instructions
1. Save the version appropriate
downloaded RPM files to your
hard
drive.
2. These files should be placed on a disk system accessible from a host
computer used to browse the DASDEC/OneNet.
3. Login to the DASDEC via a Web Browser (ie. MS Internet
Explorer or Netscape or Opera, etc) as Admin from the host computer
that has access to the disk that has this RPM file (eg. if you are
using a laptop connected to the DASDEC/OneNet then the RPM files simply
need to be accessible from or on
the
laptop).
4.Navigate to the DASDECWeb Browser page
Setup->Server->Upgrade (on older systems this is simply at
Setup->Server).
5.At the bottom of that page is a text field where you can enter the
path and name of one RPM file. The easiest way to fill this in is to
use the provided Browse button. This will show you the filesystems
accessible from your host computer. Change directories as needed until
you find the desired RPM file. Select the RPM file name and it will be
placed
into the text field. Then click on the Upgrade Server button. After the
file is examined you will be asked to confirm the upgrade action. Do so
and wait for the DASDEC login to return.
The GLIBC upgrade must be completed in 3 phases, the HTTPD Web
Server in 3 phases, the OpenSSH in 4 phases and the OpenSSL in 2
phases. You have to
load each RPM file of the group in succession. You will be told which
packages have been loaded and which ones remain to be loaded. After
loading the final RPM of the bunch, the DASDEC will actually run
the upgrade. This will take a couple of minutes. Do not get impatient if
the Web browser tries and fails to contact the unit after just a minute.
Just try again after another minute or so. The GLIBC upgrade takes
noticably longer to complete than other upgrades.
The streaming audio upgrade is simpler to do because it simply takes
the single file. This upgrade should complete in less than a minute
once initiated.
And to
just emphasize the obvious but important, do not power off the DASDEC during any
upgrade! The front panel LCD will display that it is
upgrading. It will also display when the DASDEC is back to a
ready status and you can log in.
6. After waiting a for the upgrade to complete, log back in via
Web Browser.
Command Line RPM Installation Instructions
RPM upgrades can also be
directly installed by customers familiar or comfortable with a Linux
command line interface. As the 'root' user logged onto a DASDEC, run
the 'rpm' application to install. For instance :
rpm -U openssl-0.9.7a-20.6.legacy.i386.rpm
openssl-devel-0.9.7a-20.6.legacy.i386.rpm
will install the OpenSSL
patch. See detailed instructions next.
NOTE: Manual (command
line) upgrade is
NOT the preferred method! Only do this to upgrade older
systems to newer RPM patches not supported buy the built-in Web Server
upgrade feature. For example, to upgrade a DASDEC
at software versions 1.5-1 and earlier to the GLIBC RPMS with 2007 DST
changes. Copy the desired group of rpm files to a target
DASDEC into the directory /root/rpm. There are a
variety of means to get these files to the target. The two most likely
are :
1. Use the Windows 'putty'
application psftp to do a
secure ftp copy of the RPM files from a Windows machine to the
DASDEC/OneNet. This version of ftp works like standard ftp. The putty
suite is readily available on the Web. Simply do a web search for putty.
or
2. Copy the RPM files to a USB flash drive and plug-in the flash drive
into one of the USB ports in the back of the DASDEC. Logon to
the DASDEC either from an attached keyboard/moniter, or via an
ssh client.
At the command line prompt run (example demonstrates with glibc
RPM files):
mkdir
/mnt/sdcruzer
mount
/dev/sda1
/mnt/sdcruzer
cp
/mnt/sdcruzer/glibc* /root/rpm
umount
/mnt/sdcruzer
Now install the new rpm packages. If you are not at a command line
prompt on the target DASDEC, then logon to the target
DASDEC.
Install the new packages by running rpm on the group of installed files
(example demonstrates with glibc):
cd /root/rpm
rpm -U
glibc-2.3.2-27.9.7.4.legacy.i386.rpm
glibc-common-2.3.2-27.9.7.4.legacy.i386.rpm
glibc-devel-2.3.2-27.9.7.4.legacy.i386.rpm
The installation is finished when the command line prompt appears.
You can verify the installation by running:
rpm -qa | grep glibc
This command will print all of the installed packages that have the
word glibc embedded in the
package name. This will print out more packages than the three we just
installed. But
you need to see that the three installed ones appear on the printed
list.
IMPORTANT LAST STEP if DST changes
are
being
made with the GLIBC upgrade instead of by main software upgrade:
Logon to the Web Browser interface and
reset the timezone to a zone different from your current zone. Goto
Setup->Time to do this. Set the zone and click Accept Changes and
then wait a few seconds and log back on. Now go back to Setup->Time
and reset the timezone
back to the correct zone and click Accept Changes again. Now the new
timezone rules are in place.
|
|
|
|
