From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: transferring contents of /etc/conf.d to the config files
Date: Mon, 10 Oct 2011 20:45:17 +0200 [thread overview]
Message-ID: <20111010184517.GB2844@solfire> (raw)
In-Reply-To: <j6vb3t$le3$1@dough.gmane.org>
Nikos Chantziaras <realnc@arcor.de> [11-10-10 19:52]:
> On 10/10/2011 08:33 PM, meino.cramer@gmx.de wrote:
> >Hi,
> >
> >I have read several docs to figure out this...all docs do changes
> >in /etc/conf.d but I found no hint how to transfer that settings
> >to the "real" configuration files of the according programs.
>
> These *are* real configuration files and you don't need to transfer
> anything.
>
>
The reason I thought, that those settings in /etc/conf.d is due
to a warning of the rkhunter tool:
[03:23:21] Performing system configuration file checks
[03:23:21] Info: Starting test name 'system_configs'
[03:23:21] Checking for SSH configuration file [ Found ]
[03:23:21] Info: Found SSH configuration file: /etc/ssh/sshd_config
[03:23:21] Info: Rkhunter option ALLOW_SSH_ROOT_USER set to 'no'.
[03:23:21] Info: Rkhunter option ALLOW_SSH_PROT_V1 set to '0'.
[03:23:21] Checking if SSH root access is allowed [ Warning ]
[03:23:21] Warning: The SSH configuration option 'PermitRootLogin' has not been set.
The default value may be 'yes', to allow root access.
[03:23:21] Checking if SSH protocol v1 is allowed [ Warning ]
[03:23:21] Warning: The SSH configuration option 'Protocol' has not been set.
The default value may be '2,1', to allow the use of protocol version 1.
[03:23:22] Checking for running syslog daemon [ Not found ]
[03:23:22] Info: The syslog daemon is not running, but a metalog daemon has been found.
[03:23:22] Checking for syslog configuration file [ Not found ]
Now I see, that it seems to check simply the wrong file.
I think it would be an idea to patch rkhunter to be more compliant to
the setup of the gentoo system ?!
From own experience I know that a lot false warnings of such tools
dull the sigth on to the real threads...
Only my two cents, your currency may vary... ;)
Best regards,
mcc
next prev parent reply other threads:[~2011-10-10 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-10 17:33 [gentoo-user] transferring contents of /etc/conf.d to the config files meino.cramer
2011-10-10 17:47 ` [gentoo-user] " Nikos Chantziaras
2011-10-10 18:45 ` meino.cramer [this message]
2011-10-10 18:53 ` Nikos Chantziaras
2011-10-10 19:13 ` meino.cramer
2011-10-10 19:28 ` Canek Peláez Valdés
2011-10-10 21:49 ` Nikos Chantziaras
2011-10-10 17:50 ` [gentoo-user] " Alan McKinnon
2011-10-10 17:56 ` Canek Peláez Valdés
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111010184517.GB2844@solfire \
--to=meino.cramer@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox