public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin64 OpenSSH_8.1p1 client segmentation fault
Date: Mon, 16 Dec 2019 20:06:00 -0000	[thread overview]
Message-ID: <6e6c6af3-1ac1-eb15-f2a0-42b657c751c9@SystematicSw.ab.ca> (raw)
In-Reply-To: <ef758903-d331-caae-fcf8-532d44893c05@cornell.edu>

On 2019-12-15 09:24, Ken Brown wrote:
> On 12/15/2019 7:22 AM, vadim wrote:
>> On 14/12/2019 20:20, Ken Brown wrote:
>>> On 12/14/2019 3:01 PM, vadim wrote:
>> I have now installed cygwin64 from 
>> http://ctm.crouchingtigerhiddenfruitbat.org/pub/cygwin/circa/64bit/2019/08/30/171738 
>> ssh now works fine. The version is
>> OpenSSH_7.0p1, OpenSSL 1.0.2t 10 Sep 2019
>> I see a change in both SSH and SSL versions here
>> Not working ssh version under cygwin64 was:
>> OpenSSH_8.1p1, OpenSSL 1.1.1d 10 Sep 2019
>> I was also trying to use the latest cygwin32 version that seemed to be working, 
>> but I noticed that git was behaving very odd - it didn't finish pull command 
>> quite often. I noticed git has dependency on the same openSSL 1.1 package, so I 
>> suspect there is an issue in that openSSL 1.1 package that is used in both ssh 
>> and git.

Just because those versions work doesn't mean that future versions won't have
BLODA problems, which as the BLODA licensee, is your problem to follow up with
your internal IT or vendor support.

> Since other people aren't reporting these problems, I still suspect BLODA.  The 
> following DLLs in your strace output look suspicious to me:
> 
> C:\PROGRA~1\Citrix\System32\MfApHook64.dll
> C:\Program Files\Avecto\Privilege Guard Client\PGHook.dll
> C:\Program Files\Citrix\ICAService\PicaWtsHook64.dll
> C:\Program Files\Citrix\ICAService\SCardHook64.dll
> C:\Program Files\Citrix\ICAService\ShellHook64.dll
> C:\Program Files\Citrix\ICAService\cxinjime64.dll
> C:\Program Files\Citrix\ICAService\picaFullScreenHookX64.dll
> C:\Windows\System32\VSMAPIMon.dll
> C:\Windows\System32\lsihok64.dll
> 
> I suggest you investigate the applications that installed these DLLs to see if 
> one of them might be interfering with Cygwin.

Beyond Trust/Avecto Privilege Guard blocks elevation and possibly other rights:
suggest adding to BLODA list; also possible are Lakeside Systems Systems
Management Agent web tracking logging software and MicroFocus/Voltage Security
Voltage Encryption network encryption which duplicates ssh functions; Citrix ICA
(like RDP) could be a possibility.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2019-12-16 19:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAL4T9x+gCedhmLbr0mX+acSjDoiMVj7c0B7yuDf3znnDeR-5wQ@mail.gmail.com>
2019-12-14 16:13 ` vadim
2019-12-14 16:17   ` vadim
2019-12-14 17:21     ` Eliot Moss
2019-12-14 18:24       ` Ken Brown
2019-12-14 19:01     ` Marco Atzeri
2019-12-14 20:20     ` vadim
2019-12-15 12:22       ` Ken Brown
2019-12-15 13:14         ` vadim
2019-12-15 17:00           ` Ken Brown
2019-12-16 20:06             ` Brian Inglis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6e6c6af3-1ac1-eb15-f2a0-42b657c751c9@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).