ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: "Dmitry V. Levin" <ldv@altlinux.ru>
To: devel@linux.iplabs.ru
Subject: [devel] [security@LINUX-MANDRAKE.COM: MDKSA-2001:030-1 - sgml-tools update]
Date: Thu, 22 Mar 2001 10:07:30 +0300
Message-ID: <20010322100730.A11121@ldv.office.altlinux.ru> (raw)

[-- Attachment #1: Type: text/plain, Size: 7153 bytes --]

----- Forwarded message from Linux Mandrake Security Team <security@LINUX-MANDRAKE.COM> -----

Date:         Tue, 20 Mar 2001 17:51:52 -0700
From: Linux Mandrake Security Team <security@LINUX-MANDRAKE.COM>
To: BUGTRAQ@SECURITYFOCUS.COM
Subject:      MDKSA-2001:030-1 - sgml-tools update
Mail-Followup-To: Linux Mandrake Security Announcements <security-announce@linux-mandrake.com>,
	Linux Mandrake Security <mdk-security@lists.freezer-burn.org>,
	Bugtraq <bugtraq@securityfocus.com>,
	Linux Security List <linuxlist@securityportal.com>

________________________________________________________________________

                Linux-Mandrake Security Update Advisory
________________________________________________________________________

Package name:           sgml-tools
Date:                   March 20th, 2001
Original Advisory Date: March 15th, 2001
Advisory ID:            MDKSA-2001:030-1

Affected versions:      6.0, 6.1, 7.1, 7.2, Corporate Server 1.0.1
________________________________________________________________________

Problem Description:

 Insecure handling of temporary file permissions can lead to other users
 on a multi-user system being able to read the documents being
 converted.  This is due to sgml-tools creating temporary files without
 any special permissions.  The updated packages create a secure
 temporary directory first, which is readable only by the owner, and
 then create the temporary files in that secure directory.

Update:

 The packages for Linux-Mandrake 7.1 and Corporate Server 1.0.1 had a
 dependency on the wrong version of sgml-common which made it impossible
 to upgrade the software.  New packages have been released that fix this
 problem.
________________________________________________________________________

Please verify the update prior to upgrading to ensure the integrity of
the downloaded package.  You can do this with the command:
  rpm --checksig package.rpm
You can get the GPG public key of the Linux-Mandrake Security Team at
  http://www.linux-mandrake.com/en/security/RPM-GPG-KEYS
If you use MandrakeUpdate, the verification of md5 checksum and GPG
signature is performed automatically for you.

Linux-Mandrake 6.0:
0dffdf59bf60b15f695a8f8cf1e0633e  6.0/RPMS/sgml-tools-1.0.9-3.1mdk.i586.rpm
67970748cf90806c3f11885245f38175  6.0/SRPMS/sgml-tools-1.0.9-3.1mdk.src.rpm

Linux-Mandrake 6.1:
a9478714b0629d55de7aa2f48f0bfcb4  6.1/RPMS/sgml-tools-1.0.9-3.1mdk.i586.rpm
67970748cf90806c3f11885245f38175  6.1/SRPMS/sgml-tools-1.0.9-3.1mdk.src.rpm

Linux-Mandrake 7.1:
35e8e14047ac5710274e803bc7bd3e7c  7.1/RPMS/sgml-tools-1.0.9-8.3mdk.i586.rpm
02d2fa1b6a56a7c8dc2decfb9339d2a6  7.1/SRPMS/sgml-tools-1.0.9-8.3mdk.src.rpm

Linux-Mandrake 7.2:
c5e48714e3da71f692e447eb942a368b  7.2/RPMS/sgml-tools-1.0.9-8.1mdk.i586.rpm
c2242855d3be03b899a908944c48ac1d  7.2/SRPMS/sgml-tools-1.0.9-8.1mdk.src.rpm

Corporate Server 1.0.1:
35e8e14047ac5710274e803bc7bd3e7c  1.0.1/RPMS/sgml-tools-1.0.9-8.3mdk.i586.rpm
02d2fa1b6a56a7c8dc2decfb9339d2a6  1.0.1/SRPMS/sgml-tools-1.0.9-8.3mdk.src.rpm
________________________________________________________________________

To upgrade automatically, use MandrakeUpdate.

If you want to upgrade manually, download the updated package from one
of our FTP server mirrors and upgrade with "rpm -Fvh *.rpm".

You can download the updates directly from one of the mirror sites
listed at:

  http://www.linux-mandrake.com/en/ftp.php3.

Updated packages are available in the "updates/[ver]/RPMS/" directory.
For example, if you are looking for an updated RPM package for
Linux-Mandrake 7.2, look for it in "updates/7.2/RPMS/".  Updated source
RPMs are available as well, but you generally do not need to download
them.

Please be aware that sometimes it takes the mirrors a few hours to
update.

You can view other security advisories for Linux-Mandrake at:

  http://www.linux-mandrake.com/en/security/

If you want to report vulnerabilities, please contact

  security@linux-mandrake.com
________________________________________________________________________

Linux-Mandrake has two security-related mailing list services that
anyone can subscribe to:

security-announce@linux-mandrake.com

  Linux-Mandrake's security announcements mailing list.  Only
  announcements are sent to this list and it is read-only.

security-discuss@linux-mandrake.com

  Linux-Mandrake's security discussion mailing list.  This list is open
  to anyone to discuss Linux-Mandrake security specifically and Linux
  security in general.

To subscribe to either list, send a message to
  sympa@linux-mandrake.com
with "subscribe [listname]" in the body of the message.

To remove yourself from either list, send a message to
  sympa@linux-mandrake.com
with "unsubscribe [listname]" in the body of the message.

To get more information on either list, send a message to
  sympa@linux-mandrake.com
with "info [listname]" in the body of the message.

Optionally, you can use the web interface to subscribe to or unsubscribe
from either list:

  http://www.linux-mandrake.com/en/flists.php3#security
________________________________________________________________________

Type Bits/KeyID     Date       User ID
pub  1024D/22458A98 2000-07-10 Linux Mandrake Security Team
  <security@linux-mandrake.com>


-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBDlp594RBAC2tDozI3ZgQsE7XwxurJCJrX0L5vx7SDByR5GHDdWekGhdiday
L4nfUax+SeR9SCoCgTgPW1xB8vtQc8/sinJlMjp9197a2iKM0FOcPlkpa3HcOdt7
WKJqQhlMrHvRcsivzcgqjH44GBBJIT6sygUF8k0lU6YnMHj5MPc/NGWt8wCg9vKo
P0l5QVAFSsHtqcU9W8cc7wMEAJzQsAlnvPXDBfBLEH6u7ptWFdp0GvbSuG2wRaPl
hynHvRiE01ZvwbJZXsPsKm1z7uVoW+NknKLunWKB5axrNXDHxCYJBzY3jTeFjsqx
PFZkIEAQphLTkeXXelAjQ5u9tEshPswEtMvJvUgNiAfbzHfPYmq8D6x5xOw1IySg
2e/LBACxr2UJYCCB2BZ3p508mAB0RpuLGukq+7UWiOizy+kSskIBg2O7sQkVY/Cs
iyGEo4XvXqZFMY39RBdfm2GY+WB/5NFiTOYJRKjfprP6K1YbtsmctsX8dG+foKsD
LLFs7OuVfaydLQYp1iiN6D+LJDSMPM8/LCWzZsgr9EKJ8NXiyrQ6TGludXggTWFu
ZHJha2UgU2VjdXJpdHkgVGVhbSA8c2VjdXJpdHlAbGludXgtbWFuZHJha2UuY29t
PohWBBMRAgAWBQI5aefeBAsKBAMDFQMCAxYCAQIXgAAKCRCaqNDQIkWKmK6LAKCy
/NInDsaMSI+WHwrquwC5PZrcnQCeI+v3gUDsNfQfiKBvQSANu1hdulq5AQ0EOWnn
7xAEAOQlTVY4TiNo5V/iP0J1xnqjqlqZsU7yEBKo/gZz6/+hx75RURe1ebiJ9F77
9FQbpJ9Epz1KLSXvq974rnVb813zuGdmgFyk+ryA/rTR2RQ8h+EoNkwmATzRxBXV
Jb57fFQjxOu4eNjZAtfII/YXb0uyXXrdr5dlJ/3eXrcO4p0XAAMFBACCxo6Z269s
+A4v8C6Ui12aarOQcCDlV8cVG9LkyatU3FNTlnasqwo6EkaP572448weJWwN6SCX
Vl+xOYLiK0hL/6Jb/O9Agw75yUVdk+RMM2I4fNEi+y4hmfMh2siBv8yEkEvZjTcl
3TpkTfzYky85tu433wmKaLFOv0WjBFSikohGBBgRAgAGBQI5aefvAAoJEJqo0NAi
RYqYid0AoJgeWzXrEdIClBOSW5Q6FzqJJyaqAKC0Y9YI3UFlE4zSIGjcFlLJEJGX
lA==
=WxWn
-----END PGP PUBLIC KEY BLOCK-----


----- End forwarded message -----

Regards,
	Dmitry

+-------------------------------------------------------------------------+
Dmitry V. Levin     mailto://ldv@altlinux.ru
Software Engineer   PGP pubkey http://www.fandra.org/users/ldv/pgpkeys.html
ALT Linux Team      http://altlinux.ru
Fandra Project      http://www.fandra.org
+-------------------------------------------------------------------------+
UNIX is user friendly. It's just very selective about who its friends are.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

             reply	other threads:[~2001-03-22  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-22  7:07 Dmitry V. Levin [this message]
2001-03-22 19:00 ` Ivan Zakharyaschev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010322100730.A11121@ldv.office.altlinux.ru \
    --to=ldv@altlinux.ru \
    --cc=devel@linux.iplabs.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

ALT Linux Team development discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
		devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
	public-inbox-index devel

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://lore.altlinux.org/org.altlinux.lists.devel


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git