devil-linux-develop — developer discussions

[Devil-linux-develop] Package Requests

[<js...@bi...>]

Hi,
I have been very impressed by how relatively easy DL is to build and
customize. 

I'd be interested in having the following packages added to Devil-Linux 

nullmailer
Description:
This is nullmailer, a sendmail/qmail/etc replacement MTA for hosts which
relay to a fixed set of smart relays.  It is designed to be simple to
configure, secure, and easily extendable. 

homepage: http://untroubled.org/nullmailer/ 

dnstop
Description
dnstop is a libpcap application (ala tcpdump) that displays various tables 
of DNS traffic on your network. Currently dnstop displays tables of: 

Source IP addresses
Destination IP addresses
Query types
Top level domains
Second level domains
Third level domains
If people find dnstop useful and interesting, we plan to add additional 
tables, such as classification of legitimate/illegitimate queries. 

homepage: http://dns.measurement-factory.com/tools/dnstop/ 


thanks,
jon 

[Devil-linux-develop] PPTP - MPPE/MPPC kernel module for Linux

[Serge L. <se...@nn...>]

Dear Sirs,

I decided to use pptp connection with mppe/mppc possibility
The patch and manual were found here - http://free.polbox.pl/h/hs001/
> Although the module's source code is completely free, MPPC itself is
> patented algorithm. Patent for *Microsoft* PPC is holded by the Hifn
> Inc. This is obvious ;-). Furthermore, MPPE uses RC4[1] encryption
> algorithm which itself isn't patented, but RC4 is trademark of RSA
> Data Security Inc. To avoid legal problems, US citizens shouldn't
> use this module.     

After some minor changes in pptp-patch script it was rebuilt
successfully.

http://free.polbox.pl/h/hs001/linux-2.4.29-mppe-mppc-1.3.patch.gz
original, but repacked by bzip2
./src/linux-2.4.29-mppe-mppc-1.3.patch.bz2

http://free.polbox.pl/h/hs001/ppp-2.4.3-mppe-mppc-1.1.patch.gz
A little modified version - for using together with other ppp-patch
scripts (09_ppp-2.4.3-mppe-mppc-1.1.patch) is in the attachment

and, finally
in /etc/modules.conf
#alias ppp-compress-18  ppp_mppe
alias ppp-compress-18   ppp_mppe_mppc

PS. If IMQ path renew to http://www.linuximq.net/patchs/linux-2.4.28-imq2.diff
( I've saved it as IMQ-iptables-1.3.0.diff.bz2 )
then iptables will be able renew too (to 1.3.1) without any problems.

> root@rsf:~ # uname -a
> Linux rsf 2.4.30 #1 Tue Apr 26 11:01:43 EST 2005 i686 GenuineIntel unknown GNU/Linux
> root@rsf:~ # iptables -V
> iptables v1.3.1

-- 
Best regards,
 Serge                          mailto:se...@nn...

[Devil-linux-develop] DNSMASQ & DHCPD - collosion

[Kari M. <ka...@tr...>]

There is a pending co-operation problem with /etc/init.d/dhcpd and=20
/etc/init.d/dnsmasq.

If I disable dhcpd in /etc/sysconfig/config, and enable dnsmasq, the=20
dnsmasq does not start. Why? dhcpd is still starting and reserving the=20
port for dhcp service.

So far I have fixed this with the following change to /etc/init.d/dhcpd

# Default-Start:
# Default-Stop:   0 1 3 5 6

and by erasing the start script in rc3.d with command

rm /etc/init.7d/rc3.d/S??dhcpd


After those changes dnsmasq works ok.

It is only, that after every DL upgrade, I either have to redo the=20
above, or not to migrate /etc/init.d/dhcpd file.

I'm not saying how this should be fixed, because I don't know all the=20
innings of DL boot process -- not yet, anyway.  I just throw the ball=20
out to you...



Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

[Devil-linux-develop] [PATCH] Add support for Outlook clients - cyrus-sasl

[Martin G. <sou...@gl...>]

Hi,

A minor patch to add login support to cyrus-sasl which allows Outlook clients 
to authenticate against a Postfix server.

Thanks

Martin

Re: [Devil-linux-develop] DL mail gateway notes

[Heiko Z. <he...@zu...>]

> Heiko Zuerker wrote:
>
>> Kari Mattsson wrote:
>>
>>
>>>
>>> Few notes from my mailgw.....com project:
>>>
>>>
>> I guess it would be nice to post the key settings to the discuss list,
>> I'm sure some users will appreciate this.
>>
>
> I'll do that a bit later.  Obvious suggestion..
>
>
>>> - it would be a great addition, if i could integrate postfix to
>>> saslauthd on this same setup, but it is not possible at this time due
>>> to a missing saslauth conf file -- this seems to be a known issue
>>
>>
>> Are we missing this file?
>>
>
> I'm referring to an earlier discussion on this list with subject
> "patch to get postfix to work with saslauthd".
>
>
> The following URL says it "all":
> http://sourceforge.net/mailarchive/forum.php?thread_id=6791055&forum_id=43
> 2
>
>
> The file /usr/lib/sasl2/smtpd.conf is missing.  It is a bit tricky to
> fix properly, as you have to modify that file to suit your authentication
> requirements.

Now it's coming back...

I'll see what I can do, I just don't have much time and really would like
to release 1.2.5 ASAP.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] DL mail gateway notes

