TrueCrypt - Free opensource on the fly Disk Encryption tool

In todays world of data security and confidentiality of documents and files ranging from critical information like business secrets on a mobile laptop to a password file of personal use with informations like credit card details etc, it is important to have a data security and encryption software like Truecrypt in place.

Full Story

How to install & configure Xen Virtualization in openSUSE 11.0

In openSUSE 11.0, Xen Virtualization ins pre-built and all it takes is a few clicks away from up and running with Virtualization in no time. Xen is a virtual machine monitor for x86 that supports execution of multiple guest operating systems with unprecedented levels of performance and resource isolation. To install and configure Xen Virtualization in opensuse Click Here

SUSE Security Announcement: Opera 9.25 (SUSE-SA:2008:001)

______________________________________________________________________________

SUSE Security Announcement

Package: opera
Announcement ID: SUSE-SA:2008:001
Date: Mon, 07 Jan 2008 18:00:00 +0000
Affected Products: SUSE LINUX 10.1
openSUSE 10.2
openSUSE 10.3
Vulnerability Type: remote code execution
Severity (1-10): 4
SUSE Default Package: no
Cross-References: CVE-2007-6520, CVE-2007-6521, CVE-2007-6522
CVE-2007-6523, CVE-2007-6524

Content of This Advisory:
1) Security Vulnerability Resolved:
Opera 9.25 security release
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

Opera released version 9.25 of their browser to fix various security
problems:

CVE-2007-6520: Fixed an issue where plug-ins could be used to allow
cross domain scripting, as reported by David Bloom. Details will be
disclosed at a later date.

CVE-2007-6521: Fixed an issue with TLS certificates that could
be used to execute arbitrary code, as reported by Alexander Klink
(Cynops GmbH). Details will be disclosed at a later date.

CVE-2007-6522: Rich text editing can no longer be used to allow cross
domain scripting, as reported by David Bloom. See our advisory.

CVE-2007-6523: Fixed a problem where malformed BMP files could cause
Opera to temporarily freeze.

CVE-2007-6524: Prevented bitmaps from revealing random data from
memory, as reported by Gynvael Coldwind. Details will be disclosed
at a later date.

2) Solution or Work-Around

There is no known workaround, please install the update packages.

3) Special Instructions and Notes

Please close and restart all running instances of Opera after the update.

4) Package Location and Checksums

The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command

rpm -Fhv

to apply the update, replacing with the filename of the
downloaded RPM package.

x86 Platform:

openSUSE 10.3:
http://download.opensuse.org/pub/opensuse/update/10.3/rpm/i586/opera-9.25-1.1.i586.rpm
1cc7dfa3230320e6f90d235fec6e885f

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/i586/opera-9.25-1.1.i586.rpm
8d66debcef68034bfc60344283009a2c

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/i586/opera-9.25-1.1.i586.rpm
2c437285b8cc80decb649ec818f5a616

Power PC Platform:

openSUSE 10.3:
http://download.opensuse.org/pub/opensuse/update/10.3/rpm/ppc/opera-9.25-1.1.ppc.rpm
715ee156b5f5b3983ddc576e8f9b74d7

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/ppc/opera-9.25-1.1.ppc.rpm
d2496ef4adbffc6688ff720d6674d6a0

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/ppc/opera-9.25-1.1.ppc.rpm
82aa04dc7743d43239b34dc115729942

x86-64 Platform:

openSUSE 10.3:
http://download.opensuse.org/pub/opensuse/update/10.3/rpm/x86_64/opera-9.25-1.1.x86_64.rpm
799df7724aece868efdfe2474e137eef

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/x86_64/opera-9.25-1.1.x86_64.rpm
76c67616c8d2c70f77b43935832c44d4

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/x86_64/opera-9.25-1.1.x86_64.rpm
75de97d12c071a60f498f84536d8be29

Sources:

openSUSE 10.3:
http://download.opensuse.org/pub/opensuse/update/10.3/rpm/src/opera-9.25-1.1.nosrc.rpm
157c00c3e60dd9610521b9b050cfaaac

