From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] rsh-0.17-3
Date: Mon, 16 Jul 2018 16:06:00 -0000 [thread overview]
Message-ID: <20180717010613.0cc8eb0fd4b34b197bab74d9@nifty.ne.jp> (raw)
In-Reply-To: <b433e196-271a-f61b-01ae-826cfbdacf80@gmail.com>
On Mon, 16 Jul 2018 09:54:02 -0400
cyg Simple wrote:
> On 7/16/2018 5:32 AM, Corinna Vinschen wrote:
> > As a compromise, we could continue to provide the client package and
> > just discontinue the server package, but it's your choice.
>
> What use would there be even for the client? Even in my home mode
> connecting to BlueHost or any other such service I need ssh to connect
> to my server.
The existence of the rsh package itself does not pose a vulnerability
to cygwin. People who do not need rsh package do not have to install it.
Should not it leaves on users to decide whether to install or not?
I think that it is better for users to have a choice.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2018-07-16 16:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-15 19:55 Takashi Yano
2018-07-16 8:35 ` Achim Gratz
2018-07-16 8:49 ` Takashi Yano
2018-07-16 9:03 ` Achim Gratz
2018-07-16 9:16 ` Corinna Vinschen
2018-07-16 9:33 ` Corinna Vinschen
2018-07-16 13:54 ` cyg Simple
2018-07-16 14:02 ` Stephen John Smoogen
2018-07-16 14:22 ` cyg Simple
2018-07-16 15:09 ` Stephen John Smoogen
2018-07-16 15:29 ` Corinna Vinschen
2018-07-16 20:14 ` Brian Inglis
2018-07-16 16:06 ` Takashi Yano [this message]
2018-07-16 16:40 ` cyg Simple
2018-07-17 8:25 ` Corinna Vinschen
2018-07-19 11:32 ` Takashi Yano
2018-07-16 15:45 ` Achim Gratz
2018-07-17 8:27 ` Corinna Vinschen
2018-07-16 10:06 ` Achim Gratz
2018-07-16 10:22 ` Corinna Vinschen
2018-07-19 11:58 ` Takashi Yano
2018-07-26 18:45 ` Andrew Schulman
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=20180717010613.0cc8eb0fd4b34b197bab74d9@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).