[Kari M. <ka...@tr...>]

Heiko Zuerker wrote:
> Kari Mattsson wrote:
> 
>>
>> Few notes from my mailgw.....com project:
>>
> I guess it would be nice to post the key settings to the discuss list, 
> I'm sure some users will appreciate this.

I'll do that a bit later.  Obvious suggestion..

>> - it would be a great addition, if i could integrate postfix to 
>> saslauthd on this same setup, but it is not possible at this time due 
>> to a missing saslauth conf file -- this seems to be a known issue
> 
> 
> Are we missing this file?

I'm referring to an earlier discussion on this list with subject
"patch to get postfix to work with saslauthd".

The following URL says it "all":
http://sourceforge.net/mailarchive/forum.php?thread_id=6791055&forum_id=432

The file /usr/lib/sasl2/smtpd.conf is missing.  It is a bit tricky to 
fix properly, as you have to modify that file to suit your 
authentication requirements.

/Kari

Re: [Devil-linux-develop] Sagator and ClamAV interaction+integration on DL - minor fix

[Kari M. <ka...@tr...>]

Heiko Zuerker wrote:
> Kari Mattsson wrote:
> 
>> Sagator's readme file recommends changing the following two files
>> /etc/freshclam.conf
>> /etc/clamd.conf
>>
>> ...and the change is simple:
>>
>> DatabaseDirectory /var/spool/vscan/var/lib/clamav
> 
> 
> Hmmmm......
> Anybody else has an oppinion about this?

I do :-)  Don't do the change.  Yesterday I re-created the email filter
from scratch (=default etc.tar.bz2), and it actually doesn't work with
the above DatabaseDirectory /var/spool/vscan... setting.  Sagator
complains about not being able to find signatures.

The default in /etc/freshclam.conf works ok.

:-)  ...and I don't the clamd any more. I just commented out 2 lines
starting clamd in file /etc/init.d/clamd in the start section.  It was
easier than splitting the init.d script and then playing with the
startup dependencies.

/Kari

Re: [Devil-linux-develop] Sagator and ClamAV interaction+integration on DL - minor fix

[Kari M. <kar...@tr...>]

Heiko Zuerker wrote:
> Kari Mattsson wrote:
> 
>> Sagator's readme file recommends changing the following two files
>> /etc/freshclam.conf
>> /etc/clamd.conf
>>
>> ...and the change is simple:
>>
>> DatabaseDirectory /var/spool/vscan/var/lib/clamav
> 
> 
> Hmmmm......
> Anybody else has an oppinion about this?

I do :-)  Don't do the change.  Yesterday I re-created the email filter 
from scratch (=default etc.tar.bz2), and it actually doesn't work with 
the above DatabaseDirectory /var/spool/vscan... setting.  Sagator 
complains about not being able to find signatures.

The default in /etc/freshclam.conf works ok.

