From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id 3576AE00CBD; Wed, 6 Sep 2017 14:57:33 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [64.235.150.235 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0045] * 0.0 HTML_MESSAGE BODY: HTML included in message X-Greylist: delayed 906 seconds by postgrey-1.32 at yocto-www; Wed, 06 Sep 2017 14:57:31 PDT Received: from 14pmail.ess.barracuda.com (14pmail.ess.barracuda.com [64.235.150.235]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id ADD86E00CB4 for ; Wed, 6 Sep 2017 14:57:31 -0700 (PDT) Received: from SFAMAIL.SAKURAUS.LOCAL (mail.sakuraus.com [12.26.104.5]) by mx3.ess.sfj.cudaops.com (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=NO); Wed, 06 Sep 2017 21:57:29 +0000 Received: from SFAMAIL.SAKURAUS.LOCAL (10.16.3.8) by SFAMAIL.SAKURAUS.LOCAL (10.16.3.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.669.32; Wed, 6 Sep 2017 14:42:18 -0700 Received: from SFAMAIL.SAKURAUS.LOCAL ([::1]) by SFAMAIL.SAKURAUS.LOCAL ([::1]) with mapi id 15.01.0669.032; Wed, 6 Sep 2017 14:42:18 -0700 From: Greg Wilson-Lindberg To: "yocto@yoctoproject.org" Thread-Topic: Working behind a Palo Alto firewall/proxy Thread-Index: AdMnV80YgGzHXD1LRPmTpkR9+dAmmw== Date: Wed, 6 Sep 2017 21:42:18 +0000 Message-ID: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.16.5.3] MIME-Version: 1.0 X-BESS-ID: 1504735048-298554-12554-171595-1 X-BESS-VER: 2017.10-r1707252126 X-BESS-Apparent-Source-IP: 12.26.104.5 X-BESS-Outbound-Spam-Score: 0.00 X-BESS-Outbound-Spam-Report: Code version 3.2, rules version 3.2.2.184751 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------- 0.00 BSF_BESS_OUTBOUND META: BESS Outbound 0.00 HTML_MESSAGE BODY: HTML included in message X-BESS-Outbound-Spam-Status: SCORE=0.00 using account:ESS29408 scores of KILL_LEVEL=7.0 tests=BSF_BESS_OUTBOUND, HTML_MESSAGE X-BESS-BRTS-Status: 1 Subject: Working behind a Palo Alto firewall/proxy X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Sep 2017 21:57:33 -0000 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_afce79fad80649ff88295ca3d41499efsakurauscom_" --_000_afce79fad80649ff88295ca3d41499efsakurauscom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi List, Does anybody have any experience trying to run Yocto behind a Palo Alto fir= ewall. The Palo Alto firewall basically works as a Man in the Middle system= , it hands out its own certificate to boxes behind it and then decrypts and= re-encrypts traffic going through it. The Palo Alto box is supposed to act= as a transparent Proxy. I'm getting an error that the 'server certificate verification failed' abou= t an hour into a yocto build. The certificate that the Palo Alto box is sen= ding to my system is self-signed so will fail if checked for a valid root C= A, and also is not from whatever site is being downloaded from. Any suggestions would be appreciated. Greg Wilson-Lindberg Sakura Finetek 310-783-5075 --_000_afce79fad80649ff88295ca3d41499efsakurauscom_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi List,

Does anybody have any experience trying to run Yocto= behind a Palo Alto firewall. The Palo Alto firewall basically works as a M= an in the Middle system, it hands out its own certificate to boxes behind i= t and then decrypts and re-encrypts traffic going through it. The Palo Alto box is supposed to act as a transp= arent Proxy.

 

I'm getting an error that the 'server certificate ve= rification failed' about an hour into a yocto build. The certificate that t= he Palo Alto box is sending to my system is self-signed so will fail if che= cked for a valid root CA, and also is not from whatever site is being downloaded from.

 

Any suggestions would be appreciated.

 

Greg Wilson-Lindberg

Sakura Finetek

310-783-5075

--_000_afce79fad80649ff88295ca3d41499efsakurauscom_--