From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] rsh-0.17-3
Date: Mon, 16 Jul 2018 09:03:00 -0000 [thread overview]
Message-ID: <87h8kzsgbv.fsf@Rainer.invalid> (raw)
In-Reply-To: <20180716174907.6de89a81b55e404dc62a4e18@nifty.ne.jp> (Takashi Yano's message of "Mon, 16 Jul 2018 17:49:07 +0900")
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.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2018-07-16 9:03 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 [this message]
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
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=87h8kzsgbv.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).