:-)  ...and I don't the clamd any more. I just commented out 2 lines 
starting clamd in file /etc/init.d/clamd in the start section.  It was 
easier than splitting the init.d script and then playing with the 
startup dependencies.

/Kari

Re: [Devil-linux-develop] Sagator and ClamAV interaction+integration on DL - minor fix

[Heiko Z. <he...@zu...>]

Kari Mattsson wrote:

>
> This is for mail gateway implementations of Devil-Linux.
>
> Sagator is a nice integrator between Postfix, SpamAssassin and ClamAV.
>
> The default settings with DL are not working properly.  Previously I 
> sent a minor fix for SpamAssassin+Sagator.  This posting is for 
> ClamAV+Sagator.
>
> You can do this in many different ways.  This way changes as little as 
> possible the default configuration.
>
> I suggest you add to file /etc/sysconfig/jail/SAGATOR the following 3 
> lines to add the directory (with proper user rights) for virus 
> definitions:
>
> MKDIR /var/lib/clamav
> CHMOD 750 /var/lib/clamav
> CHOWN clamav:vscan /var/lib/clamav

OK I added this.

>
> A quick explanation:
> /var/lib/clamav is the default directory for virus definitions. As 
> Sagator is executed jailrooted, this directory (actually 
> /var/spool/vscan/var/lib/clamav) does not exist.  This is also the 
> directory where Sagator excepts the virus defs to be.
> ClamAV requires write access to this directory, but Sagator 
> (user/group vscan) only requires read+chdir access.
>
> This change, however is not sufficient.  ClamAV is not executed 
> jailrooted.  That means the ClamAV default directory /var/lib/clamav 
> does not match with Sagator's /var/spool/vscan/var/lib/clamav.
>
> Sagator's readme file recommends changing the following two files
> /etc/freshclam.conf
> /etc/clamd.conf
>
> ...and the change is simple:
>
> DatabaseDirectory /var/spool/vscan/var/lib/clamav

Hmmmm......
Anybody else has an oppinion about this?

>
> You could leave the default line there as a commented one.
>
> There is a minor drawback here: You have to remember to do this change 
> every time you upgrade ClamAV, and that is (fortunately) quite often.
>
> ***
>
> As there is very little use on DL for ClamAV alone -- it is almost 
> always used with Sagator, I think the above DatabaseDirectory change 
> propably should make it to the default etc.tar.bz2.
>
> Comments?
>



-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] ClamAV with Sagator - considerations

[Heiko Z. <he...@zu...>]

Kari Mattsson wrote:

>
> Hi!
>
> If/when we have the recommended line "stream2mbox(libclam())," enabled 
> in /etc/sagator.conf, we actually are *not* using clamd?!
>
> Instead we are using the native ClamAV API. 
> Recommended+faster+safer+more robust.
>
> We *do* need freshclam for obvious reasons.
>
> I recommend we split the current /etc/init.d/clamd into 
> /etc/init.d/clamd and /etc/init.d/freshclam.
>
> ...and while you are at that, please do not force the freshclam log 
> file to be /var/log/clam-update.log -- it took me ages to find that 
> line in the current /etc/init.d/clamd.
> Personally I want the log file to be /var/log/freshclam.log.
> (There is a proper line in /etc/freshclam.conf for this setting.)
>
> Freshclam should start before clamd, of course.


I didn't split the files, but I corrected the name of the logfile.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] DL mail gateway notes

[Heiko Z. <he...@zu...>]

Kari Mattsson wrote:

>
> Few notes from my mailgw.....com project:
>
> - the following services are required:
>   postfix, spamd, freshclam, sagator, syslog[-ng]
> - postfix requires quite a bit hacking for a safe setup, which is 
> accidentally NOT an open relay, but still is an backup MX for many 
> domains, and optionally an gateway for some LAN-side mail servers

I guess it would be nice to post the key settings to the discuss list, 
I'm sure some users will appreciate this.

> - it is a good idea to limit the relay_recipients in postfix so that 
> you don't get overloaded with spam sent to non-existing addresses
> - integrating sagator+clamav+spamassassin to postfix is rather 
> straightforward
> - it would be a great addition, if i could integrate postfix to 
> saslauthd on this same setup, but it is not possible at this time due 
> to a missing saslauth conf file -- this seems to be a known issue

