public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] rsh-0.17-3
Date: Mon, 16 Jul 2018 09:33:00 -0000	[thread overview]
Message-ID: <20180716093257.GC7249@calimero.vinschen.de> (raw)
In-Reply-To: <20180716091644.GB7249@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]

On Jul 16 11:16, Corinna Vinschen wrote:
> On Jul 16 11:03, Achim Gratz wrote:
> > Takashi Yano writes:
> > > I agree rlogin/rsh/rexec are outdated. However, most major Linux
> > > and BSD distributions still provide them as a package.
> > >
> > > Should not Cygwin follow these as well?
> > 
> > Even on the UN*X side the r-tools have been deprecated for so long it
> > doesn't really make sense to use them anymore.  The only sane way to use
> > them is in fully isolated networks and I haven't seen any of those in
> > decades.  With Cygwin running on top of Windows there is ahole other set
> > of issues to deal with and that makes it even more inappropriate to even
> > offer those tools.  IMHO, deferring to the security lead for Cygwin.
> 
> We have a security lead?

Personally I agree with Takashi, btw.  Linux still provides the old r*
tools including rsh-server.  There may still be legit uses of the tools
in controlled environments.  if we remove all packages which can be used
to shoot yourself in the foot, there's not much left, I guess.

As a compromise, we could continue to provide the client package and
just discontinue the server package, but it's your choice.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-07-16  9:33 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 [this message]
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
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=20180716093257.GC7249@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --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).