37495 – Security guide should use sysctl.conf instead of self-written init script

Bug 37495 - Security guide should use sysctl.conf instead of self-written init script

Summary: Security guide should use sysctl.conf instead of self-written init script

Status:	RESOLVED FIXED

Alias:	None

Product:	[OLD] Docs-user
Classification:	Unclassified
Component:	Gentoo Security Guide (show other bugs)
Hardware:	All All

Importance:	High normal (vote)
Assignee:	Sven Vermeulen (RETIRED)

URL:
Whiteboard:
Keywords:

Duplicates (1):	35263 (view as bug list)
Depends on:
Blocks:

Reported:	2004-01-07 10:18 UTC by Sven Vermeulen (RETIRED)
Modified:	2005-02-05 00:07 UTC (History)
CC List:	2 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sven Vermeulen (RETIRED) gentoo-dev

2004-01-07 10:18:39 UTC

(A mail from Peter Koeleman to www@gentoo.org)

Dear Gentoo people,

Reading http://www.gentoo.org/doc/en/gentoo-security.xml I found that section
10. Kernel security contains info on creating /etc/init.d/procparam which
contains custom /proc kernel parameter settings. But sys-apps/baselayout
contains the /etc/sysctl.conf file which was designed to restore these
settings at boot thus the /etc/init.d/procparam file is obsolete;
editing /etc/sysctl.conf should do the trick.

Greetings,
Peter Koeleman
Happy Gentoo user

Comment 1 Sven Vermeulen (RETIRED) gentoo-dev

2004-02-08 06:21:05 UTC

Committed.

Comment 2 Joe McCann (RETIRED) gentoo-dev

2005-02-05 00:07:50 UTC

*** Bug 35263 has been marked as a duplicate of this bug. ***