Are we missing this file?

> - last but not least: getting a (graphical) report a something of a 
> key requirement on production systems; currently this seems next to 
> impossible with a stock DL
>
>    - sagator has a /etc/mrtg/sagator.cfg file for rudimentary mrtg 
> graphing -- DL does not have mrtg, only rrdtool.
>    - i tried to find a way to convert that sagtor.cfg to something 
> rrdtool would understand, but my knowledge falls short at this time.
>    - mailgraph is an excellent (best?) graphing tool on 
> postfix+spamassassin+clamav log files, it uses rrdtool. well, 
> mailgraph only works with metalog ja syslog log files, not with 
> syslog-ng. i'm told changing from syslog-ng to syslog might break 
> things. mailgraph also requires few more perl modules than we 
> currently have.

I may add mrtg to 1.2.5, but no promises.
I wanted to add some more stuff anyway, it just depends how much time I 
have available.

> Any suggestions on how I could get graphs on mail traffic?

Pen and Paper ? ;-)

>
> I'm willing to send key parts of my main.cf and some other key files, 
> if there is interest. Either to this list, or to requester(s) directly.



-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-linux-develop] DL mail gateway notes

[Kari M. <ka...@tr...>]

Few notes from my mailgw.....com project:

- the following services are required:
   postfix, spamd, freshclam, sagator, syslog[-ng]
- postfix requires quite a bit hacking for a safe setup, which is=20
accidentally NOT an open relay, but still is an backup MX for many=20
domains, and optionally an gateway for some LAN-side mail servers
- it is a good idea to limit the relay_recipients in postfix so that you=20
don't get overloaded with spam sent to non-existing addresses
- integrating sagator+clamav+spamassassin to postfix is rather=20
straightforward
- it would be a great addition, if i could integrate postfix to=20
saslauthd on this same setup, but it is not possible at this time due to=20
a missing saslauth conf file -- this seems to be a known issue
- last but not least: getting a (graphical) report a something of a key=20
requirement on production systems; currently this seems next to=20
impossible with a stock DL

    - sagator has a /etc/mrtg/sagator.cfg file for rudimentary mrtg=20
graphing -- DL does not have mrtg, only rrdtool.
    - i tried to find a way to convert that sagtor.cfg to something=20
rrdtool would understand, but my knowledge falls short at this time.
    - mailgraph is an excellent (best?) graphing tool on=20
postfix+spamassassin+clamav log files, it uses rrdtool. well, mailgraph=20
only works with metalog ja syslog log files, not with syslog-ng. i'm=20
told changing from syslog-ng to syslog might break things. mailgraph=20
also requires few more perl modules than we currently have.


Any suggestions on how I could get graphs on mail traffic?

I'm willing to send key parts of my main.cf and some other key files, if=20
there is interest. Either to this list, or to requester(s) directly.


Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

[Devil-linux-develop] ClamAV with Sagator - considerations

[Kari M. <ka...@tr...>]

Hi!

If/when we have the recommended line "stream2mbox(libclam())," enabled=20
in /etc/sagator.conf, we actually are *not* using clamd?!

Instead we are using the native ClamAV API.=20
Recommended+faster+safer+more robust.

We *do* need freshclam for obvious reasons.

I recommend we split the current /etc/init.d/clamd into=20
/etc/init.d/clamd and /etc/init.d/freshclam.

...and while you are at that, please do not force the freshclam log file=20
to be /var/log/clam-update.log -- it took me ages to find that line in=20
the current /etc/init.d/clamd.
Personally I want the log file to be /var/log/freshclam.log.
(There is a proper line in /etc/freshclam.conf for this setting.)

Freshclam should start before clamd, of course.


Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

Re: [Devil-linux-develop] Sagator and ClamAV interaction+integration on DL - minor fix

[Heiko Z. <he...@zu...>]

>

