MESSAGE
DATE | 2024-02-18 |
FROM | Mithun Bhattacharya
|
SUBJECT | Re: [Hangout - NYLXS] HTTPd Devs Considered Harmful to
|
From hangout-bounces-at-nylxs.com Sun Feb 18 23:47:01 2024 Return-Path: X-Original-To: archive-at-mrbrklyn.com Delivered-To: archive-at-mrbrklyn.com Received: from www2.mrbrklyn.com (www2.mrbrklyn.com [96.57.23.82]) by mrbrklyn.com (Postfix) with ESMTP id 9FBCB1640BD; Sun, 18 Feb 2024 23:46:59 -0500 (EST) X-Original-To: hangout-at-www2.mrbrklyn.com Delivered-To: hangout-at-www2.mrbrklyn.com Received: by mrbrklyn.com (Postfix, from userid 1000) id B8E091640B5; Sun, 18 Feb 2024 23:45:58 -0500 (EST) Resent-From: Ruben Safir Resent-Date: Sun, 18 Feb 2024 23:45:58 -0500 Resent-Message-ID: <20240219044558.GG20445-at-www2.mrbrklyn.com> Resent-To: hangout-at-mrbrklyn.com X-Original-To: ruben-at-mrbrklyn.com Delivered-To: ruben-at-mrbrklyn.com Received: from mxout1-ec2-va.apache.org (mxout1-ec2-va.apache.org [3.227.148.255]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.apache.org", Issuer "Sectigo RSA Domain Validation Secure Server CA" (not verified)) by mrbrklyn.com (Postfix) with ESMTPS id 78ECA1640A3 for ; Sun, 18 Feb 2024 14:12:05 -0500 (EST) Received: from mail.apache.org (mailgw-he-de.apache.org [116.203.246.181]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mxout1-ec2-va.apache.org (ASF Mail Server at mxout1-ec2-va.apache.org) with ESMTPS id D91704561D for ; Sun, 18 Feb 2024 19:12:04 +0000 (UTC) Received: (qmail 1291238 invoked by uid 998); 18 Feb 2024 19:11:59 -0000 Mailing-List: contact modperl-help-at-perl.apache.org; run by ezmlm Precedence: bulk Delivered-To: mailing list modperl-at-perl.apache.org Received: (qmail 1291225 invoked by uid 116); 18 Feb 2024 19:11:58 -0000 Received: from spamproc1-he-de.apache.org (HELO spamproc1-he-de.apache.org) (116.203.196.100) by apache.org (qpsmtpd/0.94) with ESMTP; Sun, 18 Feb 2024 19:11:58 +0000 Authentication-Results: apache.org; auth=none Received: from localhost (localhost [127.0.0.1]) by spamproc1-he-de.apache.org (ASF Mail Server at spamproc1-he-de.apache.org) with ESMTP id C0B351FFCB2 for ; Sun, 18 Feb 2024 19:11:58 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamproc1-he-de.apache.org X-Spam-Flag: NO X-Spam-Score: -5 X-Spam-Level: X-Spam-Status: No, score=-5 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.2, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamproc1-he-de.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-he-de.apache.org ([116.203.227.195]) by localhost (spamproc1-he-de.apache.org [116.203.196.100]) (amavisd-new, port 10024) with ESMTP id 0NfJzn6PCaLd for ; Sun, 18 Feb 2024 19:11:58 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=2607:f8b0:4864:20::931; helo=mail-ua1-x931.google.com; envelope-from=mithnb-at-gmail.com; receiver= Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) by mx1-he-de.apache.org (ASF Mail Server at mx1-he-de.apache.org) with ESMTPS id 079527E61A for ; Sun, 18 Feb 2024 19:11:57 +0000 (UTC) Received: by mail-ua1-x931.google.com with SMTP id a1e0cc1a2514c-7d2e19120b5so1982504241.2 for ; Sun, 18 Feb 2024 11:11:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708283516; x=1708888316; darn=perl.apache.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=/5x6Un/Ux80pZFLFktkvktydoyh+869ymgIbsV/ZAtA=; b=FKiDwhiTDPLJr0GBE933o1KsLVw7XeksIk4r5ObuEK/oVsj8Ko+/gwpez9qvISK0F3 0W16C2qbj1fJZ28uXhlz4QI0fzXrZkLu9URRFKnMmLWM1+rnRFvDrYb2KtrotbqjYMvI +3PlR8NnTwpQ3peZmeaZr4NJGAEy6rkexCzZPcEon/zA8vcaBK7aouL/5nGX26IYbSEx WlASw9P/2EHNxesd1UxkdaV88xiukwAmfi6okfq/dS90BWWq+na5VxP9f9Zeok6mgPUf RcSWUUF26s6jG/AC6BbDlln+TOsSfiLXEaSPPCaYtCLuJ/MoHIs3k/fiIZrTd0h3/b+F 6wLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708283516; x=1708888316; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=/5x6Un/Ux80pZFLFktkvktydoyh+869ymgIbsV/ZAtA=; b=Wa+8ygkq1g9v97p5OCR6t4XfI0aak5Vp6Dz5g7gzjriwlXHpjKVyzCLNG8OecfgNUt zITqfPwSf1NoGO/y4u1h5Ua42G5Wu0uB3s/tLkJcfBR6yq56++w2GNbR3zbSN+AjyTN0 zUVKKIsPaRCau3hjPmndgilbMCzXFS8ZRTZUOc5mHonOIN1oLGPBzaDQhp3xkazmKY8q KazWjG0WERjFx/9xInosn8O6DE/f6Y3wwhHWYxQv5c4XjTuuXbhXkMMG55YnyNw4pxbt /Da/Je2SYjO/H7I1lrlzWigPV/4fQzIlpzslp/zf+VtpEg4VxBT2COYgPfgxw5U1jHPJ qsdQ== X-Gm-Message-State: AOJu0Yxku9yveDK0hNbcatqRerIUOUlo0oYMkDK133Mn2m0eUD6uUUlm zqixhp5fezb2fToGyrcCMRXLYCTHVnpVcUit3kOf/FUT+dyC2Atf+p9qfSrevHLGlYaEfJc5RvA 16wdlZkqcN7jRAzIwfgdiAZ4brPhszGFC X-Google-Smtp-Source: AGHT+IEQxh48vKiq//iiBaKQ3Ih+mNOfu/WBF7TgfwyiBlQeU8LR3KIKQpIL2I27UKe3xPFcuEup+S4OvRsKHoO4ILQ= X-Received: by 2002:a05:6102:12c7:b0:470:390d:41d8 with SMTP id jd7-20020a05610212c700b00470390d41d8mr3913164vsb.27.1708283516479; Sun, 18 Feb 2024 11:11:56 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Mithun Bhattacharya Date: Sun, 18 Feb 2024 13:11:44 -0600 Message-ID: To: mod_perl list Subject: Re: [Hangout - NYLXS] HTTPd Devs Considered Harmful to Apache2::Request users X-BeenThere: hangout-at-nylxs.com X-Mailman-Version: 2.1.30rc1 List-Id: NYLXS Tech Talk and Politics List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1719543133==" Errors-To: hangout-bounces-at-nylxs.com Sender: "Hangout"
--===============1719543133== Content-Type: multipart/alternative; boundary="0000000000002cf3c90611acc093"
--0000000000002cf3c90611acc093 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Also thank you for the library !
On Sun, Feb 18, 2024, 1:11=E2=80=AFPM Mithun Bhattacharya > wrote:
> So is there a cleaner/saner version of libapreq2 or is the 2012 version > better ? > > On Sun, Feb 18, 2024, 12:58=E2=80=AFPM Joe Schaefer = wrote: > >> For the past 25 years, I have been the lead developer of the libapreq2 >> subproject within the Apache HTTPd Server Parent Project. The original i= dea >> of libapreq as a safe/performant HTML form and Cookie parsing library ca= me >> out of a collaboration between Lincoln Stein and Doug MacEachern in the >> late 90s. >> >> It was my vision back then to transform the library into a generic, >> non-Perl related C library that would support language bindings from oth= er >> programming languages, which is why I pushed for the project to be homes >> under the HTTPd umbrella instead of the Apache-Perl project. >> >> While this vision was wildly successful, with language bindings availabl= e >> for several languages like Perl, TCL, R, etc, ever since about 2010 its >> proven tragic for the existing user community consisting of all of them, >> not just Perl. >> >> What happened? Philip Gollucci, a Perl/FreeBSD olleague of mine at the >> time, started agitating that we promote the project to be released from >> inside the HTTPd server itself. What Philip didn=E2=80=99t know very wel= l back then >> was how utterly vapid and territorial that team had become, which would >> have meant having to collaborate with them directly on user-facing >> decisions about the code base. >> >> In 2012, Philip got what he wanted and I stopped resisting, so he forked >> the existing project and copied the C library components into HTTPd core= . >> >> In 2016 I resigned from the Foundation en masse. You can guess the >> reasons. >> >> In 2020 or so, Google=E2=80=99s Security Team took advantage of an alpha= release >> of httpd 2.5 by fuzzing its 8 year old copy of apreq. It found a few >> hotspots that needed repair. >> >> Instead of having the courtesy of reaching out to me, or anyone else >> involved in development of apreq, a junior engineer on the HTTPd team we= nt >> about the business of =E2=80=9Cbug fixing=E2=80=9D the vulnerabilities G= oogle found. You >> can see a record of his trial and error work in every release since then= . >> >> But the coup de grace was the 2022 release of 2.17, wherein the rookie >> developer purposely introduced a fatal bug into the codebase, breaking a >> fifteen year old regression test. >> >> If you are wondering how something with a broken regression test winds u= p >> on CPAN, you=E2=80=99ll have to look into how RELENG is done in the serv= er project. >> >> Long story short, they commented out the test and shipped it anyway, and >> called it a Security Release that fixed a vulnerability every prior rele= ase >> was susceptible to. >> >> Why do I care now? Because I=E2=80=99m the sucker users reach out to for= answers >> as a known subject matter expert. >> >> This sucks, but I=E2=80=99m sorry to tell you that my days wearing the S= uperman >> cape at Apache ended 8 years ago. >> >> -- >> Joe Schaefer, Ph.D. >> >> Orion - The Enterprise Jamstack Wiki >> >> >> 954.253.3732 >> >> >>
--0000000000002cf3c90611acc093 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Also thank you for the library !
mail_quote"> yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">dir=3D"auto">So is there a cleaner/saner version of libapreq2 or is the 201= 2 version better ?
ss=3D"gmail_attr">On Sun, Feb 18, 2024, 12:58=E2=80=AFPM Joe Schaefer <<= a href=3D"mailto:joe-at-sunstarsys.com" target=3D"_blank" rel=3D"noreferrer">j= oe-at-sunstarsys.com> wrote:
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">iv dir=3D"ltr">neva,sans-serif;font-size:13.3333px;background-color:rgb(246,246,239)">For = the past 25 years, I have been the lead developer of the libapreq2 subproje= ct within the Apache HTTPd Server Parent Project. The original idea of liba= preq as a safe/performant HTML form and Cookie parsing library came out of = a collaboration between Lincoln Stein and Doug MacEachern in the late 90s.<= /span>rif;font-size:13.3333px;background-color:rgb(246,246,239)">It was my vision= back then to transform the library into a generic, non-Perl related C libr= ary that would support language bindings from other programming languages, = which is why I pushed for the project to be homes under the HTTPd umbrella = instead of the Apache-Perl project. ont-family:Verdana,Geneva,sans-serif;font-size:13.3333px;background-color:r= gb(246,246,239)">While this vision was wildly successful, with language bin= dings available for several languages like Perl, TCL, R, etc, ever since ab= out 2010 its proven tragic for the existing user community consisting of al= l of them, not just Perl. :Verdana,Geneva,sans-serif;font-size:13.3333px;background-color:rgb(246,246= ,239)">What happened? Philip Gollucci, a Perl/FreeBSD olleague of mine at t= he time, started agitating that we promote the project to be released from = inside the HTTPd server itself. What Philip didn=E2=80=99t know very well b= ack then was how utterly vapid and territorial that team had become, which = would have meant having to collaborate with them directly on user-facing de= cisions about the code base. ily:Verdana,Geneva,sans-serif;font-size:13.3333px;background-color:rgb(246,= 246,239)">In 2012, Philip got what he wanted and I stopped resisting, so he= forked the existing project and copied the C library components into HTTPd= core. s-serif;font-size:13.3333px;background-color:rgb(246,246,239)">In 2016 I re= signed from the Foundation en masse. You can guess the reasons. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">In 2020 or so, Google=E2=80=99= s Security Team took advantage of an alpha release of httpd 2.5 by fuzzing = its 8 year old copy of apreq. It found a few hotspots that needed repair.p> font-size:13.3333px;background-color:rgb(246,246,239)">Instead of having th= e courtesy of reaching out to me, or anyone else involved in development of= apreq, a junior engineer on the HTTPd team went about the business of =E2= =80=9Cbug fixing=E2=80=9D the vulnerabilities Google found. You can see a r= ecord of his trial and error work in every release since then. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">But the coup de grace was the = 2022 release of 2.17, wherein the rookie developer purposely introduced a f= atal bug into the codebase, breaking a fifteen year old regression test.> ont-size:13.3333px;background-color:rgb(246,246,239)">If you are wondering = how something with a broken regression test winds up on CPAN, you=E2=80=99l= l have to look into how RELENG is done in the server project. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">Long story short, they comment= ed out the test and shipped it anyway, and called it a Security Release tha= t fixed a vulnerability every prior release was susceptible to. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">Why do I care now? Because I= =E2=80=99m the sucker users reach out to for answers as a known subject mat= ter expert. a,sans-serif;font-size:13.3333px;background-color:rgb(246,246,239)">This su= cks, but I=E2=80=99m sorry to tell you that my days wearing the Superman ca= pe at Apache ended 8 years ago.
ature_prefix">--
-smartmail=3D"gmail_signature">
--0000000000002cf3c90611acc093--
--===============1719543133== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
_______________________________________________ Hangout mailing list Hangout-at-nylxs.com http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============1719543133==--
--===============1719543133== Content-Type: multipart/alternative; boundary="0000000000002cf3c90611acc093"
--0000000000002cf3c90611acc093 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Also thank you for the library !
On Sun, Feb 18, 2024, 1:11=E2=80=AFPM Mithun Bhattacharya > wrote:
> So is there a cleaner/saner version of libapreq2 or is the 2012 version > better ? > > On Sun, Feb 18, 2024, 12:58=E2=80=AFPM Joe Schaefer = wrote: > >> For the past 25 years, I have been the lead developer of the libapreq2 >> subproject within the Apache HTTPd Server Parent Project. The original i= dea >> of libapreq as a safe/performant HTML form and Cookie parsing library ca= me >> out of a collaboration between Lincoln Stein and Doug MacEachern in the >> late 90s. >> >> It was my vision back then to transform the library into a generic, >> non-Perl related C library that would support language bindings from oth= er >> programming languages, which is why I pushed for the project to be homes >> under the HTTPd umbrella instead of the Apache-Perl project. >> >> While this vision was wildly successful, with language bindings availabl= e >> for several languages like Perl, TCL, R, etc, ever since about 2010 its >> proven tragic for the existing user community consisting of all of them, >> not just Perl. >> >> What happened? Philip Gollucci, a Perl/FreeBSD olleague of mine at the >> time, started agitating that we promote the project to be released from >> inside the HTTPd server itself. What Philip didn=E2=80=99t know very wel= l back then >> was how utterly vapid and territorial that team had become, which would >> have meant having to collaborate with them directly on user-facing >> decisions about the code base. >> >> In 2012, Philip got what he wanted and I stopped resisting, so he forked >> the existing project and copied the C library components into HTTPd core= . >> >> In 2016 I resigned from the Foundation en masse. You can guess the >> reasons. >> >> In 2020 or so, Google=E2=80=99s Security Team took advantage of an alpha= release >> of httpd 2.5 by fuzzing its 8 year old copy of apreq. It found a few >> hotspots that needed repair. >> >> Instead of having the courtesy of reaching out to me, or anyone else >> involved in development of apreq, a junior engineer on the HTTPd team we= nt >> about the business of =E2=80=9Cbug fixing=E2=80=9D the vulnerabilities G= oogle found. You >> can see a record of his trial and error work in every release since then= . >> >> But the coup de grace was the 2022 release of 2.17, wherein the rookie >> developer purposely introduced a fatal bug into the codebase, breaking a >> fifteen year old regression test. >> >> If you are wondering how something with a broken regression test winds u= p >> on CPAN, you=E2=80=99ll have to look into how RELENG is done in the serv= er project. >> >> Long story short, they commented out the test and shipped it anyway, and >> called it a Security Release that fixed a vulnerability every prior rele= ase >> was susceptible to. >> >> Why do I care now? Because I=E2=80=99m the sucker users reach out to for= answers >> as a known subject matter expert. >> >> This sucks, but I=E2=80=99m sorry to tell you that my days wearing the S= uperman >> cape at Apache ended 8 years ago. >> >> -- >> Joe Schaefer, Ph.D. >> >> Orion - The Enterprise Jamstack Wiki >> >> >> 954.253.3732 >> >> >>
--0000000000002cf3c90611acc093 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Also thank you for the library !
mail_quote"> yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">dir=3D"auto">So is there a cleaner/saner version of libapreq2 or is the 201= 2 version better ?
ss=3D"gmail_attr">On Sun, Feb 18, 2024, 12:58=E2=80=AFPM Joe Schaefer <<= a href=3D"mailto:joe-at-sunstarsys.com" target=3D"_blank" rel=3D"noreferrer">j= oe-at-sunstarsys.com> wrote:
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">iv dir=3D"ltr">neva,sans-serif;font-size:13.3333px;background-color:rgb(246,246,239)">For = the past 25 years, I have been the lead developer of the libapreq2 subproje= ct within the Apache HTTPd Server Parent Project. The original idea of liba= preq as a safe/performant HTML form and Cookie parsing library came out of = a collaboration between Lincoln Stein and Doug MacEachern in the late 90s.<= /span>rif;font-size:13.3333px;background-color:rgb(246,246,239)">It was my vision= back then to transform the library into a generic, non-Perl related C libr= ary that would support language bindings from other programming languages, = which is why I pushed for the project to be homes under the HTTPd umbrella = instead of the Apache-Perl project. ont-family:Verdana,Geneva,sans-serif;font-size:13.3333px;background-color:r= gb(246,246,239)">While this vision was wildly successful, with language bin= dings available for several languages like Perl, TCL, R, etc, ever since ab= out 2010 its proven tragic for the existing user community consisting of al= l of them, not just Perl. :Verdana,Geneva,sans-serif;font-size:13.3333px;background-color:rgb(246,246= ,239)">What happened? Philip Gollucci, a Perl/FreeBSD olleague of mine at t= he time, started agitating that we promote the project to be released from = inside the HTTPd server itself. What Philip didn=E2=80=99t know very well b= ack then was how utterly vapid and territorial that team had become, which = would have meant having to collaborate with them directly on user-facing de= cisions about the code base. ily:Verdana,Geneva,sans-serif;font-size:13.3333px;background-color:rgb(246,= 246,239)">In 2012, Philip got what he wanted and I stopped resisting, so he= forked the existing project and copied the C library components into HTTPd= core. s-serif;font-size:13.3333px;background-color:rgb(246,246,239)">In 2016 I re= signed from the Foundation en masse. You can guess the reasons. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">In 2020 or so, Google=E2=80=99= s Security Team took advantage of an alpha release of httpd 2.5 by fuzzing = its 8 year old copy of apreq. It found a few hotspots that needed repair.p> font-size:13.3333px;background-color:rgb(246,246,239)">Instead of having th= e courtesy of reaching out to me, or anyone else involved in development of= apreq, a junior engineer on the HTTPd team went about the business of =E2= =80=9Cbug fixing=E2=80=9D the vulnerabilities Google found. You can see a r= ecord of his trial and error work in every release since then. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">But the coup de grace was the = 2022 release of 2.17, wherein the rookie developer purposely introduced a f= atal bug into the codebase, breaking a fifteen year old regression test.> ont-size:13.3333px;background-color:rgb(246,246,239)">If you are wondering = how something with a broken regression test winds up on CPAN, you=E2=80=99l= l have to look into how RELENG is done in the server project. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">Long story short, they comment= ed out the test and shipped it anyway, and called it a Security Release tha= t fixed a vulnerability every prior release was susceptible to. =3D"color:rgb(130,130,130);font-family:Verdana,Geneva,sans-serif;font-size:= 13.3333px;background-color:rgb(246,246,239)">Why do I care now? Because I= =E2=80=99m the sucker users reach out to for answers as a known subject mat= ter expert. a,sans-serif;font-size:13.3333px;background-color:rgb(246,246,239)">This su= cks, but I=E2=80=99m sorry to tell you that my days wearing the Superman ca= pe at Apache ended 8 years ago.
ature_prefix">--
-smartmail=3D"gmail_signature">
--0000000000002cf3c90611acc093--
--===============1719543133== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline
_______________________________________________ Hangout mailing list Hangout-at-nylxs.com http://lists.mrbrklyn.com/mailman/listinfo/hangout
--===============1719543133==--
|
|