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: Tue, 17 Jul 2018 08:27:00 -0000	[thread overview]
Message-ID: <20180717082610.GB6137@calimero.vinschen.de> (raw)
In-Reply-To: <878t6brxp7.fsf@Rainer.invalid>

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

On Jul 16 17:45, Achim Gratz wrote:
> Corinna Vinschen writes:
> > 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.
> 
> I would normally agree, but in this particular case I've never seen an
> environment controlled enough to allow this safely and certainly not
> anywhere near anything running Windows.  I'm not saying it isn't
> possible or it doesn't exist, it's just that setting it up is going to
> take more work than using SSH.  If the real reason is legacy equipment
> (I actually have to deal with that, just not with rsh specifically),
> then I'd rather put an access relay in front of it than compromise my
> entire network.  This stuff usually has a bunch of other quirks/problems
> that you don't want to expose.
> 
> > As a compromise, we could continue to provide the client package and
> > just discontinue the server package, but it's your choice.
> 
> You'd still send all sensitive information over the network.
> 
> I've just checked and openSUSE no longer offers the netkit tools.  There
> are packages for mrsh (using munge authentication) and compat packages
> providing rsh/rcp and the respective daemons.
> 
> Debian optionally replaces the rsh-server with rsh-redone-server and
> rsh-client with openssh-client (i.e. these provide some or all
> functionality of the corresponding netkit packages).

Fedora just packs them:

  rsh-0.17-86.fc28.x86_64
  rsh-server-0.17-86.fc28.x86_64


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-17  8:27 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
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 [this message]
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=20180717082610.GB6137@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).