> This is for mail gateway implementations of Devil-Linux.
>
>
> Sagator is a nice integrator between Postfix, SpamAssassin and ClamAV.
>
>
> The default settings with DL are not working properly.  Previously I
> sent a minor fix for SpamAssassin+Sagator.  This posting is for
> ClamAV+Sagator.
>
>
> You can do this in many different ways.  This way changes as little as
> possible the default configuration.
>
> I suggest you add to file /etc/sysconfig/jail/SAGATOR the following 3
> lines to add the directory (with proper user rights) for virus
> definitions:
>
>
> MKDIR /var/lib/clamav
> CHMOD 750 /var/lib/clamav
> CHOWN clamav:vscan /var/lib/clamav
>
>
> A quick explanation:
> /var/lib/clamav is the default directory for virus definitions. As
> Sagator is executed jailrooted, this directory (actually
> /var/spool/vscan/var/lib/clamav) does not exist.  This is also the
> directory where Sagator excepts the virus defs to be. ClamAV requires write
> access to this directory, but Sagator (user/group vscan) only requires
> read+chdir access.
>
> This change, however is not sufficient.  ClamAV is not executed
> jailrooted.  That means the ClamAV default directory /var/lib/clamav does
> not match with Sagator's /var/spool/vscan/var/lib/clamav.
>
> Sagator's readme file recommends changing the following two files
> /etc/freshclam.conf
> /etc/clamd.conf
>
>
> ...and the change is simple:
>
>
> DatabaseDirectory /var/spool/vscan/var/lib/clamav
>
>
>
> You could leave the default line there as a commented one.
>
>
> There is a minor drawback here: You have to remember to do this change
> every time you upgrade ClamAV, and that is (fortunately) quite often.
>
> ***
>
>
> As there is very little use on DL for ClamAV alone -- it is almost
> always used with Sagator, I think the above DatabaseDirectory change
> propably should make it to the default etc.tar.bz2.
>
> Comments?

I have my sagator configured to connect to clamd, which currently is not
chrooted.
Your suggestion would actually improve security, so if nobody complains we
could do the change.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-linux-develop] Sagator and ClamAV interaction+integration on DL - minor fix

[Kari M. <ka...@tr...>]

This is for mail gateway implementations of Devil-Linux.

Sagator is a nice integrator between Postfix, SpamAssassin and ClamAV.

The default settings with DL are not working properly.  Previously I=20
sent a minor fix for SpamAssassin+Sagator.  This posting is for=20
ClamAV+Sagator.

You can do this in many different ways.  This way changes as little as=20
possible the default configuration.

I suggest you add to file /etc/sysconfig/jail/SAGATOR the following 3=20
lines to add the directory (with proper user rights) for virus definition=
s:

MKDIR /var/lib/clamav
CHMOD 750 /var/lib/clamav
CHOWN clamav:vscan /var/lib/clamav

A quick explanation:
/var/lib/clamav is the default directory for virus definitions. As=20
Sagator is executed jailrooted, this directory (actually=20
/var/spool/vscan/var/lib/clamav) does not exist.  This is also the=20
directory where Sagator excepts the virus defs to be.
ClamAV requires write access to this directory, but Sagator (user/group=20
vscan) only requires read+chdir access.

This change, however is not sufficient.  ClamAV is not executed=20
jailrooted.  That means the ClamAV default directory /var/lib/clamav=20
does not match with Sagator's /var/spool/vscan/var/lib/clamav.

Sagator's readme file recommends changing the following two files
/etc/freshclam.conf
/etc/clamd.conf

...and the change is simple:

DatabaseDirectory /var/spool/vscan/var/lib/clamav


You could leave the default line there as a commented one.

There is a minor drawback here: You have to remember to do this change=20
every time you upgrade ClamAV, and that is (fortunately) quite often.

***

As there is very little use on DL for ClamAV alone -- it is almost=20
always used with Sagator, I think the above DatabaseDirectory change=20
propably should make it to the default etc.tar.bz2.

Comments?



Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

Re: [Devil-linux-develop] Sagator jailing, minor fix

[Heiko Z. <he...@zu...>]

>

