From: Pierre Souchay <pierre@souchay.net>
To: cygwin-apps@cygwin.com
Subject: Re: Patch for openssh : allow to use AuthorizedKeysCommand on sshd on cygwin
Date: Mon, 31 Jul 2017 21:07:00 -0000 [thread overview]
Message-ID: <BCE73C40-C4B3-4D40-87B0-566CD407F213@souchay.net> (raw)
In-Reply-To: <20170731201228.GF18950@calimero.vinschen.de>
Hi Corinna,
> On 31 Jul 2017, at 22:12, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
>
> On Jul 31 20:38, Pierre Souchay wrote:
>> Hello,
>>
>> Please consider this patch: https://github.com/pierresouchay/cygwin_patches/blob/master/openssh.patch
>>
>> It patches opensshd to allow to use the AuthorizedKeysCommand on Cygwin (similar to https://github.com/openssh/openssh-portable/pull/72 )
>
> Cygwin's OpenSSH is built from upstream sources only. Consequentially
> this patch will go into Cygwin's OpenSSH package as soon as an official
> OpenSSH version will be released with this patch.
This patch can be applied on sources in current Cygwin repositories (aka openssh-7.4p1-1), so, if I understand well, you don't want to use the PATCH_URI mechanism of cygport to fix the issue and prefer me to do the fix upstream in OpenBSD source code?
(The issue being that root on CYGWIN is not uid=0 but uid=18 aka SYSTEM)
I'll send a patch to openbds maintainers as well, but since the patch is Cygwin centric, I expected it would take less time to be applied this way.
Regards
Pierre Souchay
>
>
> Corinna
>
> --
> Corinna Vinschen Please, send mails regarding Cygwin to
> Cygwin Maintainer cygwin AT cygwin DOT com
> Red Hat
next prev parent reply other threads:[~2017-07-31 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 18:38 Pierre Souchay
2017-07-31 20:12 ` Corinna Vinschen
2017-07-31 21:07 ` Pierre Souchay [this message]
2017-08-01 8:54 ` Corinna Vinschen
2017-08-01 18:25 ` Achim Gratz
2017-08-01 20:53 ` Pierre Souchay
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=BCE73C40-C4B3-4D40-87B0-566CD407F213@souchay.net \
--to=pierre@souchay.net \
--cc=cygwin-apps@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).