openSUSE 10.2:
ftp://ftp.suse.com/pub/suse/update/10.2/rpm/src/opera-9.25-1.1.nosrc.rpm
a628b5553b4306136f10e90217beb2c8

SUSE LINUX 10.1:
ftp://ftp.suse.com/pub/suse/update/10.1/rpm/src/opera-9.25-1.1.nosrc.rpm
c5b73df479db77b4cb6819a0936f87e4

______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

See SUSE Security Summary Report.
______________________________________________________________________________

6) Authenticity Verification and Additional Information

- Announcement authenticity verification:

SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.

To verify the signature of the announcement, save it as text into a file
and run the command

gpg --verify

replacing with the name of the file where you saved the
announcement. The output for a valid signature looks like:

gpg: Signature made using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team "

where is replaced by the date the document was signed.

If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command

gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

- Package authenticity verification:

SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.

There are two verification methods that can be used independently from
each other to prove the authenticity of a downloaded file or RPM package:

1) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement

1) The internal rpm package signatures provide an easy way to verify the
authenticity of an RPM package. Use the command

rpm -v --checksig

to verify the signature of the package, replacing with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.

This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.

2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command

md5sum

after you downloaded the file from a SUSE FTP server or its mirrors.
Then compare the resulting md5sum with the one that is listed in the
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.

- SUSE runs two security mailing lists to which any interested party may
subscribe:

opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.

opensuse-security-announce@opensuse.org
- SUSE's announce-only mailing list.
Only SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
.

=====================================================================
SUSE's security contact is or .
The public key is listed below.
=====================================================================
______________________________________________________________________________

The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular, the
clear text signature should show proof of the authenticity of the text.

SUSE Linux Products GmbH provides no warranties of any kind whatsoever
with respect to the information contained in this security advisory.

Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key

Ultimo bugfix per SUSE Linux Desktop 1.0

Ecco la mail apparsa nella ML di opensuse:

Hi,

With the release of the python/pcre bugfix/security fix update we have
now released the last maintenance update for SUSE Linux Desktop 1.0.

SUSE Linux Desktop 1.0 is now at its End Of Life, support is discontinued,
and no more updates will be published.

So lets take a look back at its history...

SUSE Linux Desktop 1.0 was released end of May 2003, making its lifetime
4.5 years.

SLD 1.0 was the first true enterprise desktop SUSE published, previously
existed just a lesser known add-on called SUSE Linux Office Desktop.

Currently the following SUSE Linux Enterprise Desktop products exist
and are in maintenance (regular / extended maintenance):
- Novell Linux Desktop 9 (until July 30th 2009/2011)
- SUSE Linux Enterprise Desktop 10 (until July 31st 2011/2013)

Some interesting things:
- SLEC had a 50% package difference against UL1 core (411 additional source
rpms, vs around 800 for UL1).
NLD9 has around 17% (271:1570), SLED 10 has 0%.

- SLEC had a seperate kernel branch and stayed at 2.4.19 while SLES 8 went
to 2.4.21.

Some bad things security wise:
- We were not able to update RealPlayer to RealPlayer 9 to fix security
issues because version 9 does not work with the old glibc version.
(glibc 2.3 vs 2.2.5)

- We had to stop updating Acrobat Reader to version 7 for the same reason.

- We were unable to continue upgrading Mozilla to after the Mozilla
1.7.x release due to mismatching gtk2 and xft library requirements.

Some statistics regarding our online updates:

Total: 380 (240 active)
Security: 324 (200 active)
Recommended: 41 ( 34 active)
Optional: 15 ( 6 active)

Top issues:
21 kernel
12 ImageMagick
12 cups
9 samba
8 gpg
7 openssh
7 mozilla (would have scored higher, see notes)
7 heimdal
6 rsync
6 libpng
6 java2
6 gaim
5 XFree86-server
5 openssl
5 OpenOffice_org
5 MPlayer
5 mc
4 XFree86-libs
4 qt3
4 libtiff
4 koffice-wordprocessing
4 kdelibs3
4 acroread (would have scored higher, see notes)
... others below 4 ...

Ciao, Marcus Meissner