> This is for DL implementations, where you are using Sagator and Spamd
> (SpamAssassin).  OK, you want ClamAV too, but it is not an issue here.
>
>
>
> If you want to get rid of the following kind of log errors:
>
>
> Apr 12 09:43:55 s_dgram@mailgw spamd[14935]: Creating default_prefs
> [/var/spool/vscan/.spamassassin/user_prefs]
> Apr 12 09:43:55 s_dgram@mailgw spamd[14935]: Cannot write to
> /var/spool/vscan/.spamassassin/user_prefs: Permission denied
> Apr 12 09:43:55 s_dgram@mailgw spamd[14935]: Couldn't create readable
> default_prefs for [/var/spool/vscan/.spamassassin/user_prefs]
>
>
> ...just add the following 2 lines to file /etc/sysconfig/jail/SAGATOR:
>
>
> MKDIR /.spamassassin
> CHMOD 777 /.spamassassin
>
>
>
> That user_prefs file is a per user settings file for SpamAssassin

I added it to 1.2 and 1.3.

Thanks!

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-linux-develop] Sagator jailing, minor fix

[Kari M. <ka...@tr...>]

This is for DL implementations, where you are using Sagator and Spamd=20
(SpamAssassin).  OK, you want ClamAV too, but it is not an issue here.


If you want to get rid of the following kind of log errors:

Apr 12 09:43:55 s_dgram@mailgw spamd[14935]: Creating default_prefs=20
[/var/spool/vscan/.spamassassin/user_prefs]
Apr 12 09:43:55 s_dgram@mailgw spamd[14935]: Cannot write to=20
/var/spool/vscan/.spamassassin/user_prefs: Permission denied
Apr 12 09:43:55 s_dgram@mailgw spamd[14935]: Couldn't create readable=20
default_prefs for [/var/spool/vscan/.spamassassin/user_prefs]


...just add the following 2 lines to file /etc/sysconfig/jail/SAGATOR:

MKDIR /.spamassassin
CHMOD 777 /.spamassassin


That user_prefs file is a per user settings file for SpamAssassin


Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

[Devil-linux-develop] Re: Some DL errors I've found & Tanks!

[Kari M. <ka...@tr...>]

