server software

[punk000]

are there any telnet daemons or dns serving software included in the knoppix distro?

[aay]

You can look at a complete list of the software on the CD here (ftp://ftp.uni-kl.de/pub/linux/knoppix/packages.txt). You can also check this list for updates by issuing this command: "dpkg -l |more"

[punk000]

does anyone know how to start the telnetd deamon? and the dns server software..

[David Douthitt]

Telnet is controlled by the network "super-daemon" inetd; look at inetd.conf to configure. Be aware that by using telnet you are sending your passwords - indeed, ALL of your telnet traffic - across the wire "in the clear" - that is, any of your passwords or your traffic is readable by someone with nothing more than a PC and a complete Linux installation. Better to use ssh.

Configuring and running a DNS server is much more complex; you might not want to run a DNS server until you are more comfortable with UNIX. Running a DNS server is non-trivial; there are many entire books on the topic.

Configuring SSH is also non-trivial - but is easier than DNS. It also has entire books written about it.

I recommend both of O'Reilly & Associates books on SSH and DNS. But you should know something of UNIX, too.

[punk000]

how often does initd search through initd.conf to see if i have added any services??? is there a way i ca trigger it to run through once, and start my server? and i know its going to be complexe, and thats what i am looking for..... and as for security, well.... im not a very security concoips person (yet) and i do not know of may expliots ect.... but at the same time, my computer is a home pc, and the data on it is non crucial, so id rather experiment with these things now and figure out any little kinks or tricks before i actually have something to protect asides my porn colection:P (joke joke).....


here is my inetd.conf
# /etc/inetd.conf: see inetd(8) for further informations.
#
# Internet server configuration database
#
#
# Lines starting with "#:LABEL:" or "#<off>#" should not
# be changed unless you know what you are doing!
#
# If you want to disable an entry so it isn't touched during
# package updates just comment it out with a single '#' character.
#
# Packages should modify this file by using update-inetd(8)
#
# <service_name> <sock_type> <proto> <flags> <user> <server_path> <args>
#
#:INTERNAL: Internal services
#echo stream tcp nowait root internal
#echo dgram udp wait root internal
#chargen stream tcp nowait root internal
#chargen dgram udp wait root internal
discard stream tcp nowait root internal
discard dgram udp wait root internal
daytime stream tcp nowait root internal
#daytime dgram udp wait root internal
time stream tcp nowait root internal
#time dgram udp wait root internal

#:STANDARD: These are standard services.
ftp stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.ftpd
telnet stream tcp nowait root /usr/sbin/tcpd /usr/sbin/in.telnetd

#:BSD: Shell, login, exec and talk are BSD protocols.
talk dgram udp wait root.tty /usr/sbin/tcpd /usr/sbin/kotalkd
ntalk dgram udp wait root.tty /usr/sbin/tcpd /usr/sbin/ktalkd

#:MAIL: Mail, news and uucp services.

#:INFO: Info services

#:BOOT: Tftp service is provided primarily for booting. Most sites
# run this only on machines acting as "boot servers."
tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd /boot

#:RPC: RPC based services

#:HAM-RADIO: amateur-radio services

#:OTHER: Other services
#<off># netbios-ssn stream tcp nowait root /usr/sbin/tcpd /usr/sbin/smbd
#<off># netbios-ns dgram udp wait root /usr/sbin/tcpd /usr/sbin/nmbd -a
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd
vboxd stream tcp nowait root /usr/sbin/tcpd /usr/sbin/vboxd
saft stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sendfiled
xtel stream tcp nowait root /usr/sbin/tcpd /usr/sbin/xteld
amanda dgram udp wait backup /usr/sbin/tcpd /usr/lib/amanda/amandad
amandaidx stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amindexd
amidxtape stream tcp nowait backup /usr/sbin/tcpd /usr/lib/amanda/amidxtaped
#<off># https stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 80
#<off># ssmtp stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 25
#<off># nntps stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 119
#<off># telnets stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 23
#<off># imaps stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 143
#<off># ircs stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 194
#<off># pop3s stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 110
#<off># ftps-data stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 20
#<off># ftps stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 21
#<off># sswat stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 901

im guessing what i have to modify is the part here
#<off># telnets stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 23
so that it sais "on" and remove the #beacuse the makes it a descript, or does the second one close it??? wud this start the server?

im a noob, but love unix already, i bought the unix bible and killed it in almost 4 days.... but parts can be confusing withought help from ppl like you (which i apreciate)

[cascadefx]

how often does initd search through initd.conf to see if i have added any services???

It doesn't. You have to trigger it or restart the system (which won't help with the CD version since you can't save the changes that you make in inetd.conf to the CD).

You have to trigger it.


is there a way i ca trigger it to run through once, and start my server?

The commands for doing that from the root shell follow (do this after you make changes to inetd):

1. Type ps | grep inetd <--- list the processes running on the system and grab (via grep) the lines with inetd in them

2. Make note of the PID (Process ID)

3. Type kill -SIGHUP <replace this with inetd's PID > <--- sends the "hang up" signal to inetd and has it restart. When it restarts, it will reread the inetd.conf file and incorporate any changes that you have made.



and i know its going to be complexe, and thats what i am looking for..... and as for security, well.... im not a very security concoips person (yet) and i do not know of may expliots ect.... but at the same time, my computer is a home pc, and the data on it is non crucial, so id rather experiment with these things now and figure out any little kinks or tricks before i actually have something to protect asides my porn colection:P (joke joke).....

Messing with servers is very serious business for a number of reasons. That is why they are all turned off by default. It would be much better for you to just turn on the ssh (secure shell) server for the knoppix user from the knoppix menu (click on K | go to knoppix | you should find it in there). This server will accept connections from an ssh client and from an sftp client. That gives a secure (encrypted) way to interact with the system and to upload and download files.

Free ssh and sftp clients exists for all Operating System platforms. My favorite one for Windows is PuTTY. Do a search on http://www.google.com for ssh and putty and you will find it.

Telnet and FTP pass everything (including usernames and passwords) in plain text and are woefully insecure. Don't use them.

The other reason security is important, even if you aren't concerned is because people can launch attacks from insecure computers. So, your computer being compromised may not bother you, but if the attacker uses it to launch attacks against me... I would be very mad. That is why you should be security conscious even if you feel that your data isn't worthy of all the fuss.



here is my inetd.conf

<snipped for brevity>


im guessing what i have to modify is the part here
#<off># telnets stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 23
so that it sais "on" and remove the #beacuse the makes it a descript, or does the second one close it??? wud this start the server?

In unix the # means a comment (most of the time). Any line proceeded by it is ignored. Klaus (or another developer) used the designation #<off># to make that point painfully clear.

To actually enable the service, you have to remove all of his tag. So this

#<off># telnets stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 23

Would become this
telnets stream tcp nowait root /usr/sbin/tcpd /usr/sbin/sslwrap -nocert -addr 127.0.0.1 -port 23

Once you remove these lines and save the file, then you have to use the process that I mentioned up above.


im a noob, but love unix already, i bought the unix bible and killed it in almost 4 days.... but parts can be confusing withought help from ppl like you (which i apreciate)

Hopefully this was covered in the Unix Bible. If not, you may want to look at books like Running Linux or A Practical Guide to Linux or Unix Made Easy.

[punk000]

this is the output from a ps
PID TTY TIME CMD
21847 ttyp0 00:00:00 bash
22405 ttyp0 00:00:00 ps
so i did a ps -aux ( i saw it get allota data once so i figured "try it")
this is its output
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.0 72 60 ? S 09:31 0:04 init [5]
root 2 0.0 0.0 0 0 ? SW 09:31 0:00 [keventd]
root 3 0.0 0.0 0 0 ? SWN 09:31 0:00 [ksoftirqd_CPU0]
root 4 0.0 0.0 0 0 ? SW 09:31 0:01 [kswapd]
root 5 0.0 0.0 0 0 ? SW 09:31 0:00 [bdflush]
root 6 0.0 0.0 0 0 ? SW 09:31 0:00 [kupdated]
root 52 0.0 0.0 0 0 ? SW 09:32 0:00 [kapmd]
root 59 0.0 0.0 0 0 ? SW 09:32 0:00 [khubd]
root 214 0.0 0.2 1368 556 ? S 09:32 0:00 pump -i eth0
root 257 0.0 0.2 1316 548 ? S 09:32 0:07 /usr/sbin/automou
root 262 0.0 1.0 2856 1952 tty1 S 09:32 0:00 /bin/bash -login
root 263 0.0 1.0 2856 1952 tty2 S 09:32 0:00 /bin/bash -login
root 264 0.0 1.0 2856 1952 tty3 S 09:32 0:00 /bin/bash -login
root 265 0.0 1.0 2856 1952 tty4 S 09:32 0:00 /bin/bash -login
root 324 0.0 0.6 2260 1224 ? S 09:32 0:00 /bin/sh /etc/init
root 332 0.0 0.6 2260 1224 ? S 09:32 0:00 /bin/sh /etc/init
root 334 3.1 11.3 89992 21608 ? S 09:32 10:02 XFree86 -noreset
knoppix 350 0.0 0.6 2216 1196 ? S 09:32 0:00 /bin/sh /etc/X11/
knoppix 447 0.0 3.0 16772 5852 ? S 09:32 0:01 kdeinit: Running.
knoppix 450 0.0 3.3 16588 6472 ? S 09:32 0:04 kdeinit: dcopserv
knoppix 455 0.0 3.7 17588 7248 ? S 09:32 0:01 kdeinit: klaunche
knoppix 457 0.0 5.5 26464 10540 ? S 09:32 0:02 kdeinit: kded
knoppix 473 0.0 5.3 24952 10296 ? S 09:33 0:00 kdeinit: kxkb
knoppix 484 0.0 4.9 27288 9352 ? S 09:33 0:01 kdeinit: knotify
knoppix 485 0.0 0.1 1256 308 ? S 09:33 0:00 kwrapper ksmserve
knoppix 487 0.0 4.7 24224 9000 ? S 09:33 0:00 kdeinit: ksmserve
knoppix 493 0.1 5.6 25540 10800 ? S 09:33 0:34 kdeinit: kwin -se
knoppix 496 0.2 7.2 30508 13900 ? S 09:33 0:44 kdeinit: kdesktop
knoppix 504 0.2 6.9 28236 13252 ? S 09:33 0:51 kdeinit: kicker
root 555 0.0 0.0 0 0 ? SW 09:33 0:00 [eth0]
root 644 0.0 0.3 1932 728 ? S 09:33 0:00 /usr/sbin/pppd ca
root 646 0.0 0.2 1212 428 ? S 09:33 0:06 /usr/sbin/pppoe -
knoppix 753 0.0 5.5 24876 10524 ? S 09:34 0:02 kdeinit: kcookiej
knoppix 756 0.0 2.1 12124 4196 ? S 09:34 0:01 /usr/bin/kdesud
knoppix 970 0.0 5.8 25028 11116 ? S 09:37 0:01 kdeinit: kio_uise
knoppix 6177 0.1 7.1 28436 13632 ? S 10:54 0:15 kdeinit: kio_thum
knoppix 6178 0.0 3.3 16884 6356 ? S 10:54 0:00 kdeinit: kio_file
root 8180 0.0 0.3 1400 652 ? S 11:25 0:00 cron
knoppix 12771 87.6 6.9 28592 13172 ? R 12:38 115:32 kdeinit: kio_thum
knoppix 18932 0.0 2.4 7744 4620 ? S 14:01 0:02 /usr/bin/gaim
knoppix 18954 1.5 12.9 40176 24752 ? S 14:01 0:44 kdeinit: konquero
knoppix 20904 0.0 0.5 2068 1016 ? S 14:28 0:00 /bin/sh /usr/sbin
root 20928 0.0 0.6 2508 1220 ? S 14:28 0:00 /usr/sbin/sshd
knoppix 21840 0.2 6.0 26384 11480 ? R 14:41 0:01 kdeinit: konsole
knoppix 21847 0.1 0.9 2792 1892 ttyp0 S 14:41 0:00 /bin/bash
knoppix 22419 0.0 3.6 17188 6896 ? S 14:49 0:00 kdeinit: kio_http
knoppix 22422 0.1 3.5 17056 6740 ? S 14:49 0:00 kdeinit: kio_http
knoppix 22470 0.0 0.8 3440 1564 ttyp0 R 14:50 0:00 ps -aux
and if i grep the process... i kinda get a fluke thing...... i see the procces of my grep....:P so i see
knoppix 22591 0.0 0.2 1276 416 ttyp0 S 14:52 0:00 grep inetd
hehee kinda funny, but it dont help

[punk000]

got it all working... thanx:)

[cascadefx]

got it all working... thanx:)

Share how you got it to work.

[punk000]

oaky.....
well firt off. i want you all to know that i didnt figure this all out, the credit goes to others, who helped me...

first
$sudo -s
#cd /etc
#vim inetd.conf
#(ctrl+z)
#rm inetd.conf
"remove symbolic link to file (Y/N):"
#y
#fg
** here make the modifications to the inetd.conf file that u want, (to start services all you have to do is un-note the sections you want to start.... do this by removing #[off]#) you need some knoledge of vi or vim...
** write the file back... make sure you keep the same name!!!! it shudnt have changed... but dont write it to a new name....
** after the file has been written jsut :x to exit... (i know this saves and exits, but i dunno the exit command :P)
#cd init.d
#inetd start

your services shud be started, thank to all of you who helped... it was a great learing experience!!!

[punk000]

please not that $ is a regular user comand prompt... and #is the super user command prompt :D

[cascadefx]

** after the file has been written jsut :x to exit... (i know this saves and exits, but i dunno the exit command :P)


Check out this article for some help with the vi(m) editor: Easing Into Editors (redux): vim (http://www.systemtoolbox.com/article.php?articles_id=57). It includes most of the commands that you will need for simple editing.