From: Jeffrey Walton <noloader@gmail.com>
To: cygwin@cygwin.com
Subject: Re: portable use of dos2unix WAS: Re: textmode for stdout, what is "correct" now?
Date: Mon, 18 Feb 2019 13:07:00 -0000 [thread overview]
Message-ID: <CAH8yC8n0zRsMrvLn+HtKhG2tg-ghznK=R7CkD-=FMQouppdQ1w@mail.gmail.com> (raw)
In-Reply-To: <767726ce-4b90-085a-4457-af535980ebbf@ssi-schaefer.com>
On Mon, Feb 18, 2019 at 5:01 AM Michael Haubenwallner
<michael.haubenwallner@ssi-schaefer.com> wrote:
>
> On 2/15/19 10:00 PM, Corinna Vinschen wrote:
> > On Feb 15 20:33, Michael Haubenwallner wrote:
> >> On 2/15/19 7:35 PM, Andrey Repin wrote:
> >>> I have a different question though. The commands you presented in the OP
> >>> look like you aren't using Cygwin-suppied OpenSSL binary.
> >>
> >> This is true: The Cygwin distro does provide openssl-1.0.2p, but I'm building
> >> the *portable* Gentoo Prefix distro on Cygwin, with openssl-1.1.1a already.
> >> But whenever the Cygwin distro would bump to openssl-1.1, the same problem
> >> would arise there as well, just becomes noticed much later probably.
> >
> > Does OpenSSH build with OpenSSL 1.1.1a these days? If so, we might
> > want to switch OpenSSL finally, too.
>
> Well, OpenSSH-7.9_p1 maybe does, according to https://bugs.gentoo.org/592578
I believe OpenSSH sidestepped OpenSSL. That is, it no longer depends
on it in a way that things matter. I don't recall the details.
As far as building OpenSSH against OpenSSL 1.1, see
https://github.com/openssh/openssh-portable/pull/48 .
Also see https://wiki.openssl.org/index.php/OpenSSL_1.1.0_Changes,
which documents some [former] incompatibilities between other programs
and OpenSSL.
Jeff
--
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
next prev parent reply other threads:[~2019-02-18 12:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 16:05 Michael Haubenwallner
2019-02-14 18:51 ` Corinna Vinschen
2019-02-15 9:31 ` Michael Haubenwallner
2019-02-15 10:28 ` Corinna Vinschen
2019-02-15 12:48 ` Michael Haubenwallner
2019-02-15 12:49 ` Corinna Vinschen
2019-02-15 18:25 ` Michael Haubenwallner
2019-02-15 20:35 ` Corinna Vinschen
2019-02-16 9:39 ` Michael Haubenwallner
2019-02-16 9:40 ` Corinna Vinschen
2019-02-16 17:40 ` Michael Haubenwallner
2019-02-17 0:11 ` Corinna Vinschen
2019-02-18 10:01 ` Michael Haubenwallner
2019-02-18 10:43 ` Corinna Vinschen
2019-02-18 12:15 ` Michael Haubenwallner
2019-02-18 13:39 ` Corinna Vinschen
2019-02-18 15:13 ` Michael Haubenwallner
2019-02-18 16:04 ` Corinna Vinschen
2019-02-15 14:20 ` Andrey Repin
2019-02-15 18:50 ` portable use of dos2unix WAS: " Michael Haubenwallner
2019-02-15 19:14 ` Andrey Repin
2019-02-15 19:43 ` Michael Haubenwallner
2019-02-15 20:50 ` Andrey Repin
2019-02-15 21:21 ` Corinna Vinschen
2019-02-18 10:09 ` Michael Haubenwallner
2019-02-18 10:26 ` Corinna Vinschen
2019-02-18 13:07 ` Jeffrey Walton [this message]
2019-02-15 21:32 ` Brian Inglis
2019-02-16 6:09 ` Jeffrey Walton
2019-02-16 9:45 ` Corinna Vinschen
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='CAH8yC8n0zRsMrvLn+HtKhG2tg-ghznK=R7CkD-=FMQouppdQ1w@mail.gmail.com' \
--to=noloader@gmail.com \
--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).