> Kari Mattsson wrote:
>=20
>> Hello!
>>
>> Sagator:
>>
>> The otherwise good example file (taken directly form Sagator's home)=20
>> /etc/sagator.conf has a non-working LOGFILE setting.  There is no=20
>> /var/log/sagator directory for the sagator.log file.  I fixed this by=20
>> just removing 'sagator/' from the LOGFILE setting line.

Just changing my mind here:

Rather than removing 'sagator/' above, it is better to create the=20
directory /var/log/sagator, as I've found links to that directory in=20
some other places.  Right now I just remember stuff under /var/log.d/=20
directory.

????? Which program/service is using that /etc/log.d directory anyway?


Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

Re: [Devil-linux-develop] Beefing up the named on DL

[Heiko Z. <he...@zu...>]

>> thanks for the files.
>>
>> Could somebody look over the files ? I don't really have much bind
>> experience...
>
> They look OK to me. (but no guarantees since I haven't tried them :)
>
>
> One change I suggest is to rename all occurrences of "root.hint" with
> "named.root".  That way it's easier to download the latest version
> (using wget/curl/whatever) without renaming it from:
>
>
> ftp://ftp.internic.net/domain/named.root

Sounds good to me.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] Beefing up the named on DL

[Bruce S. <br...@ar...>]

> thanks for the files.
> 
> Could somebody look over the files ? I don't really have much bind
> experience...

They look OK to me. (but no guarantees since I haven't tried them :)

One change I suggest is to rename all occurrences of "root.hint" with
"named.root".  That way it's easier to download the latest version
(using wget/curl/whatever) without renaming it from:

    ftp://ftp.internic.net/domain/named.root

 - BS


> > Hi!
> >
> >
> > The default named configuration is rather empty.  On purpose?
> > The root.hint is there, but not much else.
> >
> >
> > On a proper installation you need/want name service also for the
> > localhost, and the 127.0.0 network. (Forward + reverse.)
> >
> > Attached are versions of the core config files, which should be rather
> > suitable for everybody.  I think they are even ok for inclusion on the
> > default etc.tar.bz2.
> >
> > The root.hint file on current DL CD is from 1997.  The attached version
> > is from 2004.
> >
> >
> > Terveisin/With kind regards/Med hälsningar/Lugupidamisega,
> >
> >
> > Kari Mattsson
> > Trivore Corp.
> >
> >
> >
> 
> 

Re: [Devil-linux-develop] Beefing up the named on DL

[Heiko Z. <he...@zu...>]

Hey,

thanks for the files.

Could somebody look over the files ? I don't really have much bind
experience...

Thx !

Heiko

>

> Hi!
>
>
> The default named configuration is rather empty.  On purpose?
> The root.hint is there, but not much else.
>
>
> On a proper installation you need/want name service also for the
> localhost, and the 127.0.0 network. (Forward + reverse.)
>
> Attached are versions of the core config files, which should be rather
> suitable for everybody.  I think they are even ok for inclusion on the
> default etc.tar.bz2.
>
> The root.hint file on current DL CD is from 1997.  The attached version
> is from 2004.
>
>
> Terveisin/With kind regards/Med hälsningar/Lugupidamisega,
>
>
> Kari Mattsson
> Trivore Corp.
>
>
>


-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-linux-develop] Beefing up the named on DL

[Kari M. <ka...@tr...>]

Hi!

The default named configuration is rather empty.  On purpose?
The root.hint is there, but not much else.

On a proper installation you need/want name service also for the=20
localhost, and the 127.0.0 network. (Forward + reverse.)

Attached are versions of the core config files, which should be rather
suitable for everybody.  I think they are even ok for inclusion on the
default etc.tar.bz2.

The root.hint file on current DL CD is from 1997.  The attached version=20
is from 2004.


Terveisin/With kind regards/Med h=E4lsningar/Lugupidamisega,

Kari Mattsson
Trivore Corp.

Re: [Devil-linux-develop] please resend patches

[Heiko Z. <he...@zu...>]

Zsiros Zsolt wrote:

>2005-02-12, szo keltezéssel 04:10-kor Heiko Zuerker ezt írta:
>  
>
>>Hey everybody,
>>
>>Please resend all patches since 01/29/05 , because I lost all emails
>>after this date.
>>
>>    
>>
>
>Hi Heiko,
>
>I've created a jail script for ntpd and a little patch for the xntpd
>init script to start the daemon in chroot jail.
>I attach the patch and the NTPD jail script.
>  
>

It's committed to CVS and will be included in 1.2.5.

-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

[Devil-linux-develop] Re: Some DL errors I've found & Tanks!

[Heiko Z. <he...@zu...>]

Kari,

thanks for the bug report.
It would be great if you could use the mailinglist in the future.

cu
Heiko

Kari Mattsson wrote:

>
> Hello!
>
> We are (starting) to use DL for several different purposes due to its 
> "Ultra Rapid Deployment" nature combined with up-to-dateness, 
> excellent documentation, and over-all robustness.  Thnaks for the work 
> so far!
>
> As we are humans, there are some errors.  Here are the ones I've found 
> in all versions 1.2.1 - 1.2.3, and propably also 1.2.4 (I'm 
> downloading it now):
>
>
> Named/bind:
>
> -  file /etc/rndc.key is missing. It will cause an error to be 
> displayed in the log when it is started. I fixed this with just 'touch 
> /etc/rndc.key', as I'm not really using the rndc feature.
>
> -  The /etc/sysconfig/jail/ISC_BIND file is missing a corresponding line
> COPY /etc/rndc.key to copy that empty file to the jailroot.
>
>
> Sagator:
>
> The otherwise good example file (taken directly form Sagator's home) 
> /etc/sagator.conf has a non-working LOGFILE setting.  There is no 
> /var/log/sagator directory for the sagator.log file.  I fixed this by 
> just removing 'sagator/' from the LOGFILE setting line.
>
>
> Sagator-Postfix integration:
>
> You might want to add the following lines to the two main Postfix 
> configuration files either commented, or non-commented to make the 
> life easier for Sagator users:
>
>
> # /etc/postfix/main.cf - Sagator requirement below:
> #content_filter = smtp:localhost:27
>
> # /etc/postfix/master.cf
> # Sagator required addition below:
> # Local smtpd without scanning
> #localhost:26    inet n - n - 30 smtpd
> #  -o content_filter=
> #  -o myhostname=sagator.mydomain.sk
> #  -o local_recipient_maps=  -o relay_recipient_maps=
> #  -o mynetworks=127.0.0.0/8  -o mynetworks_style=host
> #  -o smtpd_restriction_classes=  -o smtpd_client_restrictions=
> #  -o smtpd_helo_restrictions=  -o smtpd_sender_restrictions=
> #  -o smtpd_recipient_restrictions=permit_mynetworks,reject
> #  -o 
> receive_override_options=no_unknown_recipient_checks,no_header_body_checks 
>
>
>
> The last line above is a bit long...  The above lines are from Sagator 
> readme documentation.
>
>
> NTP
>
> You might want to add two to four times the line
>
> server pool.ntp.org
>
> to the file /etc/ntp.conf to have good global defaults for NTP servers.
> I recently noticed Debian and Gentoo both default to that same address.
> Adding the line more than once allows ntpd to use the best ntp server, 
> not just one.
>
>
> SpamAssassin - SPAMD
>
> You also might want to enable Razor2 in SpamAssassin, as you have it 
> on DL.  Just the line
>
> use_razor2 1
>
> to the file /etc/mail/spamassassin/local.cf will do it.
>
>
> Software RAID documentation
>
> I followed the documentation on v1.2, chapter 6 to create software 
> RAID-1.  It worked okay, but after a reboot did not find the /dev/md0 
> anymore.
>
> I found out the instructions are a bit mixed.  You either have to use 
> the short (legacy) device names, or long (recommended) device names. 
> You cannot mix those.
>
> So, the /etc/mdadm.conf must be (for IDE-only system) either like
>
> DEVICE /dev/ide/host?/bus?/target?/lun0/part*
> ARRAY /dev/md/0 level=raid1 num-devices=2
>    UUID=d876333b:694e852b:e9a6f40f:0beb90f9
> devices=/dev/ide/host0/bus0/target0/lun0/part1,/dev/ide/host0/bus0/target1/lun0/part1 
>
>
>
> ....or like:
>
>
> DEVICE /dev/hd*
> ARRAY /dev/md0 level=raid1 num-devices=2
>    UUID=d876333b:694e852b:e9a6f40f:0beb90f9
>    devices=/dev/hda1,/dev/hdb1
> ´
>
> ....and then software RAID will work ok.
>
>
>
> And a request in the end:
>
> Have you considered adding 'mailgraph' 
> <http://people.ee.ethz.ch/~dws/software/mailgraph/> to DL?  If not, 
> could you?  I know it is easy to add my own, but still..
>
>
>
> I hope these issues are not too trivial, or something for you 
> correct/change.  I also hope it is okay for me to email you some other 
> findings in the future, shall I find those.
>
>
>
> Terveisin/With kind regards/Med hälsningar/Lugupidamisega,
>
> Kari Mattsson
> Trivore Corp. (Finland)
>


-- 

Regards
  Heiko Zuerker
  http://www.devil-linux.org

Re: [Devil-linux-develop] patch to get postfix to work with saslauthd

[Friedrich L. <fl...@fl...>]

Heiko Zuerker wrote on 13.03.2005 17:23 MET:
> Friedrich Lobenstock wrote:
> 
>> PS: This is just step closer as I now got saslauthd talk to the imap 
>> server BUT there some other problems there. Updates to come...
>
> I did a quick test with the patch and it fails only in 1 place for the 
> currently used Postfix 2.1.5. Postfix 2.2.0 has 2 rejects.
> This wouldn't be hard to fix.
> 
> Do you want us to wait until you're further down the road with your 
> implementation ?

The PSU of the machine I was testing this on, is dead and I'll have to see if I 
can continue testing because it's not decided yet if this machine will ever be 
resurrected.

-- 
MfG / Regards
Friedrich Lobenstock
____________________________________________________________________
Friedrich Lobenstock                       Linux Services Lobenstock
URL: http://www.lsl.at/                         Email: fl...@fl...
____________________________________________________________________