public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Allen Parker" <allenp@efn.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: FW: [gentoo-dev] suggestion: virtual/telnet
Date: Sat, 27 Dec 2003 21:44:06 -0500	[thread overview]
Message-ID: <E1AaQuV-0000uX-NK@smtp.gentoo.org> (raw)

Sorry, the first time I sent it, I hit the wrong reply button.

> -----Original Message-----
> From: Allen Parker [mailto:allenp@efn.org]
> Sent: Saturday, December 27, 2003 7:32 PM
> To: 'Ciaran McCreesh'
> Subject: RE: [gentoo-dev] suggestion: virtual/telnet
> 
> I must pipe up on this one. When a user asks for "telnet" they're usually
> not aware of the security risks involved. (kinda makes me wonder why it's
> installed by default on Debian :-\) Probably the best way to handle this
> is to create a virtual/telnet and add a default package that when
> uninstalled displays a basic readme saying telnet isn't secure and why,
> asks the user if they still want to do it, and THEN after they've
> confirmed that they do in fact want telnet, allow them to emerge whichever
> telnet they choose.
> 
> So, to re-state because I'm not even sure what I said up there:
> Create package block-telnet that does as it's name implies, blocks the
> virtual/telnet package so that no other telnetd/telnet client may be
> emerged without removing it first.
> Setup block-telnet to install something like /usr/share/doc/telnet-readme
> (the contents of the same thing you read when you remove block-telnet) and
> upon unmerge fire off a simple shell script that less's the same file
> (hidden) that is telnet-readme with a yes/no choice saying are you sure
> you wish to remove me?
> Add block-telnet -> virtual/telnet as a virtual/telnet blocker by default
> for all arch/stage/devel profiles under system instead of world and make
> it a default package (like nano) for Gentoo 2004.
> 
> It honestly seems to me that this would probably take any dev minutes to
> set the virtual up this way and it would also allow very fast, short
> answers in regards to getting questions on telnet:
> 
> Eg:
> User: how do I install telnet?
> Dev: emerge unmerge block-telnet ... and read what it says.
> User: thanks for your help!
> 
> That's my 2/100ths of a monetary unit.
> Allen Parker
> 
> > -----Original Message-----
> > From: Ciaran McCreesh [mailto:ciaranm@gentoo.org]
> > Sent: Saturday, December 27, 2003 6:06 PM
> > To: gentoo-dev@lists.gentoo.org
> > Subject: Re: [gentoo-dev] suggestion: virtual/telnet
> >
> > On Sat, 27 Dec 2003 23:03:23 +0100 Spider <spider@gentoo.org> wrote:
> > | Well,
> > |   this is something that a lot of users ask about (how do I get
> > |   telnet?)
> >
> > Wouldn't it be better to educate the users to get rid of that 'type in
> > emerge telnet to install telnet' mentality?
> >
> > --
> > Ciaran McCreesh
> > Mail:    ciaranm at gentoo.org
> > Web:     http://dev.gentoo.org/~ciaranm



--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-12-28  3:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-28  2:44 Allen Parker [this message]
2003-12-28  3:34 ` [gentoo-dev] suggestion: virtual/telnet Jason Wever
2003-12-28 10:26   ` Mike Williams
2003-12-28 10:33     ` Ciaran McCreesh
2003-12-28 13:01       ` Mike Frysinger
2003-12-28 10:47     ` Jeremy Maitin-Shepard
2003-12-28  3:37 ` Allen Parker

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=E1AaQuV-0000uX-NK@smtp.gentoo.org \
    --to=allenp@efn.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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