You should look into running ssh, that way you can telnet in from anywhere
and everything will be encrypted. I do it all the time, from home to work,
using ssh. Works great.
jake
On Thu, 4 May 2000, Michael J. McGillick wrote:
> Afternoon:
>
> I understand the security implications of doing this. We're working on an
> internal network not connected to the Internet. This is a development
> laboratory where I frequently need to install and test software
> applications I support on more than one UNIX platform. These applications
> need to be installed as root. Our office deals with just about every
> flavor and release of UNIX imaginable, and it can get very tedious looking
> and for different versions if sudo, if they exist, for the different
> systems.
>
> I do appreciate the concerns of others on the list, but was just looking
> for the elusive piece of infomration on how to set it up, even if it it is
> incorrect. I more concerned with getting the work completed and tested at
> the moment.
>
> - Mike
>
> On Thu, 4 May 2000, Steve Borho wrote:
>
> > On Thu, May 04, 2000 at 08:27:56PM -0400, Ed Schernau wrote:
> > > I love this one, I hope more people ask about root telnet, so
> > > that it can continue to so obviously infuriate the many wise
> > > list users whose answer is "dont".
> > >
> > > Ed, he who telnets as root across his home LAN all the time.
> >
> > Installing sudo will keep you from developing bad habits. It's like those
> > people who alias rm to 'rm -i' and then get used to typing "rm *" to
> > delete just one file. Works fine until they log into their friends
> > machine that doesn't have the alias defined, and .... *boom*
> >
> >
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
>
>
Jake McHenry
[EMAIL PROTECTED]
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
