Re: [LinkStation_General] Really newbie questions about OpenLink/Twonky installation
- --- wheely30km <wheely30km@...> wrote:
> Hi everybody,
> I want to install Twonky on my Linkstation2.
> I followed the instructions in the wiki how-to :
I don't own a Linkstation yet and have Limited linux
background, but I'll take a stab partially because I'm
bored right now. Correct me if I'm wrong.
> Now my dumb questions [:">]You don't want everyone to have the same default
> step 12 : what's the purpose of changing the root
> password ? Does it
> affect the connection to the LS2 through the web
> browser by asking this
> password, or is it only for telnet ?
password, do you? Root, also known as the super user
has special privledges and you only log on, or run a
program with root privledges when you HAVE TO.
In the world of Unix/Linux, files are created with an
owner, a group and are set to be read, write or
executable by everybody, the owner or the group or a
combination. Only root can overide these privledges
and root is the owner of many files that control
configuration. Hence, root is like the Administrator
user for a PC system. The PC doesn't have an owner or
group associated with a file. This is the short
version. An odd thing about Unix/Linix is that the
password file /etc/passwd is readable by everybody and
the password encryption is one way, so the ciphertext
is in clear text in that file and the password is
unrecoverable in cleartext.
>Telnet passes passwords in clear text. That means
> step 13 : installing a ssh daemon to get a secure
> connection : so there
> must be a connection that is not secure : I suppose
> it's Telnet ?
> who could hack it, as it's a home network behind a
> firewalled router ?
readable by the naked eye with a packet sniffer. If
you don't open up port 23, the default for Telnet,
then I suppose your OK.
>Yep. Called disabing Telnet which is an insecure
> step 14 : why should I disable the utelnetd startup
> link it if there's a
> SSH daemon : to avoid hackers to connect with telnet
protocol because it passes passwords in the clear.
> step 15&16 : why should I adjust the "utelnetdCan't answer that one.
> startup script" ? what
> are the effects of this modification ? does it make
> asking for a
> password, thus making it safer ?
>See the answer to step 12. I'll guess. You create
> step 17 : what is a non root account, and how do I
> create it ?
accounts using the web browser interface. All users
use the same password for whatever method one uses to
login. Again short version. With ssh/scp, you can
operate between "TRUSTED" hosts without passwords. ssh
stands for "Secure Shell". scp stands for "Secure
>I suppose not, UNLESS twonky is installed without root
> Finally, do I have to make any of those steps to get
> twonky running on
> my LS2 ?
privledges. If it doesn't need root privledges to
run, then don't install it running as root. A
misbehaving program can destroy the operating system.
>I've been using Unix on and off since 1975 and I've
> Really sorry for those dumb questions, but Linux is
> like chinese for
> me, I would like to learn it but I'm not sure I will
> ever have enough
> time [:-s]
used a Keypunch machine and a teletype ASR 33.
> Thanks all for your patience to read my post, and
> even more to answer my
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
- --- In LinkStation_General@yahoogroups.com, KeepIt SimpleStupid
> --- wheely30km <wheely30km@...> wrote:[...]
> > I want to install Twonky on my Linkstation2.
> > step 12 : what's the purpose of changing the rootFor everything. Everone logged on as root has full control over your
> > password ? Does it
> > affect the connection to the LS2 through the web
> > browser by asking this
> > password, or is it only for telnet ?
> > step 15&16 : why should I adjust the "utelnetdCorrect. But you should really install and test SSH, and once you can
> > startup script" ? what
> > are the effects of this modification ? does it make
> > asking for a
> > password, thus making it safer ?
log in with SSH (not earlier), disable Telnet altogether!