r u guys doing something on serial port modem connectivity also..

----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, October 15, 2004 8:11 AM
Subject: ilugd Digest, Vol 19, Issue 21


> Send ilugd mailing list submissions to
> [EMAIL PROTECTED]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://frodo.hserus.net/mailman/listinfo/ilugd
> or, via email, send a message with subject or body 'help' to
> [EMAIL PROTECTED]
>
> You can reach the person managing the list at
> [EMAIL PROTECTED]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ilugd digest..."
>
>
> Please trim replies before posting.
>
> Today's Topics:
>
>    1. Re: DNS help (Sibayan Das)
>    2. Re: Re: [RANT & Maybe OT] Wired - weird India (vivek khurana)
>    3. Re: Re: [RANT & Maybe OT] Wired - weird India
>       (Sandip Bhattacharya)
>    4. Re: Hallofshame web page (was) Re: [ilugd] Re: [RANT & Maybe
>       OT] Wired - weird India (Sandip Bhattacharya)
>    5. (fwd) [SECURITY] [DSA 566-1] New CUPS packages fix
>       information leak (Raj Mathur)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 14 Oct 2004 12:22:46 -0500
> From: Sibayan Das <[EMAIL PROTECTED]>
> Subject: Re: [ilugd] DNS help
> To: selvarajan k <[EMAIL PROTECTED]>, The Linux-Delhi
> mailing list <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII
>
> hello there
>
> what exactly do you want to know about it?
>
> regards
>
>
> On 14 Oct 2004 14:19:28 -0000, selvarajan k <[EMAIL PROTECTED]>
wrote:
> >
> > for running BIND (9) in a
> >
> > chroot jail
> >
> > i.e, for the unpriveledged users
> > can any one help me
> > _______________________________________________
> > ilugd mailinglist -- [EMAIL PROTECTED]
> > http://frodo.hserus.net/mailman/listinfo/ilugd
> > Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi
http://www.mail-archive.com/[EMAIL PROTECTED]/
> >
>
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 14 Oct 2004 11:07:34 -0700 (PDT)
> From: vivek khurana <[EMAIL PROTECTED]>
> Subject: Re: [ilugd] Re: [RANT & Maybe OT] Wired - weird India
> To: The Linux-Delhi mailing list <[EMAIL PROTECTED]>
> Cc: Linux-India-help <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
>
>
>
> > That is the whole point isnt it? These companies
> > develop websites, and test
> > it solely on IE, and dont even care for other
> > browsers like Netscape, Opera
> > etc.
>
>  Okay so this means they are using a flawed
> development model, but it is insufficient to prove
> that the are pro M$ or are blocking no-IE browsers.
> There is no code in the main page which is blocking
> any browser. Absolutely no broser identification is
> used anywhere.
>
>  Ya, the tag used is not specified in w3c standard but
> it doesnot require any special libraries (MS specific)
> to be displayed as hyperlink.
> >
> > The point of that hallofshame webpage is to point
> > out instances where the
> > said entity doesnt bother making their
> > services/products accessible on
> > non-IE browsers. It doesnt matter what is causing
> > the problem - in most
> > cases, these entities dont bother using standard
> > compatible code.
> >
> > For them IE is the standard, and any browsers which
> > doesnt support
> > everything that IE supports is non-standard.
> > Somewhat similar to what you
> > wrote in your mail.
> >
> > The point of this drive is to publicise the fact
> > that there is a world
> > outside IE which is trying to use their websites.
> > Other issues that are
> > worth pointing out is when important websites like
> > banks, etc. are not
> > accessible by people with disabilities like
> > color-blindness, etc. Not being
> > accessible by any kind of people is discrimination,
> > something similar to
> > "You can enter this premises, because you are not
> > wearing a shirt and tie".
> >
>
>  What kind of awareness wil you generate by putting a
> website directly into "hall of shame" without giving
> them a chance to respond. Has anyone reported the
> mater to icicidirect.com? Did they declined to make
> changes which will make there website work with other
> browser? Do the authorities at icicidirect.com even
> have a slight idea about standards or are they even
> aware of other browsers? You can't assume they want to
> disallow other browsers. You cant assume they are even
> aware of other browsers, just because you know they
> exist.You can't make someone guilty till proven
> innocent ;-)
>  Most of the companies outsource such work and have no
> knowledge of w3c standards or any standard infact. For
> institutions such as the party under consideration use
>  technology as a marketing tool. they have an idea in
> mind about the kind of service they want to provide to
>  end user and they simply outsource such work. It ould
> turn out that icicidirect.com is unawre of this flaw
> (which i still belive is nothing more than a minor
> bug) The way to ensure standards are followed is to
> first make higher authorities in an organization aware
> of the standards and if they still are reluctant and
> adhere to some proprietory standard put themin
> whatever list you want to .
>  By putting an organization into a list like this or
> posting suggestions like dragging them to consumer
> court, without giving them a chance to respond,
> paramounts to a libel. We are ourselves providing
> material for bad press regarding linux and linux users
> to other party.
>
>  What if we get bad press due to such actions? Will an
> end user even think of using linux if other party
> projects linux users as militant?
>
>  Even i agree that we need a list like hall of shame
> but we have to be very specific under what conditions
> website, ISP or vendor will be added to the list. Just
> remember this will be a public list and entry into
> such a list will have negative impact on the party
> involved, so all i want to recomend is just be
> careful!!
>
> Regards
> VK
>
> PS:- I am no way, directly or indirectly, involved
> with www.icicidirect.com.
>
> =====
> Hug the REALITY ;-)
>
>
>
> Disclamer
> The facts expressed here belong to everybody, the opinions to me. The
distinction is yours to draw...
>
>
>
> _______________________________
> Do you Yahoo!?
> Declare Yourself - Register online to vote today!
> http://vote.yahoo.com
>
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 15 Oct 2004 00:10:34 +0530
> From: Sandip Bhattacharya <[EMAIL PROTECTED]>
> Subject: Re: [ilugd] Re: [RANT & Maybe OT] Wired - weird India
> To: The Linux-Delhi mailing list <[EMAIL PROTECTED]>
> Cc: Linux-India-help <[EMAIL PROTECTED]>
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> I have already addressed much of the points of this mail in a previous
mail
> at http://article.gmane.org/gmane.user-groups.linux.delhi/7253
>
> vivek khurana wrote:
> >> That is the whole point isnt it? These companies
> >> develop websites, and test
> >> it solely on IE, and dont even care for other
> >> browsers like Netscape, Opera
> >> etc.
> >
> >  Okay so this means they are using a flawed
> > development model, but it is insufficient to prove
> > that the are pro M$ or are blocking no-IE browsers.
> > There is no code in the main page which is blocking
> > any browser. Absolutely no broser identification is
> > used anywhere.
>
> I dont understand. The page has code which works only on IE. It is
> preventing other browsers to access the page by using non-standard
> IE-specific code. Yes, they are not "actively" blocking browsers by
> checking browser identification like many other sites do. But isnt being
> proprietary being anti-choice? It is taking away the visitors right of
> using the browser of their choice.
>
> >
> >  Ya, the tag used is not specified in w3c standard but
> > it doesnot require any special libraries (MS specific)
> > to be displayed as hyperlink.
>
> Who said that incompatibility/lanck-of-interoperability only has to be at
> binary level?
>
> >> The point of this drive is to publicise the fact
> >> that there is a world
> >> outside IE which is trying to use their websites.
> >> Other issues that are
> >> worth pointing out is when important websites like
> >> banks, etc. are not
> >> accessible by people with disabilities like
> >> color-blindness, etc. Not being
> >> accessible by any kind of people is discrimination,
> >> something similar to
> >> "You can enter this premises, because you are not
> >> wearing a shirt and tie".
> >>
> >
> >  What kind of awareness wil you generate by putting a
> > website directly into "hall of shame" without giving
> > them a chance to respond. Has anyone reported the
> > mater to icicidirect.com? Did they declined to make
> > changes which will make there website work with other
> > browser?
>
> I have acknowleged this in my earlier mail to ILUGD which you must have
> read before sending this mail.
>
>
> >Do the authorities at icicidirect.com even
> > have a slight idea about standards or are they even
> > aware of other browsers? You can't assume they want to
> > disallow other browsers. You cant assume they are even
> > aware of other browsers, just because you know they
> > exist.You can't make someone guilty till proven
> > innocent ;-)
>
> Ignorance is not always good excuse. I dont believe that other than real
> newbies, people are unaware of other browsers. Especially, any person who
> has spent even a single day at any web development outfit, will know of
> non-IE browsers. This is simply a case of convenient ignorance. There are
> many, more obvious ways to do the particular non-standard code at
> icicidirect.com in a more standard way.
>
> >  By putting an organization into a list like this or
> > posting suggestions like dragging them to consumer
> > court, without giving them a chance to respond,
> > paramounts to a libel. We are ourselves providing
> > material for bad press regarding linux and linux users
> > to other party.
>
> I dont think so. We have every right to complain when we have been
> discriminated with, out of or without ignorance. This list is a form of
> protest.
>
> >
> >  What if we get bad press due to such actions? Will an
> > end user even think of using linux if other party
> > projects linux users as militant?
>
> There is nothing militant about this. Think of this as the Internet way of
> having a "morcha" or "procession". :)
>
> >
> >  Even i agree that we need a list like hall of shame
> > but we have to be very specific under what conditions
> > website, ISP or vendor will be added to the list. Just
> > remember this will be a public list and entry into
> > such a list will have negative impact on the party
> > involved, so all i want to recomend is just be
> > careful!!
>
>
> I have dwelled on these points in the mail I mentioned before, at
> http://article.gmane.org/gmane.user-groups.linux.delhi/7253.
>
> - Sandip
>
> --
> Sandip Bhattacharya    *    Puroga Technologies   *     [EMAIL PROTECTED]
> Work: http://www.puroga.com        *         Home: http://www.sandipb.net
>
> PGP/GPG Signature: 51A4 6C57 4BC6 8C82 6A65 AE78 B1A1 2280 A129 0FF3
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Fri, 15 Oct 2004 01:12:07 +0530
> From: Sandip Bhattacharya <[EMAIL PROTECTED]>
> Subject: Re: Hallofshame web page (was) Re: [ilugd] Re: [RANT & Maybe
> OT] Wired - weird India
> To: The Linux-Delhi mailing list <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Sandip Bhattacharya wrote:
> >
> > I think we should have a policy for two kinds of "offenses".
> >
>
> I have tried to setup a policy[1] for the HallofShame page, and have
> removed icicidirect.com from the list for the time being .. in accordance
> with the policy.
>
> [1] http://www.lug-delhi.org/HallOfShame
>
> - Sandip
>
> --
> Sandip Bhattacharya    *    Puroga Technologies   *     [EMAIL PROTECTED]
> Work: http://www.puroga.com        *         Home: http://www.sandipb.net
>
> PGP/GPG Signature: 51A4 6C57 4BC6 8C82 6A65 AE78 B1A1 2280 A129 0FF3
>
>
>
>
> ------------------------------
>
> Message: 5
> Date: Fri, 15 Oct 2004 08:04:59 +0530
> From: Raj Mathur <[EMAIL PROTECTED]>
> Subject: [ilugd] (fwd) [SECURITY] [DSA 566-1] New CUPS packages fix
> information leak
> To: [EMAIL PROTECTED],
> [EMAIL PROTECTED]
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=us-ascii
>
> [Please upgrade if you have CUPS installed on any distribution; this
> is not the same as the vulnerability reported in September.
>
> Also note the recommendations given regarding authentication
> information in device URIs -- Raju]
>
> This is an RFC 1153 digest.
> (1 message)
> ----------------------------------------------------------------------
>
> Message-Id: <[EMAIL PROTECTED]>
> From: [EMAIL PROTECTED]
> Sender: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: [Full-Disclosure] [SECURITY] [DSA 566-1] New CUPS packages fix
information leak
> Date: Thu, 14 Oct 2004 17:27:26 +0200 (CEST)
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> - ------------------------------------------------------------------------
--
> Debian Security Advisory DSA 566-1                     [EMAIL PROTECTED]
> http://www.debian.org/security/                             Martin Schulze
> October 14th, 2004                      http://www.debian.org/security/faq
> - ------------------------------------------------------------------------
--
>
> Package        : cupsys
> Vulnerability  : unsanitised input
> Problem-Type   : local
> Debian-specific: no
> CVE ID         : CAN-2004-0923
> CERT advisory  : VU#557062
>
> An information leak has been detected in CUPS, the Common UNIX
> Printing System, which may lead to the disclosure of sensitive
> information, such as user names and passwords which are written into
> log files.
>
> The used patch only eliminates the authentication information in the
> device URI which is logged in the error_log file.  It does not
> eliminate the URI from the environment and process table, which is why
> the CUPS developers recommend that system administrators do not code
> authentication information in device URIs in the first place.
>
> For the stable distribution (woody) this problem has been fixed in
> version 1.1.14-5woody7.
>
> For the unstable distribution (sid) this problem has been fixed in
> version 1.1.20final+rc1-9.
>
> We recommend that you upgrade your CUPS 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 3.0 alias woody
> - --------------------------------
>
>   Source archives:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7.
dsc
>       Size/MD5 checksum:      710 cc64cacbd7546a5609d78f47dbcd0e78
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7.
diff.gz
>       Size/MD5 checksum:    39147 90020c9ccf4c20d75545d2b9fc804f12
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14.orig.tar
.gz
>       Size/MD5 checksum:  6150756 0dfa41f29fa73e7744903b2471d2ca2f
>
>   Alpha architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
alpha.deb
>       Size/MD5 checksum:  1899802 4f68d49c505e401ec65c45fc89baaef0
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_alpha.deb
>       Size/MD5 checksum:    74186 87538022f3f049de24a67524f6b6e374
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_alpha.deb
>       Size/MD5 checksum:    92828 a97dec155e925386ec24723825fb821b
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_alpha.deb
>       Size/MD5 checksum:  2445680 b0ee9dc5e73ab807fc4befa4f62ed2e4
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_alpha.deb
>       Size/MD5 checksum:   137850 4c95ecf39a123d7fc2b20a11471478d4
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_alpha.deb
>       Size/MD5 checksum:   180786 1daecceb7cfdce5a2715ae10cd227c0d
>
>   ARM architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
arm.deb
>       Size/MD5 checksum:  1821486 8e7f3aca59e978f96d5d85ed7d9b132c
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_arm.deb
>       Size/MD5 checksum:    68322 6cb0d1d79e7c630e62a316f9991d04c6
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_arm.deb
>       Size/MD5 checksum:    85500 303f4eb613479f112c84f496190c9b72
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_arm.deb
>       Size/MD5 checksum:  2345676 99216618a594ee5bb5a87c3023428355
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_arm.deb
>       Size/MD5 checksum:   112826 52e2ea3acbdcfdb3b0182833b5713541
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_arm.deb
>       Size/MD5 checksum:   150236 b49e83f022a165d4a1c84b757d3f9292
>
>   Intel IA-32 architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
i386.deb
>       Size/MD5 checksum:  1788306 a96f7bf460aa90e3f26e0a0dff99090d
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_i386.deb
>       Size/MD5 checksum:    67852 ee72adda3436557359f244a48088ee5d
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_i386.deb
>       Size/MD5 checksum:    84012 fdcfac62cfdd73d412a82d6f7d4d5659
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_i386.deb
>       Size/MD5 checksum:  2311820 8fe69ac7ea5cf3fb82f25387a6c3be71
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_i386.deb
>       Size/MD5 checksum:   110854 3e9c9b1102844a6f82c853682b1c2e77
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_i386.deb
>       Size/MD5 checksum:   136426 827b43571bfed94ccf6e7dd6d423d1b8
>
>   Intel IA-64 architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
ia64.deb
>       Size/MD5 checksum:  2007756 3a4d0833b9efea469ff3a839ecb699a9
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_ia64.deb
>       Size/MD5 checksum:    77250 aec887b9d536409c3888be0519b92e4f
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_ia64.deb
>       Size/MD5 checksum:    96978 b4088ed3cbdf7707e1454761fa737ae7
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_ia64.deb
>       Size/MD5 checksum:  2656628 3d1c5e6c5d9e690eb365051e2b547a38
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_ia64.deb
>       Size/MD5 checksum:   155830 c57c5e454626ab01a048ad5e891f1e04
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_ia64.deb
>       Size/MD5 checksum:   182796 c0392a8c7865cb50d04be0e94652950e
>
>   HP Precision architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
hppa.deb
>       Size/MD5 checksum:  1881442 563a1aa0dd580b6ad3c6c0a2349dca4a
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_hppa.deb
>       Size/MD5 checksum:    70642 5621e5d9b87d09518989007f56226829
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_hppa.deb
>       Size/MD5 checksum:    89672 3b0e46f09ddf5729ecf1ff2ffd96e330
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_hppa.deb
>       Size/MD5 checksum:  2455902 b2cec64fb76c5897e80ae5f1dcac544e
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_hppa.deb
>       Size/MD5 checksum:   126408 1e2d78fb9ea9ccf33c8795e299c80472
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_hppa.deb
>       Size/MD5 checksum:   159394 4f3b418889cca6c58a6f43e45f4a850b
>
>   Motorola 680x0 architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
m68k.deb
>       Size/MD5 checksum:  1754764 f87db50992018fe8b5de25211b574426
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_m68k.deb
>       Size/MD5 checksum:    66118 296777959e50722e6b9f9d6faa4cfc1b
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_m68k.deb
>       Size/MD5 checksum:    81236 32a5503de356745eec4e1c635038fceb
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_m68k.deb
>       Size/MD5 checksum:  2261258 c019c2ae5fcbd0971f3d2cda8d9e3847
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_m68k.deb
>       Size/MD5 checksum:   106082 4a9d724f386e377d1fd85fa99889f59a
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_m68k.deb
>       Size/MD5 checksum:   128650 667a278f8fcb605687c98b23b3f3aafe
>
>   Big endian MIPS architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
mips.deb
>       Size/MD5 checksum:  1811334 a4c2911a2e87d42a1dbc9184ef9c0816
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_mips.deb
>       Size/MD5 checksum:    67744 413e2cd4d055e0b4c75328cb31ba7fac
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_mips.deb
>       Size/MD5 checksum:    81192 33d5eea8d3c413e7a99e1124de8fc45a
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_mips.deb
>       Size/MD5 checksum:  2404494 015fa93177953806525c84386a2d08c8
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_mips.deb
>       Size/MD5 checksum:   112614 74ee1d6ea3fb489e6a9934000ff458cd
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_mips.deb
>       Size/MD5 checksum:   151050 93d3f6cf6aa5dff4864020f919628e21
>
>   Little endian MIPS architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
mipsel.deb
>       Size/MD5 checksum:  1811896 beefa067ccaea12fa4d68d5678960c3d
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_mipsel.deb
>       Size/MD5 checksum:    67718 e557c54204935027615e54070022d266
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_mipsel.deb
>       Size/MD5 checksum:    81200 9261e171865e9b90abe5e3c32b7985c6
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_mipsel.deb
>       Size/MD5 checksum:  2406850 8c076e85e74f2bb724e8861caf5cbd1a
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_mipsel.deb
>       Size/MD5 checksum:   112422 899ee72e7435f36443cf2682fd1eedfc
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_mipsel.deb
>       Size/MD5 checksum:   150868 3ac0b70dd963fd9d691778f3db475e78
>
>   PowerPC architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
powerpc.deb
>       Size/MD5 checksum:  1800310 e91d519ebb667d0fc014197c9fc50bbf
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_powerpc.deb
>       Size/MD5 checksum:    67750 f612f520350723784e7e412b5c5c6d76
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_powerpc.deb
>       Size/MD5 checksum:    83326 3d6ac0b7cac6a22b7a8ab35d3284d426
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_powerpc.deb
>       Size/MD5 checksum:  2359640 b68c2880e24184dd822858ff0f8c2c6c
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_powerpc.deb
>       Size/MD5 checksum:   116626 965df8a04738453a1be6dcadfb185425
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_powerpc.deb
>       Size/MD5 checksum:   145072 1f5234bbf22e3d4e87ab83e05c293aee
>
>   IBM S/390 architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
s390.deb
>       Size/MD5 checksum:  1795398 5fb02f410f015da208095d47dd544225
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_s390.deb
>       Size/MD5 checksum:    69130 5c18941172e2a104778aa738e77af8e4
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_s390.deb
>       Size/MD5 checksum:    85850 3426a67e51a4681b509b8c2fb960b36d
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_s390.deb
>       Size/MD5 checksum:  2337448 6e27c255720ee9be9a463155a44a30ab
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_s390.deb
>       Size/MD5 checksum:   115168 ceb391d9471abff5410adfde83d063c7
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_s390.deb
>       Size/MD5 checksum:   140690 0123cc8d43645684800913c441572d9a
>
>   Sun Sparc architecture:
>
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys_1.1.14-5woody7_
sparc.deb
>       Size/MD5 checksum:  1845052 2cea12827ac192d5e53aabf6f9d15c0c
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-bsd_1.1.14-5woo
dy7_sparc.deb
>       Size/MD5 checksum:    70706 4585deca2f2105f00f89fe2a90dc81b5
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-client_1.1.14-5
woody7_sparc.deb
>       Size/MD5 checksum:    84132 f81ebff2f338f9c0a847cbc75e465aa6
>
http://security.debian.org/pool/updates/main/c/cupsys/cupsys-pstoraster_1.1.
14-5woody7_sparc.deb
>       Size/MD5 checksum:  2354524 a171535afe6b378f471d2b7098538698
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2_1.1.14-5woo
dy7_sparc.deb
>       Size/MD5 checksum:   120310 9bd1fd569c5727431647a1649e89d2f7
>
http://security.debian.org/pool/updates/main/c/cupsys/libcupsys2-dev_1.1.14-
5woody7_sparc.deb
>       Size/MD5 checksum:   146600 6e5b4f99e8f1e6d2fe09d6037f2d16e1
>
>
>   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: [EMAIL PROTECTED]
> Package info: `apt-cache show <pkg>' and http://packages.debian.org/<pkg>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
>
> iD8DBQFBbprdW5ql+IAeqTIRAs2XAKCaRQ490/C8iFKprrBBK8CsbnjVEQCaApFb
> HfNhjsxtZ0wRnppgq06sO7w=
> =gN6K
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>
> ------------------------------
>
> End of this Digest
> ******************
>
> --
> Raj Mathur                [EMAIL PROTECTED]      http://kandalaya.org/
>        GPG: 78D4 FC67 367F 40E2 0DD5  0FEF C968 D0EF CC68 D17F
>                       It is the mind that moves
>
>
>
> ------------------------------
>
> _______________________________________________
> ilugd mailing list
> [EMAIL PROTECTED]
> http://frodo.hserus.net/mailman/listinfo/ilugd
>
>
> End of ilugd Digest, Vol 19, Issue 21
> *************************************


_______________________________________________
ilugd mailinglist -- [EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[EMAIL PROTECTED]/

Reply via email to