Author: JT Smith
Uncovering rotor — a shared source CLI
Sun edges towards a Linux binge
Author: JT Smith
Category:
- Linux
Does the future of AI belong to open source Java programs?
Author: JT Smith
Upstart Natural Machine is taking a chance by giving the future of artificial intelligence (AI) to open source Java programmers. In an era when the open source business model is still unproven, Natural Machine is releasing the core of its flagship product, Verbal AI (http://www.naturalmachine.com/products/vai/) under the open source project name of Ai Kernel (AIK) (http://aikernel.sourceforge.net). The company feels the rewards will come from leveraging the shared knowledge of thousands of AI enthusiasts and academia to expand its capabilities in key areas of research such as neural networks, Bayesian networks, natural language processing (NLP) and other computational linguistics. The AIK can be used in conversational computing, robotics, and other advanced computer technologies.
“From the beginning, in 1999, I wanted to release Verbal AI as an open source project, and I think weve found a way to do it,” said Michael Rice, Natural Machines founder and chief software engineer. Today, the product is the engine behind Verbal AIs prompt and respond computing model — combining artificial intelligence, automatic speech recognition (ASR), text to speech (TTS) and VoiceXML technologies.
The AIK is hosted on the leading platform for collaborative open source development, Sourceforge at www.sourceforge.net/projects/aikernel/ and is currently available for free download. As part of the open source effort, the company is currently recruiting assistance from the Java developer community for help in the project.
Additionally, the company has released its latest version of Verbal AI for free download at (http://www.naturalmachine.com).”
Barring the desktop, where should Linux go?
Author: JT Smith
Category:
- Linux
Mail server administration workshop in Everett, Wash.
Author: JT Smith
workshop on Monday, March 18 in Everett, Wash. This workshop covers the basics
of SMTP mail services through the installation
and basic configuration of the widely-used Exim Mail Transfer Agent.
Exim is an open source, featureful, scalable,
and easy-to-configure mail server that runs on various Unix systems.
It is installed by default on several Linux systems and powers many
of the internet’s busiest email servers.
The three hour workshop also covers common techniques for
blocking unsolicited mail and troubleshooting email issues.
The course is one of a series of ongoing open source seminars and
hands-on workshops provided by Puget Sound Technology.
“We’ve seen more and more companies and individuals switch to open source
software as a low-cost and reliable alternative to mainstream
software,” says Heather Reed, Puget Sound Technology vice president.
“We’re offering these seminars and workshops to introduce Linux and BSD
and to provide practical training for busy information technology
professionals.”
Some upcoming workshops include: Introduction to
Linux, BSD and Open Source; Hosting Websites with Apache; Configuring
and Troubleshooting Domain Name (DNS) Services; and Exploring the KDE
Graphical Environment.
Seating is limited.
For more information or to register, visit
http://www.pugetsoundtechnology.com/training/works hops/.
About Puget Sound Technology
Puget Sound Technology is an IT technical support, consulting,
training, and outsourcing company that specializes in BSD, Linux,
free software and open source solutions. Located in the north
Seattle, Wash. area, Puget Sound Technology provides professional
planning and designing, implementation, operations, training, and
maintenance services for computer systems and networks. For more
information, please visit www.pugetsoundtechnology.com.
No more excuses: It’s time to stop using Microsoft products
Author: JT Smith
Miller –
Microsoft management is now threatening to stop shipping Windows completely if the next federal court decision goes against them. This is insane. If I used Windows in my business, I would be working hard to switch to Linux — or Mac or BSD — as fast as I possibly could, just in case Microsoft decides to make good on this threat.
The essence of the whole debate over “punishment” for Microsoft seems to hinge
right now on whether or not Internet Explorer and other Microsoft-supplied doo-dads are essential to the
Windows operating system. The latest Microsoft tantrum goes sort of like this:
“WAAAH! If you let the other kids use whatever browser and instant messenger and things like that they want instead of (sob sob) the one I brought to the playground, I’m going to take my operating system and go home and you won’t be able to play the game at all any more, you nasty bullies. WAAAH!”
This Register
article says the same thing in a slightly less dramatic fashion.
I have friends who work for Microsoft, and they are
perfectly nice people. But I’m sorry, this is over the line. A company that
makes this kind of threat in response to requests that it follow the basic
rules of free enterprise and competitive capitalism — not to mention follow
U.S. law — ticks me off. I don’t know if I can say I now “hate” Microsoft,
but I certainly feel contempt for them. This is, quite simply, despicable
behavior.
If I owned a business that was dependent on Microsoft products, I
would be looking very hard for an alternative. The idea that a single
company, in a fit of petulance, could stop distributing needed updates and
bugfixes to software on which I depended to earn a living would strike fear into my heart. I would, as a simple act of prudence, make sure Microsoft products were not instrumental to the operation of my company. Indeed, a public company that fails to implement alternatives to Microsoft software in light of Microsoft’s latest behavior, and later suffers business interruptions or losses as a result of Microsoft’s childish reactions to judicial orders, could easily get sued by its shareholders.
Maybe it’ll take a few hours and a few moans for the administrative staff to learn to use OpenOffice and other alternatives to Microsoft products. Whoop-tee-doo! Sysadmins only trained in Microsoft products? They’d better start learning something new right away — or stop sysadminning. Maybe you’ll need to look at a list of scanners and printers to make sure you buy ones that are compatible with your new Mac, Linux or whatever other operating system you decide to use in place of the one supplied by the playground bullies at Microsoft. Suck it up and do it. If you are not able to handle these inconveniences in order to guard your operation against Microsoft’s threats, you are not a responsible manager.
If you don’t believe Microsoft might really, truly stop producing and supporting Windows, read this excerpt from a legal deposition by Microsoft CEO Steve Ballmer:
14 The proposal as put forward by the 15 nonsettling states would -- would not be a decree 16 that I would know how to comply with. I actually 17 think we would need to withdraw the Windows product 18 from the marketplace. That -- that would be the 19 only way I understand to comply with the proposal 20 as put forward by the nonsettling states. The 21 degree to which it requires documentation of 22 internal interfaces, the degree to which it 23 requires -- what do they call that stuff where, you 24 know, you can't degrade the performance of anybody 25 else at any time in any way on any interface, and 0042 1 all interfaces, all pieces of the system have to be 2 infinitely replaceable. There -- there's no way 3 to -- not only is there no way to do new effort, 4 new product, new technology, there's simply no way 5 to do that for the existing -- the existing product 6 set. It -- it guarantees that the only way to 7 comply effectively is to remove the product from 8 the market. And -- so you just take the beginning 9 part of the proposal from the nonsettling states 10 and I think it ensures that consumers are harmed. 11 There will be no new Windows, PCs shipped, let 12 alone no new releases of Windows. There just -- I 13 don't -- at least I don't understand any other way 14 to comply with it, and I'm not going to portend I'm 15 a hundred percent expert. We have plenty of people 16 who are studying it and trying to understand it. 17 My number one job today is to make 18 sure I understand the consent decree and make sure 19 we comply with it, because that's -- you know, that 20 is -- that's real and here and now, shall I say, in 21 terms of -- of our -- of our need to execute. But 22 the way my -- my reading of it says, just to start, 23 Windows would be withdrawn from the market, and I 24 think there are -- you know, this year there will 25 be something like 120, 130 million people around 0043 1 the world who buy new computers with Windows, who 2 use those to manage their day-to-day business, 3 their home lives, deliver healthcare information. 4 All of those consumers would be, of course, 5 grievously harmed by the proposal of the non -- the 6 nonsettling states. That's to start.
This is not a low-level flunky talking. This is Microsoft’s chief executive officer!
You may want to read the nonsettling states’ original proposal (pdf format) for yourself. It was modified somewhat on March 4, 2002 — and not in Microsoft’s favor, either.
If you are a professional software developer, do you really want to tie your fortunes to a company that threatens to withdraw the operating system on which your entire income depends from the market if a court decision goes against it? If you write or publish software for a living — especially business software — and your products only work with Windows, you had better start porting to Linux, Unix or Mac — or all three — pretty darn fast, just in case.
Choice is not just good. It’s essential!
If Red Hat decided to stop shipping Red Hat Linux, perhaps because a court told the company it must include both Gnome and KDE on its bootup menus, it would be a minor irritation at most. (I use Red Hat as an example only because it is the best-known Linux distribution publisher, not because I suspect Red Hat management is as juvenile as Microsoft’s.) Linux development would go on. RPM packages would still load and run. Kernel bugs would get fixed, security holes in software packages currently included with Red Hat would continue to be patched. SuSE, Caldera, Mandrake, Lycoris, ELX, Xandros, and all the other commercial Linux distribution publishers would see their business increase, and Debian download servers would be hit hard. But there would still be all the Linux anyone could want, growing and improving, moving forward, powering everything from mainframes and supercomputing clusters to PDAs and other small, special-purpose devices.
No sane business manager would purchase trucks that could only be repaired by one vendor. Today even the U.S. military is trying to move away from single-source contracts and have multiple vendors for critical weapons systems. This is because it is financially foolish (and in the military, dangerous) to put all your eggs in one (supplier’s) basket. Every person who has ever studied business has been taught this basic precept. And yet, due to some amazing mental discontinuity, the same managers who talk knowingly of “alternate supply channels” and “the necessity of multiple vendors” for important products and services make their businesses totally dependent on Microsoft.
Maybe Linux is harder to install than Windows. So it goes. Maybe it doesn’t have some of the “frill” applications that are available for Windows. Too bad. These are minor issues. The most important thing about Linux, from a fiduciary standpoint, is that because of the very lack of a central, dominating corporate presence that has made so many managers scared to stake their business’s future on it, is a far, far, safer bet than an operating system owned, produced, and supported by an illegal monopolist that is now engaging in a white-collar version of blackmail as part of its attempt to wiggle out of well-deserved punishment for its abusive and illegal business practices.
The opinions expressed in this article are strictly those of its author, and may or may not be shared by OSDN’s or VA Software’s management.
Category:
- Migration
LinuxMAX looking for more contributors
Author: JT Smith
So please help us to keep the Open Source community grow and preserve the term ‘FREEDOM.’
— Victoria Nesta, Chief Editor, www.linuxmax.net
SuSE: ‘squid’ update
Author: JT Smith
From: Sebastian Krahmer <krahmer@suse.de>
To: <suse-security-announce@suse.com>
Subject: [suse-security-announce] SuSE Security Announcement: squid (SuSE-SA:2002:008)
Date: Mon, 4 Mar 2002 13:11:39 +0100 (CET)
-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SuSE Security Announcement
Package: squid
Announcement-ID: SuSE-SA:2002:008
Date: Mon Mar 5 13:00:00 CET 2002
Affected SuSE products: 6.4, 7.0, 7.1, 7.2, 7.3,
Enterprise Server 7
Vulnerability Type: remote command execution
Severity (1-10): 6
SuSE default package: no
Other affected systems: all systems running vulnerable squid
Content of this advisory:
1) security vulnerability resolved: Heap overflow in squid.
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds
3) standard appendix (further information)
______________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
The widely used proxy-server squid contains a heap overflow in one of its
URL constructing functions. Incorrect length-calculations for the user and
passwd fields in ftp-URLs turned out to be the origin of the problem. Only
users from hosts listed in squids ACL-files could trigger the overflow.
The ftp-URL problem is not present in the 6.4, 7.0 and 7.1 distributions,
but other security releated bugs have been fixed there.
A complete history can be found at
http://www.squid-cache.org/Versions/v2/2.4/bugs/
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update. For users of our SLES-based products, please use the yast
online update.
For the updates to take effect, invoke the following command as root:
/etc/rc.d/squid restart
If you added the htcp_port directive to your squid configuration file
you might now see a warning in the logs about that directive being
unrecognized. While this does not prevent squid from starting, you can
safely remove the directive from squid.conf since HTCP support is
disabled now.
Please note that there are two binary and two source packages for almost
every distribution available.
i386 Intel Platform:
SuSE-7.3
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/squid-2.3.STABLE4-155.i386.rpm
4b1cff53fddcaf8930ec6738c6763a94
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/squid-beta-2.4.STABLE2-94.i386.rpm
4ca7f3594ec82b703c6c36c08fb46ecb
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/squid-2.3.STABLE4-155.src.rpm
3751569a6c0ea21057d37cb7d3ca9076
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/squid-beta-2.4.STABLE2-94.src.rpm
99f33e8d1e5b8a3e8d7f6501d26c6e67
SuSE-7.2
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/squid-2.3.STABLE4-155.i386.rpm
1f098dcb1020df788cc912d88f14bb96
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/squid-beta-2.4.STABLE1-100.i386.rpm
cc136eeaf6ed4ac305e93d306e6f7461
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/squid-2.3.STABLE4-155.src.rpm
d3fae41b9128f73a0e457376bfb7a5c1
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/squid-beta-2.4.STABLE1-100.src.rpm
c24bf7c45b227b06ae1013dd6fcb9d92
SuSE-7.1
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/squid2-2.2.STABLE5-218.i386.rpm
5a7b26c99855837331e2d375901a5fce
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/squid23-2.3.STABLE4-75.i386.rpm
f3a4a2e8d9fa4b56948e8a8d2bc6e2a0
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/squid2-2.2.STABLE5-218.src.rpm
6c208e3f13da8d93fecfdca62c98f46f
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/squid23-2.3.STABLE4-75.src.rpm
ad588c92719bffbc02e72fddf6195dd2
SuSE-7.0
ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/squid2-2.2.STABLE5-218.i386.rpm
f12ae33fd707f4ea86a48a77f48fafc8
ftp://ftp.suse.com/pub/suse/i386/update/7.0/n1/squid23-2.3.STABLE4-75.i386.rpm
069c07843355ee473b8b4e10b6726455
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/squid2-2.2.STABLE5-218.src.rpm
5a2a5f0511cfd75f736ef485bcf6e5a1
ftp://ftp.suse.com/pub/suse/i386/update/7.0/zq1/squid23-2.3.STABLE4-75.src.rpm
d4bc56dc9240f5ab9582b746c5c18803
SuSE-6.4
ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/squid2-2.2.STABLE5-219.i386.rpm
13a3e9a366d3e09ee6dcc91148c86be7
ftp://ftp.suse.com/pub/suse/i386/update/6.4/n1/squid23-2.3.STABLE4-76.i386.rpm
53b7ab8cfad2f14b211e1d505d721558
source rpm:
ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/squid2-2.2.STABLE5-219.src.rpm
a9b0af504703aa7deeb2e0f6b7b0f512
ftp://ftp.suse.com/pub/suse/i386/update/6.4/zq1/squid23-2.3.STABLE4-76.src.rpm
fbe64c6fbe15e4a9d06847089bb65d13
Sparc Platform:
SuSE-7.3
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/squid-2.3.STABLE4-53.sparc.rpm
99bf4711c8e781622fd3aba55f21ae5a
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/squid-2.3.STABLE4-53.src.rpm
d56d66c2fd92efa157b98efb1bf6a0c6
SuSE-7.1
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/squid2-2.2.STABLE5-208.sparc.rpm
f6948f9862addc8d6805311b5760c95a
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/n2/squid23-2.3.STABLE4-60.sparc.rpm
e6e9bf05539791905710ffb23fbd4801
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/squid2-2.2.STABLE5-208.src.rpm
1ad2798d085326317590e0fb42346fa9
ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/squid23-2.3.STABLE4-60.src.rpm
1332572acea60f0c6ca1593fcd245771
SuSE-7.0
ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/squid2-2.2.STABLE5-207.sparc.rpm
1958de7d7f90d27c87e1dc1b21879736
ftp://ftp.suse.com/pub/suse/sparc/update/7.0/n1/squid23-2.3.STABLE4-60.sparc.rpm
a54038090e73a78a6f3cc77e1162e4a2
source rpm:
ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/squid2-2.2.STABLE5-207.src.rpm
3a398a096c2657059a093dcf58222e35
ftp://ftp.suse.com/pub/suse/sparc/update/7.0/zq1/squid23-2.3.STABLE4-60.src.rpm
7e1483d0b41f48ef3aa00e058b0e761f
AXP Alpha Platform:
SuSE-7.1
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/squid2-2.2.STABLE5-225.alpha.rpm
7f39d3a0ff45f231713c6ba5afbdcc15
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/squid23-2.3.STABLE4-74.alpha.rpm
5fe79d7f9c2da83222978f75e3387e49
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/squid2-2.2.STABLE5-225.src.rpm
705a5b370267d8d873f1e3504bcc55ed
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/squid23-2.3.STABLE4-74.src.rpm
e42367f3ad73250ec9feda4687b406d2
SuSE-7.0
ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/squid2-2.2.STABLE5-226.alpha.rpm
b0977f9c5ed0750b12308d072da1b285
ftp://ftp.suse.com/pub/suse/axp/update/7.0/n1/squid23-2.3.STABLE4-74.alpha.rpm
3906c0d918c745582a25fb1c480d3aef
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/squid2-2.2.STABLE5-226.src.rpm
2afd7d60f6da4feb346ddfefc8bec34a
ftp://ftp.suse.com/pub/suse/axp/update/7.0/zq1/squid23-2.3.STABLE4-74.src.rpm
cab334bf697df713d847ae8c569b7b30
SuSE-6.4
ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/squid2-2.2.STABLE5-227.alpha.rpm
1bc4ac5b27e3cfd62766d0258f91090a
ftp://ftp.suse.com/pub/suse/axp/update/6.4/n1/squid23-2.3.STABLE4-75.alpha.rpm
b809b2523881fbea1f77f3f5b96879c5
source rpm:
ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/squid2-2.2.STABLE5-227.src.rpm
7d6d942bc8b4208fe610f714868009d8
ftp://ftp.suse.com/pub/suse/axp/update/6.4/zq1/squid23-2.3.STABLE4-75.src.rpm
515cb7434886540fae57c5ac56acbb42
PPC Power PC Platform:
SuSE-7.3
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/squid-2.3.STABLE4-71.ppc.rpm
2a14453696ced035fb21d272f7619a5c
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/squid-beta-2.4.STABLE2-59.ppc.rpm
ceda7a8a291d8b3d01127b4e0fb1ccb2
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/squid-2.3.STABLE4-71.src.rpm
5427dd36485bdfb0d67060c9bad62127
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/squid-beta-2.4.STABLE2-59.src.rpm
a572e3f76e68a3577e6a4efe0ec016ae
SuSE-7.1
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/squid2-2.2.STABLE5-200.ppc.rpm
a8e274378dc15aab4ca01760c112b770
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/squid23-2.3.STABLE4-68.ppc.rpm
133528338cb5253a12132e3e9ec2ee2e
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/squid2-2.2.STABLE5-200.src.rpm
515cb7e5f04cd5980463a8b3f248e08e
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/squid23-2.3.STABLE4-68.src.rpm
b923a7141e0fb4b1f3b6e6d0185cb4aa
SuSE-7.0
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/squid2-2.2.STABLE5-200.ppc.rpm
2b301c87d0d2e1546cb6a63427dc9cea
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/n1/squid23-2.3.STABLE4-68.ppc.rpm
20eef813e618d3ac3e8e24abcaca894c
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/squid2-2.2.STABLE5-200.src.rpm
7d41eaa9985c49cec7afb76dd29355e7
ftp://ftp.suse.com/pub/suse/ppc/update/7.0/zq1/squid23-2.3.STABLE4-68.src.rpm
11bb4cb51a8abf8ebe994dc08f8a7c24
SuSE-6.4
ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/squid2-2.2.STABLE5-200.ppc.rpm
e8020a0a7153208e58f202b0655f1ce5
ftp://ftp.suse.com/pub/suse/ppc/update/6.4/n1/squid23-2.3.STABLE4-68.ppc.rpm
efd648b5575b6fce60cd7403fbb15d5a
source rpm:
ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/squid2-2.2.STABLE5-200.src.rpm
521d058bc1513947642f74a121e4e98b
ftp://ftp.suse.com/pub/suse/ppc/update/6.4/zq1/squid23-2.3.STABLE4-68.src.rpm
8c9bf3882aa81c7de4b2b920f31e4f69
______________________________________________________________________________
2) Pending vulnerabilities in SuSE Distributions and Workarounds:
- ucd-snmpd
The UCD snmpd contains various security releated bugs.
We are currently reviewing the code and available fixes to ensure
they all get fixed. Patches will be available as soon as possible.
It is strongly recommended to filter SNMP (TCP and UDP packets
with destination of port 161) traffic.
- hanterm/wmtv
The recently reported vulnerabilities in hanterm and wmtv do not
affect SuSE installations because they are not installed setuid
or setgid.
- cipe
We are about to prepare kernel update packages that fix a DoS
problem in the kernel modules for the cipe encrypted tunneling software.
______________________________________________________________________________
3) standard appendix: authenticity verification, additional information
- Package authenticity verification:
SuSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. 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) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) execute the command
md5sum <name-of-the-file.rpm>
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
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an uninstalled rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SuSE in rpm packages for SuSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SuSE Linux distributions version 7.1 and thereafter install the
key "build@suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the toplevel directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SuSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- general/linux/SuSE security discussion.
All SuSE security announcements are sent to this list.
To subscribe, send an email to
<suse-security-subscribe@suse.com>.
suse-security-announce@suse.com
- SuSE's announce-only mailing list.
Only SuSE's security annoucements are sent to this list.
To subscribe, send an email to
<suse-security-announce-subscribe@suse.com>.
For general information or the frequently asked questions (faq)
send mail to:
<suse-security-info@suse.com> or
<suse-security-faq@suse.com> respectively.
=====================================================================
SuSE's security contact is <security@suse.com> or <security@suse.de>.
The <security@suse.de> 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,
it is desired that the cleartext signature shows proof of the
authenticity of the text.
SuSE GmbH makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
mQGiBDnu9IERBACT8Y35+2vv4MGVKiLEMOl9GdST6MCkYS3yEKeueNWc+z/0Kvff
4JctBsgs47tjmiI9sl0eHjm3gTR8rItXMN6sJEUHWzDP+Y0PFPboMvKx0FXl/A0d
M+HFrruCgBlWt6FA+okRySQiliuI5phwqkXefl9AhkwR8xocQSVCFxcwvwCglVcO
QliHu8jwRQHxlRE0tkwQQI0D+wfQwKdvhDplxHJ5nf7U8c/yE/vdvpN6lF0tmFrK
XBUX+K7u4ifrZlQvj/81M4INjtXreqDiJtr99Rs6xa0ScZqITuZC4CWxJa9GynBE
D3+D2t1V/f8l0smsuYoFOF7Ib49IkTdbtwAThlZp8bEhELBeGaPdNCcmfZ66rKUd
G5sRA/9ovnc1krSQF2+sqB9/o7w5/q2qiyzwOSTnkjtBUVKn4zLUOf6aeBAoV6NM
CC3Kj9aZHfA+ND0ehPaVGJgjaVNFhPi4x0e7BULdvgOoAqajLfvkURHAeSsxXIoE
myW/xC1sBbDkDUIBSx5oej73XCZgnj/inphRqGpsb+1nKFvF+rQoU3VTRSBQYWNr
YWdlIFNpZ25pbmcgS2V5IDxidWlsZEBzdXNlLmRlPohcBBMRAgAcBQI57vSBBQkD
wmcABAsKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyl8sAJ98BgD40zw0GHJHIf6d
NfnwI2PAsgCgjH1+PnYEl7TFjtZsqhezX7vZvYCIRgQQEQIABgUCOnBeUgAKCRCe
QOMQAAqrpNzOAKCL512FZvv4VZx94TpbA9lxyoAejACeOO1HIbActAevk5MUBhNe
LZa/qM2JARUDBRA6cGBvd7LmAD0l09kBATWnB/9An5vfiUUE1VQnt+T/EYklES3t
XXaJJp9pHMa4fzFa8jPVtv5UBHGee3XoUNDVwM2OgSEISZxbzdXGnqIlcT08TzBU
D9i579uifklLsnr35SJDZ6ram51/CWOnnaVhUzneOA9gTPSr+/fT3WeVnwJiQCQ3
0kNLWVXWATMnsnT486eAOlT6UNBPYQLpUprF5Yryk23pQUPAgJENDEqeU6iIO9Ot
1ZPtB0lniw+/xCi13D360o1tZDYOp0hHHJN3D3EN8C1yPqZd5CvvznYvB6bWBIpW
cRgdn2DUVMmpU661jwqGlRz1F84JG/xe4jGuzgpJt9IXSzyohEJB6XG5+D0BiF0E
ExECAB0FAjxqqTQFCQoAgrMFCwcKAwQDFQMCAxYCAQIXgAAKCRCoTtronIAKyp1f
AJ9dR7saz2KPNwD3U+fy/0BDKXrYGACfbJ8fQcJqCBQxeHvt9yMPDVq0B0W5Ag0E
Oe70khAIAISR0E3ozF/la+oNaRwxHLrCet30NgnxRROYhPaJB/Tu1FQokn2/Qld/
HZnh3TwhBIw1FqrhWBJ7491iAjLR9uPbdWJrn+A7t8kSkPaF3Z/6kyc5a8fas44h
t5h+6HMBzoFCMAq2aBHQRFRNp9Mz1ZvoXXcI1lk1l8OqcUM/ovXbDfPcXsUVeTPT
tGzcAi2jVl9hl3iwJKkyv/RLmcusdsi8YunbvWGFAF5GaagYQo7YlF6UaBQnYJTM
523AMgpPQtsKm9o/w9WdgXkgWhgkhZEeqUS3m5xNey1nLu9iMvq9M/iXnGz4sg6Q
2Y+GqZ+yAvNWjRRou3zSE7Bzg28MI4sAAwYH/2D71Xc5HPDgu87WnBFgmp8MpSr8
QnSs0wwPg3xEullGEocolSb2c0ctuSyeVnCttJMzkukL9TqyF4s/6XRstWirSWaw
JxRLKH6Zjo/FaKsshYKf8gBkAaddvpl3pO0gmUYbqmpQ3xDEYlhCeieXS5MkockQ
1sj2xYdB1xO0ExzfiCiscUKjUFy+mdzUsUutafuZ+gbHog1CN/ccZCkxcBa5IFCH
ORrNjq9pYWlrxsEn6ApsG7JJbM2besW1PkdEoxak74z1senh36m5jQvVjA3U4xq1
wwylxadmmJaJHzeiLfb7G1ZRjZTsB7fyYxqDzMVul6o9BSwO/1XsIAnV1uuITAQY
EQIADAUCOe70kgUJA8JnAAAKCRCoTtronIAKyksiAJsFB3/77SkH3JlYOGrEe1Ol
0JdGwACeKTttgeVPFB+iGJdiwQlxasOfuXyITAQYEQIADAUCPGqpWQUJCgCCxwAK
CRCoTtronIAKyofBAKCSZM2UFyta/fe9WgITK9I5hbxxtQCfX+0ar2CZmSknn3co
SPihn1+OBNyZAQ0DNuEtBAAAAQgAoCRcd7SVZEFcumffyEwfLTcXQjhKzOahzxpo
omuF+HIyU4AGq+SU8sTZ/1SsjhdzzrSAfv1lETACA+3SmLr5KV40Us1w0UC64cwt
A46xowVq1vMlH2Lib+V/qr3b1hE67nMHjysECVx9Ob4gFuKNoR2eqnAaJvjnAT8J
/LoUC20EdCHUqn6v+M9t/WZgC+WNR8cq69uDy3YQhDP/nIan6fm2uf2kSV9A7ZxE
GrwsWl/WX5Q/sQqMWaU6r4az98X3z90/cN+eJJ3vwtA+rm+nxEvyev+jaLuOQBDf
ebh/XA4FZ35xmi+spdiVeJH4F/ubaGlmj7+wDOF3suYAPSXT2QAFEbQlU3VTRSBT
ZWN1cml0eSBUZWFtIDxzZWN1cml0eUBzdXNlLmRlPokBFQMFEDbhLUfkWLKHsco8
RQEBVw4H/1vIdiOLX/7hdzYaG9crQVIk3QwaB5eBbjvLEMvuCZHiY2COUg5QdmPQ
8SlWNZ6k4nu1BLcv2g/pymPUWP9fG4tuSnlUJDrWGm3nhyhAC9iudP2u1YQY37Gb
B6NPVaZiYMnEb4QYFcqv5c/r2ghSXUTYk7etd6SW6WCOpEqizhx1cqDKNZnsI/1X
11pFcO2N7rc6byDBJ1T+cK+F1Ehan9XBt/shryJmv04nli5CXQMEbiqYYMOu8iaA
8AWRgXPCWqhyGhcVD3LRhUJXjUOdH4ZiHCXaoF3zVPxpeGKEQY8iBrDeDyB3wHmj
qY9WCX6cmogGQRgYG6yJqDalLqrDOdmJARUDBRA24S0Ed7LmAD0l09kBAW04B/4p
WH3f1vQn3i6/+SmDjGzUu2GWGq6Fsdwo2hVM2ym6CILeow/K9JfhdwGvY8LRxWRL
hn09j2IJ9P7H1Yz3qDf10AX6V7YILHtchKT1dcngCkTLmDgC4rs1iAAl3f089sRG
BafGPGKv2DQjHfR1LfRtbf0P7c09Tkej1MP8HtQMW9hPkBYeXcwbCjdrVGFOzqx+
AvvJDdT6a+oyRMTFlvmZ83UV5pgoyimgjhWnM1V4bFBYjPrtWMkdXJSUXbR6Q7Pi
RZWCzGRzwbaxqpl3rK/YTCphOLwEMB27B4/fcqtBzgoMOiaZA0M5fFoo54KgRIh0
zinsSx2OrWgvSiLEXXYKiEYEEBECAAYFAjseYcMACgkQnkDjEAAKq6ROVACgjhDM
/3KM+iFjs5QXsnd4oFPOnbkAnjYGa1J3em+bmV2aiCdYXdOuGn4ZiQCVAwUQN7c7
whaQN/7O/JIVAQEB+QP/cYblSAmPXxSFiaHWB+MiUNw8B6ozBLK0QcMQ2YcL6+Vl
D+nSZP20+Ja2nfiKjnibCv5ss83yXoHkYk2Rsa8foz6Y7tHwuPiccvqnIC/c9Cvz
dbIsdxpfsi0qWPfvX/jLMpXqqnPjdIZErgxpwujas1n9016PuXA8K3MJwVjCqSKI
RgQQEQIABgUCOhpCpAAKCRDHUqoysN/3gCt7AJ9adNQMbmA1iSYcbhtgvx9ByLPI
DgCfZ5Wj+f7cnYpFZI6GkAyyczG09sE=
=LRKC
- -----END PGP PUBLIC KEY BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv
iQEVAwUBPINe7Hey5gA9JdPZAQGDuQf+PIbXwU/pUs88pt5DjLvZHeG9Tna1so2r
STXBudCW+B/RvBHyFq5kjvaAYwMlBcXl/9V88rEbMF3DhFiYnxndDFb0Z6A0ItCZ
w0+cS0lOC1okXi2NFCma+YiIBV1zwlUF6cj/zehG/D0oOM8rydhq4gYO2SX1cLFV
KCbCB035zeYQN9uL18E4SHsNT6RIyN94k9zDs6JmSBxpCFVBUPQslx86MwI2ccOM
rD3yXlXNT7Iw5kPe5G3DZA6NuGvkfVbFhXzAfyu/xRqcLdTdaf962M5dqz7f+U1g
C4G606sqHg/AS9nf2MhLgHoCfUi3vO+ag62Xvrjo3nZ9sBdtuGjqgw==
=AlQv
-----END PGP SIGNATURE-----
--
~
~ perl self.pl
~ $_='print"$_=47$_47;eval"';eval
~ krahmer@suse.de - SuSE Security Team
~
--
To unsubscribe, e-mail: suse-security-announce-unsubscribe@suse.com
For additional commands, e-mail: suse-security-announce-help@suse.com
Category:
- Linux
Sun releases Abicheck under the LGPL
Author: JT Smith
Looping emails: Latest scourge of the Internet?
Author: JT Smith