hallo ich habe auf meinen root bouncer installiert und ich möchte einen trust requesten dafür brauche ich OIDENT
Wie installier ich es unter Redhat ?
hallo ich habe auf meinen root bouncer installiert und ich möchte einen trust requesten dafür brauche ich OIDENT
Wie installier ich es unter Redhat ?
http://at.search.yahoo.com/sea…fl=0&vc=&x=wrt&meta=vc%3D
Ist zwar in diesem Falle eine Suche nach psyBNC, sollte sich aber für jeden anderen Bouncer der oidentd unterstützt anwenden lassen.
Cheers
tcs
ZitatAlles anzeigen
Q15: How to use psyBNC with oidentd?
A:
1. Installation:
You can install oidentd with an rpm or download the source code and compile it by yourself.
a) rpm installation
First change to the desired directory and download the rpm package:
wget http://url.to/oident.tgz
now install the rpm:
rpm -Uhv oidentd-2.0.4-2.i386.rpm
If everything runs configure oidentd and psyBNC.
Now you should stop the old identd daemon: killall -9 identd
Afterwards you should by means of: /etc/init.d/oidentd start start oidentd.
Delete the entries of the old identd daemons if these are still present.
b) source (tar.gz) installation
First you should if not already done, download the newest version of oidentd.
Change for example to your gome home directory and enter:
wget http://belnet.dl.sourceforge.n…ojnk/oidentd-2.0.4.tar.gz
Now you should extract the package: tar -xzvf oidentd-2.0.5.tar.gz
and change to the extracted directory: cd oidentd-2.0.4
Now its time to configure and make the oidentd:
./configure --prefix=/usr
make
and as root: make install
If you receive any error after the ./configure --prefix=/usr step, your system may miss some packages.
In most cases you'll need these packages (they are for an i386 system and should work on most linux distributions,
if they dont go to rpmfind.net, and search for the packages yourself):
flex -> ftp://ftp.rpmfind.net/linux/re…S/flex-2.5.4a-23.i386.rpm
bison -> ftp://ftp.rpmfind.net/linux/re…PMS/bison-1.35-1.i386.rpm
byacc -> ftp://ftp.rpmfind.net/linux/re…PMS/byacc-1.9-19.i386.rpm
to install them, type "wget ftp://path/file.rpm" and "rpm -Uhv file.rpm"
oidentd should correct installed now and you should stop the old inetd deamons with: killall -9 identd
In order to examine the correct installation, you should search the file /usr/sbin/oidentd.
If it exists, everything was correct.
2. Configuration of oidentd:
After you successfully installed oidentd, it will be necessary to configure a few things.
If the file /etc/oidentd.conf not be available, create it with an editor like vi or mcedit.
Make sure that the file is created in unix text mode and not in dos text mode, else you'll get an error when trying
to start oidentd later, that says something like "can't read configuration file" or "error in configuration file".
In order to permit each bouncer user to get his own ident, change the /etc/oidentd.conf as follows and make sure that
it can be read by any user. To ensure this, type: chmod 644 /etc/oidentd.conf
In order to permit that each bouncer user gets his own ident, change the /etc/oidentd.conf as follows:
--------------------------------------------------------------------------------
# Configuration for oidentd
# see oidentd.conf(5)
#
default {
default {
allow spoof
allow spoof_all
allow spoof_privport
allow random
allow random_numeric
allow numeric
allow hide
}
}
--------------------------------------------------------------------------------
3. Configuration of psyBNC:
That psyBNC work together with oidentd, you must activate the oidentd support for psyBNC.
This can be realized either by make menuconfig, or however manually, editing the file config.h and insert into a free line:
#define OIDENTD
Afterwards you must recompile psyBNC. All psyBNC passwords would become invalid.
To prevent this use the following method: 1. You need a copy of salt.h - you can provide with: cp salt.h salt.bak
2. You need a copy of its psyBNC.conf - you can provide with: cp psyBNC.conf psyBNC.bak
It applies to provide both copies before the recompilation. If the file salt.h was moved or renamed,
you must copy it back to the psyBNC directory and rename it in salt.h.
Afterwards you could execute 'make'. After make is finished, you must retransfer psyBNC.bak and
rename it in"psybnc.conf". 'cp psybnc.bak psybnc.conf'
Now psyBNC has oidentd support and you lost no passwords.
Now you can start oidentd manually and examine if the idents are correctly indicated:
/usr/sbin/oidentd -m -u nobody -g nogroup
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!