Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Enji Cooper
> On Dec 22, 2018, at 1:03 PM, Cy Schubert wrote: … > Regarding the Red Hat bugzilla bug, looks like they're doing the right > thing by reaching out to VMware. This should be our position as well. > Add it to ssh_config or sshd_config if one must but have VMware fix > their bugs. Putting

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Cy Schubert
In message <0503b382-d886-39a4-d265-b43d8adc1...@yuripv.net>, Yuri Pankov write s: > This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --e7sW91Qf9WxzTaujtGEdAimN5k2EtpJ6Q > Content-Type: multipart/mixed; boundary="3a9zlXDI7Z2P48EdQkgwMdVOMQOEfR5Wm"; > protected-headers="v1" > From:

Re: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved)

2018-12-22 Thread Mark Millard
[I found my E-mail records reporting successful builds using qemu-user-static from ports head -r484783 under FreeBSD head -r340287.] On 2018-Dec-22, at 00:10, Mark Millard wrote: > [I messed up the freebsd-emulation email address the first time I sent > this. I also forgot to indicate the

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Yuri Pankov
Cy Schubert wrote: > In message , Yuri > Pankov write > s: >> This is an OpenPGP/MIME signed message (RFC 4880 and 3156) >> --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH >> Content-Type: multipart/mixed; boundary="c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi"; >> protected-headers="v1" >> From: Yuri Pankov >> To:

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Cy Schubert
In message , Yuri Pankov write s: > This is an OpenPGP/MIME signed message (RFC 4880 and 3156) > --NAG3HGfiwhsHyGq3aNdsIv1NzTEMODbUH > Content-Type: multipart/mixed; boundary="c7yUHUJpZYpJqOrOWLAb4sE3Rmh2alrdi"; > protected-headers="v1" > From: Yuri Pankov > To: Cy Schubert > Cc: Mark Peek ,

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Yuri Pankov
Cy Schubert wrote: > In message <913730b6-c6f0-60b8-a589-e89e872b7...@yuripv.net>, Yuri > Pankov write > s: >> Yuri Pankov wrote: >>> In-Reply-To: l.gmail. >>> com> >>> Mark Peek wrote: On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > wro= >>> te: =20 > >> On Dec 21, 2018, at

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Cy Schubert
In message <913730b6-c6f0-60b8-a589-e89e872b7...@yuripv.net>, Yuri Pankov write s: > Yuri Pankov wrote: >> In-Reply-To: > com> >> Mark Peek wrote: >> > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wro= >> te: >> >=20 >> >> >> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >> >>> >> >>> Mark

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Warner Losh
On Sat, Dec 22, 2018, 11:03 AM Yuri Pankov Mark Peek wrote: > > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper > wrote: > > > >> > >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > >>> > >>> Mark Peek wrote: > Thanks for the cc:. I forwarded the original report on to an internal >

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Yuri Pankov
Mark Peek wrote: > On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote: > >> >>> On Dec 21, 2018, at 17:48, Yuri Pankov wrote: >>> >>> Mark Peek wrote: Thanks for the cc:. I forwarded the original report on to an internal VMware desktop product contact. >>> >>> Thank you. >>> What

Re: workaround for VMware WS NAT bug triggered by OpenSSH 7.8p1 changes

2018-12-22 Thread Mark Peek
On Fri, Dec 21, 2018 at 9:30 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 17:48, Yuri Pankov wrote: > > > > Mark Peek wrote: > >> Thanks for the cc:. I forwarded the original report on to an internal > >> VMware desktop product contact. > > > > Thank you. > > > >> What version of Workstation

Re: A reliable port cross-build failure (hangup) in my context (amd64->armv7 cross build, with native-tool speedup involved)

2018-12-22 Thread Mark Millard
[I messed up the freebsd-emulation email address the first time I sent this. I also forgot to indicate the qemu-user-static vintage relationship.] I had been reporting intermittent hang-ups for my amd64->{aarch64,armv7} port cross builds in another message sequence. But it turns out that one