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

2018-12-21 Thread Enji Cooper
> 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 or Fusion is this occurring on? I saw >> Workstation 14 mentioned

Re: ctm(1) deprecation in the FreeBSD base system?

2018-12-21 Thread Julian H. Stacey
> The port Makefile that I have prepared is attached below for reference. > Regards, STefan Thanks Stefan, I took current /usr/ports/misc/ctm/ & converted Stephen's & my diffs to be automatic ports patches: http://berklix.com/~jhs/src/bsd/fixes/freebsd/ports/gen/misc/ctm/files/

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

2018-12-21 Thread Mark Millard
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 thing I ran into has hung-up every time, the same way, for amd64->armv7 cross builds: multimedia/gstreamer1-qt@qt5 . So I extract the material here

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

2018-12-21 Thread Yuri Pankov
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 or Fusion is this occurring on? I saw > Workstation 14 mentioned but curious if it occurs on Workstation 15 > (latest). Running the

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

2018-12-21 Thread Mark Peek
Thanks for the cc:. I forwarded the original report on to an internal VMware desktop product contact. What version of Workstation or Fusion is this occurring on? I saw Workstation 14 mentioned but curious if it occurs on Workstation 15 (latest). Mark On Fri, Dec 21, 2018 at 4:19 PM Warner Losh

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

2018-12-21 Thread Warner Losh
I've been hit by this as well. At least two others on IRC have had the same issue. Warner On Fri, Dec 21, 2018 at 5:10 PM Enji Cooper wrote: > > > On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: > > > > Hi, > > > > There's apparently a bug in VMware Workstation NAT implementation, made > >

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

2018-12-21 Thread Enji Cooper
> On Dec 21, 2018, at 3:55 PM, Yuri Pankov wrote: > > Hi, > > There's apparently a bug in VMware Workstation NAT implementation, made > visible by the change to default values of IPQoS in OpenSSH 7.8p1, > making all ssh connections from the guest behind the NAT to fail with > obscure

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

2018-12-21 Thread Yuri Pankov
Hi, There's apparently a bug in VMware Workstation NAT implementation, made visible by the change to default values of IPQoS in OpenSSH 7.8p1, making all ssh connections from the guest behind the NAT to fail with obscure "Fssh_packet_write_wait: Connection to 192.168.1.53 port 22: Broken pipe".

Re: AESNI, /dev/crypto, and new OpenSSL

2018-12-21 Thread Alexey Dokuchaev
On Fri, Dec 21, 2018 at 01:10:07AM +0700, Alexey Dokuchaev wrote: > On Thu, Dec 20, 2018 at 09:33:41AM -0800, Freddie Cash wrote: > > On Thu, Dec 20, 2018 at 9:21 AM Alexey Dokuchaev wrote: > > > Had something got broken here, or I'm misunderstanding how this machinery > > > now works? > > > >