Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Oct 2000 18:39:00 +0200
From:      bk <koester@x-itec.de>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Re: Root-Like telnet account
Message-ID:  <14122691348.20001020183900@x-itec.de>
In-Reply-To: <007401c036f8$10325fe0$86e1e440@lmc.ericsson.se>
References:  <MDAEMON10001200010151918.AA1823076@sbohm.yi.org> <007401c036f8$10325fe0$86e1e440@lmc.ericsson.se>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello Travor,

Monday, October 16, 2000, 12:34:20 AM, you wrote:

>> Hi,
>>
>> I just installed FreeBSD on an older system I have, just to try it out,
MG> and would like to be able to telnet into it, and configure things remotely.
MG> Is is possible to make it so that I can login from root, or that another
MG> account has many of the same pr
>> velages as root, such as modifying configuration files?

look at /etc/ttys and add "secure" on the terminal you want to connect
to. if you do not know the right termial, login with a normal account
remotely and use the command "w" to see who is online.

Example:

localhost# w
 8:46PM  up  1:11, 2 users, load averages: 0.01, 0.00, 0.00
USER             TTY      FROM              LOGIN@  IDLE WHAT
root             v0       -                 7:36PM  1:08 -csh (csh)
blabla           p0       master            8:39PM     - w

i am looging in as root remotely from v0 on the console and from p0
remotely. so i have to add secure to the ttyp0 pseudo terminal.

If you want to keep your bsd system secure, i suggest you not to allow
root to login remotely.
Create a user with adduser command and put this user into the group
"wheel". login with this user and enter "su" to switch to root
account. This is more secure, because an external attacker do not know
what account is required to logon or to be root.


>>
>> Also, when I login to through telnet, it connects, and sits for about 1-2
MG> minutes before I get a login dialog.  After this, data transfers very

this is mostly a resolver "problem" (not a real one). Look in your /etc/hosts and add
pseudo names of your client(s). for example, if you want to connect from
192.168.0.2 to your freebsd server 192.168.0.99 then you add on your
freebsd server this line

192.168.0.2             master

master is a pseudonym only for the freebsd resolver. all connects are
tried to resolv to a hostname, if there is no nameserver available and
if there is no hostname, it seems to block somewhere. This is a
normal and will stop i think if you modify/create your /etc/hosts.

-- 
Boris Köster




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14122691348.20001020183900>